Oops I can agree with you, "Regular backups were never meant to act for
long-term storage."
Archive sound better but I didnt consider that two different management
classes would confuse..
How do you manage first day of the month??
//Henrik
"Stapleton,
Mark" To: [EMAIL PROTECTED]
<[EMAIL PROTECTED] cc: (bcc: Henrik Wahlstedt)
BEE.COM> Subject: Re: Backup definition
Sent by:
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
RIST.EDU>
2003-10-09
14:35
Please
respond to
"ADSM: Dist
Stor Manager"
From: Bernd Schemmer [mailto:[EMAIL PROTECTED]
>I want to implement the following backup definitions:
Create a fullbackup every 1st day of each month
Create an incremental backup every further day of the month
The fullbackup should be stored for 12 month; the incremental backups
only until the next fullbackup is done.
The fullbackups and incremental backups should go to the same storage pool.
How do I do this?<
Schedule regular backups every day. Once a month, schedule an archive with
365-day retention (which is the default archive retention). Easy to do. Do
not confuse the need for short-term backups with long-term archives.
An even easier method would be to do the regular daily backups, and create
a backupset once a month with a one-year retention. This method doesn't
require a pull of data across the network for the monthly backupset.
Don't be fooled about creating two different nodenames with two different
management classes, and all the confusion that goes along with that scheme.
Regular backups were never meant to act for long-term storage.
--
Mark Stapleton ([EMAIL PROTECTED])
-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.
