There are two ways allowing a backup and restore of the Data Protector Internal Database. The procedures described below can also be used for performing migrations. The internal database is located in the DB40 folder within the installation directory.
The first way is relatively easy: create a backup job in the Data Protector Manager Console and select the Internal Database in the selection tree. The downside of this method is the lack of control where the database is stored (on a tape, but which one? on disk, in a bunch of files!) and how fast can it be restored in case of disaster. If you did not implement any fallback mechanisms, a catalog operation will be required! Needless to say it will take some time to complete.
Dumping the data to disk can come in very handy as a safety copy during maintenance operation such as upgrades, patchings, etc.
This can be executed by following these steps while logged onto the backup server (Cell Manager):
- Omnistat: to check if there are any running sessions.
- Omnisv -stop: to stop the Data Protector services.
- Omnisv -start: to start the Data Protector services, this will gain exclusive access to the IDB for the next command;
- omnidbutil -writedb -mmdb d:\dp\dumpmmdb\ -cdb d:\dp\dumpcdb\.
- When the script is completed, it will ask to copy some additional files.
- As a personal best-practice I copy also some of the folders in the configuration folder of Data Protector (such as Schedules, Datalists, Barlists, Barschedules, etc.), these hold the configuration data of the defined backupjobs.
Performing a restore can be executed in the following manner:
If the server changed hostname, it should also be changed in the IDB. Changing the hostname can be done by executing the following command: omnidbutil –change_cell_name “oldserver”.