This topic explains how to restore the configuration for the SAN
File System cluster.
Steps
- If the system was backed up using the LUN method, and the entire
cluster is down, perform these steps to restore the cluster configuration
information:
- If you have previously saved the configuration files to another location,
copy these files onto the boot drive for the engine.
- Copy Tank.Bootstrap to /usr/tank/server/config.
- Copy Tank.Config to /usr/tank/server/config.
Note: If you have saved any other administrative configuration files,
you can reference them when restoring the SAN File System metadata configuration.
- If the cluster bootstrap file, Tank.Bootstrap, is corrupted or missing,
you can attempt to recreate the contents of that file using information from
the metadata LUNs:
- Use the /usr/tank/server/bin/tank lsdisklabel –device command
to find the master volume. If you cannot remember which device is your master
volume, this is an iterative process of searching all suspected master volume
devices until the command indicates you have found a valid master volume.
- Use the /usr/tank/server/bin/tank extractbootrecord command
to regenerate Tank.Bootstrap from the master volume.
- Use the /usr/tank/server/bin/tank resetcluster command
to reinitialize the master volume for subsequent rebuilding of the cluster
configuration.
- Use the /usr/tank/server/bin/tank addserver command
for all subordinate metadata server engines to recreate the cluster definition.
- If the system was backed up using the LUN method,
and only the master metadata server is down, perform these steps to restore
the cluster configuration information:
- If you have previously saved the configuration files to another location,
copy these files onto the boot drive for the engine.
- Copy Tank.Bootstrap to /usr/tank/server/config.
- Copy Tank.Config to /usr/tank/server/config.
Note: If you have saved any other administrative configuration files,
you can reference them when restoring the SAN File System metadata configuration.
- If the cluster bootstrap file, Tank.Bootstrap, is corrupted or missing,
you can attempt to recreate the contents of that file using information from
the metadata LUNs:
- Use the /usr/tank/server/bin/tank lsdisklabel –device command
to find the master volume. If you cannot remember which device is your master
volume, this is an iterative process of searching all suspected master volume
devices until the command indicates you have found a valid master volume.
- Use the /usr/tank/server/bin/tank extractbootrecord command
to regenerate Tank.Bootstrap from the master volume.
- Use the /usr/tank/server/bin/tank resetcluster command
to reinitialize the master volume for subsequent rebuilding of the cluster
configuration.
- Use the /usr/tank/server/bin/tank addserver command
to add the original master metadata server to the cluster.
- Use the /usr/tank/server/bin/tank resetcluster command
to reinitialize the master volume for subsequent rebuilding of the cluster
configuration.
- If the system was backed up using the API method, perform these
steps to restore the cluster configuration information:
- If you have previously saved the configuration files to another location,
copy these files onto the boot drive for the engine.
- Copy Tank.Bootstrap to /usr/tank/server/config.
- Copy Tank.Config to /usr/tank/server/config.
Note: If you have saved any other administrative configuration files,
you can reference them when restoring the SAN File System metadata configuration.
- If you suspect that the metadata LUNs are corrupted, you can perform these
steps to recreate the cluster definition:
- Delete all Tank.Bootstrap and Tank.Config files from your metadata server
engines.
- Start the /usr/tank/server/bin/tank binary on
your master metadata server with the install option
rather than normal option.
Attention: The existing metadata
data server information will be overwritten.
This will create new
Tank.Bootstrap and Tank.Config files on your master metadata server. Be sure
to specify the same cluster name that was used prior to the disaster:
- Now start the master metadata server with /usr/tank/server/bin/tank
normal command.
- Use the addserver command to add all subordinate
metadata server engines. This will create new Tank.Bootstrap and Tank.Config
files on the subordinates.