ourselves rolling back the TSM server 8 days. It think that 1 or
2 weeks is pretty standard for folks on this list.
Ben
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Paul Dudley
Sent: Monday, April 10, 2006 10:49 PM
To: ADSM-L@VM.MARIST.EDU
Su
eye has an
opinion too.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Paul Dudley
Sent: Monday, April 10, 2006 11:49 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Resend - Policy and DRP question
I sent this query a week ago but have not received
You should keep ALL of your copypool tapes offsite. You should keep TSM
db backup tapes offsite to match your 'del volhist'. You should set your
reuse delay for your offsite copy storage pool to match the length of
time you keep your tsm db backups, in your case 10 days. This last
requirement of g
I sent this query a week ago but have not received a reply back. I am
resending in the hope that someone can offer some advice.
We have TSM version 5.2
I have changed the standard policy so that we now keep the 10 latest
versions of each file rather than 7.
I have also changed our del volhist to
TSM is not tape-oriented: it is stored-object-oriented.
The copy storage pool contains an image of your primary pool(s)
according to the policies for the objects stored in the primary pool.
Your DR practices need to keep a copy of all data objects offsite,
not just a fixed number of tapes. You're
We have TSM version 5.2
I have changed the standard policy so that we now keep the 10 latest
versions of each file rather than 7.
I have also changed our del volhist to tod=today-10 where it was
previously 7.
I have been told that previously we had to keep the 7 latest copy tapes
and db tapes of
