HP StorageWorks Fabric Manager 5.x Administrator Guide (AA-RUQSF-TE, September 2005)

Fabric Manager 5.x administrator guide 225
20 Storing data and performing backups
Fabric Manager stores user settings when you exit, not while you run the software. When the client
attempts to log in to the server, the server authenticates the client login. After the server authenticates the
client, Fabric Manager launches and polls switches.
Fabric Manager stores the following user settings locally (on the client machine):
• Fabric Manager user name
• Host name/server IP address of all servers you have successfully accessed
• Browser path used to launch Advanced Web Tools
• Dimensions of the Fabric Manager window
The following user settings are saved on the database in the server:
• User interface settings (view customizations, topology locations, and so on)
• Switch user names and passwords
Other settings are global to all clients running on the same Fabric Manager server. To perform database
backups, you can use the dbbackup utility. The dbbackup utility is called from a script to back up the
Fabric Manager database. You can perform either a full backup or incremental backups. The full database
backup includes both the transaction log file and the database file. The incremental backup is used to back
up only the transaction log file.
Performing full backups
To perform a full backup, enter the following command in the CLI (the entire command is on a single line):
dbbackup -c
"uid=dba;pwd=sql;eng=fabman;CommLinks=tcpip{DOBROADCAST=DIRECT;HOST=localhost;Ser
verPort=2638}" -y -r -n destdir
where:
• destdir is the destination directory for the backup files.
• -y is an option that causes the dbbackup utility to overwrite files without a prompt.
CAUTION: Be careful with the -y option if you are always backing up the same directory. The
fabman.db database file is overwritten without a prompt by this option.
• -r is an option that renames and restarts the transaction log file after backing it up. You can use
this option to reduce the transaction log file size.
• -n is an option that causes the transaction log file to be named using the yymmddxx.log format,
where xx is AA, AB, AC, etc.
NOTE: A copy of the transaction log file is also placed in the databases directory. This copy can be
safely deleted after the backup is complete.