Softpanorama (slightly skeptical) Open Source Software Educational Society

May the source be with you, but remember the KISS principle ;-) Softpanorama Search

wbkupdb command

wbkupdb command -- Backs up and restores Tivoli object databases.

Notes

1. If you are unable to capture a full backup because of the high activity level of your Tivoli region, you can use the wlocktmr command to place your Tivoli region in maintenance mode and then run the wbkupdb command again. For more information about placing a Tivoli region in maintenance mode, refer to Tivoli Management Framework Maintenance and Troubleshooting Guide.
2. The backup is written to the $DBDIR directory.
3. For a Tivoli server, recovered files are as follows:

• odb.bdb
• odb.log
• imdb.bdb
• notice.log
• odlist.dat
• \epmgr.db (directory)
• \file_versions (directory)

Syntax

• wbkupdb -e [node_name...]
• wbkupdb -e -l [object node_name...]
• wbkupdb [-b] [-d device] [-f] [-h node_name] [node_name...]
• wbkupdb -l [-d device] [-f] [-h node_name] [object node_name...]
• wbkupdb -d device -r [-R] [node_name...]
• wbkupdb -d device -r -l [-R] [object node_name...]
• wbkupdb -s

When the -e option is used, this command estimates the total size of the backup archive. The wbkupdb -e command estimates the size of the backup of each managed node and the total size of the archive. This report is an estimate, but it is very close to the actual size of the backup image.

The third and fourth forms of this command (as shown in the syntax) back up the database and store it in the specified file or device on the specified system. If the backup file already exists and is a disk file, you must specify the -f option to overwrite the old backup file.

When the -r option is used, this command restores Tivoli object databases. This is primarily useful for reverting to a previously saved copy of the Tivoli object databases that you backed up. The Tivoli server or managed node that is to be restored must have Tivoli Management Framework operational. If a restore operation is being performed from a system other than the Tivoli server, you cannot restore both the Tivoli server and the local database unless you specify the -R option. If you restore the local database, you must use the explicit node_name syntax and specify the local node at the end or specify the -R option.

If the object dispatcher that is to be restored is not running (and presumably cannot be run because its database is corrupted or missing), you can extract the database manually and put the files in the correct location in the database directory.

The wbkupdb command also saves any old versions of files and the notification database. Typically, these are not restored, because you probably do not want to read notices that have already been read. If for some reason the file is destroyed, you can restore it manually. The \files_versions directory is not restored. If you want to see old revisions of system files, the files can be moved from the \files_versions.restore directory as necessary.

The following list details the files and databases backed up in the temporary directory on UNIX and Windows managed nodes and Tivoli servers:

• For a Tivoli server, recovered files are as follows:
  • odb.bdb
  • odb.log
  • imdb.bdb
  • notice.log
  • odlist.dat
  • \epmgr.db (directory)
  • \file_versions (directory)

Options

-b

Blocks the writing of data to the Tivoli object databases during the backup. When you specify this option, the object dispatcher does not write data to the Tivoli object database while the database is backed up. After the backup operation completes, any write operations that queued during the backup operation are written to the database. Use the -b option when you want to ensure that the Tivoli object databases are unchanged for the duration of the backup, for example, in a very busy Tivoli environment. If you use the -b option to back up a node that has not been upgraded to a version of Tivoli Management Framework that contains this feature, the standard backup method is used for that node.

The -b option causes the backup operation to check for needed disk space before performing the backup. A warning message is displayed if sufficient disk space is not available.

Note

The needed disk space is estimated by calculating twice the sum of the sizes of odb.bdb and imdb.bdb. In some environments, this estimate might be too low. For these situations, you can set the TIVBACKUPSIZE environment variable to override the estimate produced by the -b option. Set the value for TIVBACKUPSIZE in KB. On Windows operating systems, TIVBACKUPSIZE must be a system environment variable.

 

When you specify this option, the object dispatcher writes error messages that result from the backup to the oservlog file.

-d device

Specifies the file or device to which the backup file should be saved or from which the backup file should be retrieved. If you specify a file name, you can insert a file date and time anywhere in the file name by adding the %t variable. This variable is replaced with a time stamp in the form Mondd-hhmm. For example, if you specify -d /usr/backups/TMR1%t.bk, the resulting file is named TMR1Dec21-0955.bk. The time is displayed in 24-hour mode.

-e

Estimates the size of the backup.

-f

Overwrites a previous backup file of the same name.

-h node_name

Specifies the system that contains the .tar file that is created by the wbkupdb command. The default is the Tivoli server.

-l

Specifies that options on the command line are object and label pairs. This option is for internal use only.

-r

Restores the databases for the specified nodes.

-R

Does not restart object dispatchers after restoring the database files. A number of .restore files are placed in the database directory. To effect the changes, use the reexec option of the odadmin command or one of its derivatives to restart the object dispatchers so that they pick up the restored copies of the databases.

-s

Suppresses display of an initial desktop message for each managed node being backed up.

node_name

Specifies the node to be backed up. You can specify multiple nodes.

object

Specifies a backup object identifier.

Authorization

Examples

See Also