setupsfs

Configures and starts a SAN File System metadata server.

Read syntax diagramSkip visual syntax diagram
>>-setupsfs----------------------------------------------------->

>--+--------------------------------------------------------------------+-><
   +- -backup--+------------------------------------------------------+-+
   |           '- -f--backup_list_file-- -backupdir--backup_directory-' |
   +- -f--config_file---------------------------------------------------+
   +- -debug--+------------------+--------------------------------------+
   |          '- -f--config_file-'                                      |
   +- -list--+------------------+---------------------------------------+
   |         '- -f--config_file-'                                       |
   +- -newcluster--+-----------------------+----------------------------+
   |               '- -f--engine_list_file-'                            |
   +- -noprompt--+------------------+-----------------------------------+
   |             '- -f--config_file-'                                   |
   '- -setmaster--+------------+--+-------------+--+------------------+-'
                  '- -noprompt-'  '- -overwrite-'  '- -f--config_file-'

Parameters

–backup backup_file
Creates a backup (tar archive) containing all metadata server configuration information. The list of files to be backed up are specified in /usr/tank/admin/config/backup.list. You can specify an alternate backup file list using the –f parameter. You can also customize the contents of backup.list to save any files of your choosing into the DR tarball.

By default the archive is stored as /usr/tank/server/DR/DRfiles-hostname-date.tar.gz

To restore a metadata server from a backup that was created using the –backup parameter, extract the tar archive in the root directory. For example:

tar -xzvf /usr/tank/server/DR/DRfiles-hostname-date.tar.gz
Then, run setupsfs without parameters (or with only the –noprompt parameter) to restart the metadata server.
Attention: Do not use the –setmaster parameter when restoring from a backup.
–backupdir directory_path
Specifies an alternate directory, in which to create the archive.
–debug
Provides extra parameters with defaults. The most common use of this parameter is when you are using Active Directory as your LDAP server.
–f file
Specifies the name of a file that contains configuration information, list of engines, or tar archive, depending on the parameters specified before the –f parameter.
–list
List all parameters and the corresponding values found in the configuration file.
–noprompt
Runs the setupsfs command without prompting you for information. The configuration file is expected to exist. If the configuration file does not exist or if a required value is missing or invalid, setupsfs exits with an error.
–newcluster engine_list
Adds one or more subordinate metadata servers to the cluster. Use this parameter only on the master metadata server.

The engine_list identifies the subordinate nodes to be added. All subordinate metadata servers must be running at the time that setupsfs –newcluster is started.

–overwrite
Initialize the master metadata server and system disks, regardless of whether they already contain cluster information.
Attention: Using this parameter destroys all data stored in the system storage pool.
–setmaster
Configures the metadata server as the master metadata server. If the given master disk already contains cluster information, this information is used when starting the metadata server.

Description

The setupsfs command is used to configure, start, or restart a metadata server. It can also be used to display the current configuration values and back up the configuration in case the server needs to be restored at a later date.

If you do not specify any parameters, setupsfs prompts you for the configuration values required to set up a subordinate metadata server. The setupsfs command maintains the values in a configuration file in parameter=value format. The configuration file is /usr/tank/admin/config/tank.properties. If a configuration file already exists, its values are presented as the suggested defaults when the prompt is displayed. Otherwise, the manufacturing defaults are presented.

Parent topic: SAN File System installation commands

Library | Support | Terms of use | Feedback
(C) Copyright IBM Corporation 2003, 2004. All Rights Reserved.
IBM TotalStorage SAN File System v2.2