Re: [Veritas-bu] understanding Storage Lifecycle Policies
The SLP is where the retention period is set in this case, not the schedule. It can be a bit misleading because you still see the retention information in the schedule. If you think of the SLP as a series of destinations each with it's own retention, that may help. In your case if your retentions are tied to schedules, then you will need a set of SLPs with those various retentions, and each schedule will use a different SLP. The actual storage used in those SLPs might all be the same, e.g.: SLP1: Monthly - Backup to Disk (retain xx days), duplicate to tape (retain 7 years) SLP2: Weekly - Backup to Disk (retain xx days), duplicate to tape (retain 1 year) SLP3: Daily Inc - Backup to Disk (retain xx days), duplicate to offsite disk (retain xx days) These are not supposed to be useful SLPs, just an example. William D L Brown -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Sanders, Nate Sent: 03 January 2012 16:56 To: bob944; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] understanding Storage Lifecycle Policies Thanks for the clarification. One question I still haven't found an answer to is that the SLP is applied at the policy level, yet there are multiple schedules within the existing policies. How does this work out? If I have dailies, weeklies and monthlies, all with different frequencies and retention periods, what happens when I apply an SLP to the policy? -Original Message- From: bob944 [mailto:bob...@attglobal.net] Sent: Sunday, January 01, 2012 1:48 PM To: veritas-bu@mailman.eng.auburn.edu Cc: Sanders, Nate (DS) Subject: RE: [Veritas-bu] understanding Storage Lifecycle Policies > From: "Sanders, Nate" > > 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 different. 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. This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This e-mail was sent by GlaxoSmithKline Services Unlimited (registered in England and Wales No. 1047315), which is a member of the GlaxoSmithKline group of companies. The registered address of GlaxoSmithKline Services Unlimited is 980 Great West Road, Brentford, Middlesex TW8 9GS. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NDMP Backups on DataDomain.
You can do NDMP backups to OST via LAN transport to the media server. All you need to do is setup your ndmp credentials in NBU and on your NAS device. At least this worked for me with a VNX-File NDMP backup. If you want to transport NDMP backups via SAN to the DATADOMAIN, then you would need the VTL license/HBA on the datadomain. On 1/3/2012 2:28 PM, Anurag Sharma wrote: Hi Team, I have been given this task to move the NDMP backups from one master server to another. The current master server backups up NDMP to CDL (Clariion Disk Libraries) typical environment via SAN. Now the new master server has no TL/VTL/CDL its just has Datadomain used as netbackup openstorage device. Now my question is this . Do I have to procure VTL license from DATADOMAIN in order to do NDMP backups ? If I do NDMP backups to Datadomain open storage device will it have any performance implications ? Another point that crossed my mind is this : openstorage backups would be via LAN not via SAN would that reduce the speed of ndmp backups to great levels ? Anyone who has implement Netbackup NDMP backups on Datadomain please provide me with their valueable inputs. Regards Anurag ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] NDMP Backups on DataDomain.
Hi Team, I have been given this task to move the NDMP backups from one master server to another. The current master server backups up NDMP to CDL (Clariion Disk Libraries) typical environment via SAN. Now the new master server has no TL/VTL/CDL its just has Datadomain used as netbackup openstorage device. Now my question is this . Do I have to procure VTL license from DATADOMAIN in order to do NDMP backups ? If I do NDMP backups to Datadomain open storage device will it have any performance implications ? Another point that crossed my mind is this : openstorage backups would be via LAN not via SAN would that reduce the speed of ndmp backups to great levels ? Anyone who has implement Netbackup NDMP backups on Datadomain please provide me with their valueable inputs. Regards Anurag ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] understanding Storage Lifecycle Policies
Thanks for the clarification. One question I still haven't found an answer to is that the SLP is applied at the policy level, yet there are multiple schedules within the existing policies. How does this work out? If I have dailies, weeklies and monthlies, all with different frequencies and retention periods, what happens when I apply an SLP to the policy? -Original Message- From: bob944 [mailto:bob...@attglobal.net] Sent: Sunday, January 01, 2012 1:48 PM To: veritas-bu@mailman.eng.auburn.edu Cc: Sanders, Nate (DS) Subject: RE: [Veritas-bu] understanding Storage Lifecycle Policies > From: "Sanders, Nate" > > 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 different. 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. This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] understanding Storage Lifecycle Policies
We use SLP for our backups and copies. We create our original backups to a dd670 (2 weeks) and then spin off a copy to our remote dd670 with a different retention period (5 weeks). The SLP policy allows you to create a second copy to a different destintation right after your backups has completed. That way you have two copies of your data incase your primary site becomes disabled. If you are wanting to only have it on one device at a time, then the VAULT portion of Symantec will allow you to go back a certain amount of time and create a copy on the other destination. You could look into a ddArchiver from data domain. this will move data from an active tier to an archive tier within the same dedupe appliance and your data is on a less expensive tier of disk for the longer term. +-- |This was sent by rich.sav...@bcbsne.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] VBR and OpsCenter
Hi we have successfully migrated our VBR database over to Opscenter, saying that we did loose some reports. its pretty simple actually , when you do a new Opscenter install you can do a custom install, it will then ask you for a VBR database. in our case we pointed it to a backup we had made. from there on the install should be pretty straight forward. you will not see your data appear straight away as it will be importing them after the install. this can take days. Regs Zaka +-- |This was sent by hussa...@bupa.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
