For setting up schedules to do weekly full/daily incremental, go to the
IBM site and do a search on the following:
"Performing Full Client Backups with TSM"
The principle is based on a scheduled update to your copygroup MODE
settings.
If you need to be able to restore data up to two weeks ago, then configure
your management class/copy group criteria accordingly, maybe something
like this:
VEREXISTS=NOLIMIT
VERDELETED=NOLIMIT
RETEXTRA=15
RETONLY=15
15 is a nice number and helps in case there is a long weekend to deal
with, but hopefully you get the idea. For deleted files, you may wish to
alter VERDELETED and RETONLY.
You do not need to restore a primary storage pool volume in order to get
the data from the copy storage pool. Instead, updating the primary pool
volume's access to UNAVAILABLE or DESTROYED will do the trick; then TSM
will automatically try to mount the copy pool volume to restore the file
(if the volume is available to the library).
When it comes to managing backup versions, TSM does not use the media type
as a distinguishing factor. So there is no good way to hold data longer if
it is on tape than if it is on disk. When a backup version expires in a
primary pool, it also expires in the copy pool. In theory, you could keep
your TSM database backups for that longer period of time and make sure the
tape pool's REUSEDELAY setting is also set for that period of time. Then
if you want to restore an older version that has since expired in your
disk pool, you could restore the TSM database, and get the data from the
copy pool. But that is very ugly and such usage on a regular basis is
impractical, as database restore is intended for use only in an emergency,
such as if your TSM database has been destroyed.
With all of that said, I do not understand why you *must* manage your data
in this fashion. While it is possible to manage data this way, at least to
some extent, it does not exploit TSM's progressive incremental features,
and will increase the amount time and bandwidth needed to perform backups.
If this is being mandated because that is how other backup products work,
then perhaps you should consult with your local IBM account team to get a
better understanding of how to exploit TSM in your environment.
Otherwise.... c'est la vie!
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
Giedrius Jankauskas <Giedrius.Jankauskas AT MICROLINK DOT LT>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
02/20/2004 02:35
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L AT VM.MARIST DOT EDU
cc
Subject
Best way to do this
Hi there,
Could someone share their experience & knowledge on what would be the
best way to implement this type of backup enviroment with TSM ?
Situation :
1. unfortunately backups need to be weekly based (full on Sunday,
incremental till next Sunday). There is no way of changing that.
2. there are 2 types of physical storage : disk pool and tape pool LTO
library (LTO1 type tapes, 19(+1 cleaning) slots, single drive)
3. Each week the tapes will be taken offsite
4. data needs to be on both medias - disk and tape to ensure the
possibility of restore in case of library or disk storage failure (disk
media has enough space to store the backups of 2 weeks).
What would be the best way to do this ? I can simply create two storage
pools : diskpool and tapepool, set up tape as copy pool for disk pool.
My idea would be:
1. create diskpool, create tapepool (as copy pool for diskpool).
2. create schedules : a.) Sunday - selective backup, b.) weekdays -
incremental, c.) saturday - incremental.
How should expiration be setup ? I only need data for current, and
previous week. However, backups are mostly files generated by databases.
Therefore to restore any backup, the full backup of the Sunday is still
needed. So depending on a weekday I need files from 8 to 14 days old
(current week, and previous week).
With tape rotation it's possible to store more data on tapepool (just in
case) than diskpool. Is it possible expire older data on diskpool but
still have it available via tapepool ? Can this be done without the
backup client doing a double job : a.) Backuping to disk b.) backuping
to tape
Or is it better to backup files to diskpool, and then backup diskpool to
tapepool ? How would this work if disk storage failed ? As I understand
- I cannot restore files directly from a stgpool backup, I have to
restore the stgpool or volumes, and only then can I restore the files ?
Is it like this or am I missing something.
Maybe such weekly/periodic backup scenarios/solutions for TSM have been
documented and explained ? Since this backup implementation does not
follow tivoli's recommendations I haven't found usefull info in their
documentation on this subject.
Thank you for your time.
mailto:viny AT parkas DOT lt
|
