Q1:
You need two files also, the devconf and volhist files. In the devconf are
discriptions of the hardwareconfigurations and in the volhist is a list of
the usage of tapes (you can see it with q volhist).
So you can backup these files to floppy or email it to somewhere out of the
building.
Without the volhist, you need to know witch tape is the dbbackup or try them
all :-)
Q2:
I'm not experienced....... with DRM ;-) ........
Greetings,
Maurice van 't Loo
Compare Computers
The Netherlands
----- Original Message -----
From: "Wouter V" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 05, 2001 4:08 PM
Subject: Disaster Recovery and other questions
> Hello my dear TSM friends,
*** cut ***
> This works all OK, but if my TSM DB becomes larger than the capacity of my
> internal tapestreamer I will have a problem.
> That's the reason for the following question :
>
> I've seen that some of you do a db backup to a seperate tape in the
library,
> but :
>
> Question 1:
>
> If everything is destroyed (machine and library), and you didn't buy
DRM
> (so you don't have a script
> created by DRM to put everything back from scratch), how do you read
your
> DB back from tape ??? You need at least your
> TSM DB to restore your offsite copy. Or do you completely reinstall
your
> OS and reinstall TSM ? I almost
> can't believe the last thing because you still lost all the pointers to
> your data on the offsite copy.
> Or is there a way to read that tape directly from your OS through the
> special device name ? (for example
> tar xvf /dev/rmt3 ??)
>
> Question 2:
>
> Are there any rules to choose the exact size of the components in a TSM
> Server ?
> For example : - 25 Mb. RAM for each backupclient
> - TSM DB size = 10 % of totalcapacity to
backup
> - CPU : ???
>
> Question 3:
>
> - Can the experienced DSM'ers tell me some special advices ? What
> beginnermistakes did you guys made (and should I avoid)
> - What important reports can I make (I made a daily report to see if all
> the schedules were finished completely, and
> one monthly report to see how many times all the portables were backed
> up) ?
> - Any advices, tips, tricks ?
>