The choice is yours ... use bpexpdate on the images or on the media.
NetBackup will adjust the other for you.
From the v5.1 unix command reference:
Changing the expiration can be done on a media ID basis or on an
individual backup ID basis. Changing the expiration date of a media
ID also causes the expiration date of all backups on the media to be
changed.
If you make the change via a retention level change rather than date,
the "-recalculate" operand is important:
Allows the expiration date of backups to be changed based on the
specified retention level or you can specify a new expiration date.
When the expiration is changed according to retention level, the new
date is calculated based on the creation date of the backup plus the
value of the retention level. The expiration can be changed for a
single backup, or for all backups for a particular client, policy,
or schedule type.
If the backup is on removable media, the expiration date of the
media ID in the media catalog is changed, providing the expiration
date on this command is greater than the current expiration of the
media ID.
Note: "Infinity" is a perfectly good date when using bpexpdate.
cheers, wayne
P.S. I've always changed image expiration, but since the doc says image
expirations change the media and vice-versa, I'm assuming NetBackup is
smart enough to change expirations of *other* affected media (when
images span media and you specify a media change).
Martin, Jonathan (Contractor) wrote, in part, on 6/30/2006 11:25 AM:
> This is a terrible idea all around but I've been ordered to freeze all
> offsite data for a legal discovery to come in some lawsuit my company is
> in. I've got a list of all offsite tapes, but how do I go about keeping
> that information in the catalog? I'm thinking bpexpdate them and set
> their expiration for infinity - but is that going to set all the images
> to that expiration date or just the media? I need to make sure that all
> the data on these tapes does not expire from the catalog.
>
|
