Re: [Veritas-bu] understanding Storage Lifecycle Policies

2012-01-01 14:47:51
Subject: Re: [Veritas-bu] understanding Storage Lifecycle Policies
From: "bob944" <bob944 AT attglobal DOT net>
To: <veritas-bu AT mailman.eng.auburn DOT edu>
Date: Sun, 1 Jan 2012 14:47:40 -0500
> From: "Sanders, Nate" <sandersn AT dmotorworks DOT com>
> I'm reading through the SLP documentation but coming up a little
> short on understanding exactly how to accomplish a task. We have
> both LTO4 tape and a Data Domain 670. I would like to set a bunch of
> my data to go to the DD670 for 1 month, and then move to tape for an
> additional 2 months. This would give the data a full retention
> period of 3 months. But from what I am reading in the documentation,
> it sounds like it duplicate to tape as soon as it possible can, and
> then retain two copies at the same time. I do not wish this. I want
> only for the  data to exist on one device for 1 month, than the
> second device for an additional 2 months. How exactly does one
> achieve this with the SLP options in 7.0.1?

Your philosophy is not that of SLP designers.  Understandable, but

You:  backup to disk, make a last-minute copy to tape.

NetBackup:  backup to disk, copy to tape as soon as backup is
complete, don't let original expire before copy is successful, thus
guaranteeing you'll have you image until every copy has been made and
has then expired according to your specifications.

If you truly want it to work your way--only one copy exists at a
time--the easiest way to automate that would be to use Vault,
selecting disk images that are one month old and making a tape copy
with a two-month retention.  Along, of course, with whatever
procedures you were already planning for making sure that the original
image's expiration is extended in case of tape issues.

Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu