Erases the static cluster definition contained on the system master volume, without reinitializing the metadata, which in affect drops all metadata servers from the cluster at one time.
This task must be performed only by trained service technicians.
The cluster must be stopped.
This command is used in extreme disaster recovery situations or when you attach new hardware to an existing cluster.
This command is located in the /usr/tank/server/bin directory.
This command must be run from an engine that has a Tank.Bootstrap file. If the engine does not have a Tank.Bootstrap file, this file can be recovered from the master volume using the tank extractbootrecord command. If the master volume is unknown, you can issue the tank lsdisklabel command to inspect the SAN File System product label and to locate the master volume.
After you run this command, the first metadata server that is started with a valid Tank.Bootstrap file becomes the new master metadata server. At this point, the cluster is a single-engine cluster, and all additional metadata servers must be added using the addserver command. In addition, it might be necessary to move filesets to these new engines (using the setfilesetserver command) if the added engines have different names than the original cluster's engine names.
#/usr/tank/server/bin/tank resetcluster Static cluster definition has been reset. cluster size = 0