682 Implementing the IBM Storwize V5000 Gen2 with IBM Spectrum Virtualize V8.1
PSU replacement procedure
For information about the PSU replacement process, see the IBM Storwize V5000 Gen2
Knowledge Center at this website:
https://ibm.biz/Bdjm8C
12.3 Configuration backup
The configuration backup file must be used if a serious failure occurs that requires the system
configuration to be restored. The file contains configuration data of arrays, pools, volumes,
and so on (but no client data).
The configuration backup file can be downloaded and saved by using the graphical user
interface (GUI) or the command-line interface (CLI). The CLI option requires you to log in to
the system and download the file by using Secure Copy Protocol (SCP). It is a preferred
practice for an automated backup of the configuration.
The backup file is updated by the cluster every day and stored in the /dumps directory. Even
so, it is important to start a manual backup after you change your system configuration.
To successfully perform the configuration backup, follow the prerequisites and requirements:
All nodes must be online.
No independent operations that change the configuration can be running in parallel.
No object name can begin with an underscore.
12.3.1 Generating a manual configuration backup by using the CLI
You can use the CLI to trigger a configuration backup either manually on an ad hoc basis or
by an automatic process regularly. The svcconfig backup command generates a new backup
file. Triggering a backup by using the GUI is not possible, but you can save the output from the
GUI.
Example 12-1 shows the output of the svcconfig backup command.
Example 12-1 Triggering a backup by using the CLI
>svcconfig backup
..................................................................................
..................................................................................
....................
CMMVC6155I SVCCONFIG processing completed successfully
Important: Save the configuration files of the IBM Storwize V5000 Gen2 regularly. The
best approach is to save daily and automate this task. Always perform the additional
manual backup before you perform any critical maintenance task, such as an update of the
microcode or software version.
Important: You can perform an ad hoc backup of the configuration only from the CLI.
However, the output of the command can be downloaded from both the CLI and the GUI.
To Next Page
Loading...
Need help?
General