Loading a Snapshot

Loading using BdbTransferCond

The BdbTransferCond tool has been developed to minimized the down time that is needed to load a snapshot into a federation. It separates the transfer of the snapshot dbs to the conditions servers and replacing the existing conditions dbs into two independent steps. Only replacing the the dbs requires that the federation is locked (down time).

Two executables are used,

BdbTransferCond.pl (In package: BdbCondUtils)

is used to transfer the snapshot dbs and to replace (move) the existing ones.

BdbLockfdb.pl (In package: BdbAdminScripts)

is used to lock the federation.

Below is an example how a CDB snapshot would be loaded. The snapshot is in $snapDir and the two tdf files Conditions.tdf and Configuration.tdf exist. The OO_FD_BOOT is set to the boot file.

Transfering the Snapshot

export CONDTRANSFER=/nfs/objyserv03/objy/databases/import/test/CONDTRANSFER
BdbTransferCond.pl -tdf $snapDir/Conditions.tdf -tdf $snapDir/Configuration.tdf $OO_FD_BOOT -do

Transfers all dbs that are listed in the tdf files. The db path and host is obtained from the fdb catalog. If a db doesn't exist in the catalog the new db host is obtain from the from the file config (BdbFileConfigLoader).

A db that is transfered to a data server is using the file name suffix .condimp.bdb instead of .bdb and there the existing dbs are not overwritten. Therefore this step doesn't require that the federation is locked.

The CONDTRANSFER file is used to record which file have been transferd to which host and path. It is required for the next step.

Moving the Dbs

BdbLockfdb.pl -l $OO_FD_BOOT
sleep 300
BdbTransferCond.pl -import -importmode move -force -do
BdbLockfdb.pl -u $OO_FD_BOOT

Last modified: Tue Jul 11 22:05:43 PDT 2006