Devconfig and volhist during a disaster

[Dunul]

Hi all,

Just wondering,
In order to restore from a disaster, you must have the devconfig and volhist files.
Lets assume that a company has only one site and they using off siting.
In case of a disaster, they CAN'T restore their environment because their whole systems is down and they don't have access to those files.

What is the best way to prevent such a scenario?

-Daniel.

 

[smajl]

You should store those files off site. On ftp, or somewhere. We send devconfig and volhistory as email attachement to TSM admin team (mail services not provided by servers on-site)

 

[LED888]

Starting with TSM Server 6.1 , the volhist and the devconfig file are much more important than TSM Server 5.X. Without the these two files your not going to be able to recover the TSM Server 6.X or newer.

With the TSM Server 5.x, if you happen to know the volume(s) that contains the DBB you can still able to restore the database. That was the good old days.

With the TSM Server 6.X and newer, the volhist and the devconfig are needed to restore the database. Knowing just the DBB volume name is not enough to restore the database.

In the dsmserv.opt file, there are two parameters, vohist and devconfig that point to where the files are located. You can have up to 3 locations.
I set one local location, and the other two on an NFS file system.
When the admin schedule run the backup volhist and backup devconfig, the out put are written to three different location.
The volhist and the devconfig are small enough where you can also stored on a thumb drive.
Of course, need to keep a current copy of the volhist and devconfig.


Good Luck,
Sias