set up your policy domain for 27 or 28 days.  This will always ensure you
have a 3 week recovery window.  27 will do what is needed as long as you run
your full backups on a weekly schedule and do not miss any.

-----Original Message-----
From: Loon, E.J. van - SPLXM [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 19, 2002 8:23 AM
To: [EMAIL PROTECTED]
Subject: TDP for Exchange


Hi *SM-ers!
We are looking at TDP for Exchange for backing up our Exchange servers.
The backups should be kept for 3 weeks. I'm looking for a correct TSM policy
definition. The easiest way to do this is defining a backup copygroup with
retonly=21 and retextra=21. However, I think this is not save. A full backup
on day 1 will be deleted on day 22, so all incrementals after this full (day
2,3,4,5,6 and 7) are then also useless! So one cannot go back 3 weeks in
this case.
What is the best way to guarantee a 3 week retention?
Another small issue I detected: The TDP for Exchange manual states:
After the storage group and logs are successfully backed up, the log files
are deleted.
In our case there are always 4 log files left behind after a full backup. Is
that normal behavior?
Thanks in advance for any reply!!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential
and privileged material intended for the addressee only. If you are not the
addressee, you are notified that no part of the e-mail or any attachment may
be disclosed, copied or distributed, and that any other action related to
this e-mail or attachment is strictly prohibited, and may be unlawful. If
you have received this e-mail by error, please notify the sender immediately
by return e-mail, and delete this message. Koninklijke Luchtvaart
Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be
liable for the incorrect or incomplete transmission of this e-mail or any
attachments, nor responsible for any delay in receipt.
**********************************************************************

Reply via email to