08-18-2010 06:56 AM
02-24-2011 07:28 PM
Did you ever get a reply?
We are doing the same plan, and looking into converting to SLP
02-24-2011 07:46 PM
Yep, It is three different SLP, or if you decide to keep the daily and weeklys for the same period, you would only need 2. We are looking at a 5 week retention to give a guarantee of 28 days of restoration for ever server. That would be the SLP defined to the policy level. The weekly we would do another SLP that would keep the monthly on disk for the first period and the second copy on tape for the final period.
Are you doing this on one data domain or do you have 2 that replicate. If you could give me the guidelines, I could mock one up and post screen shots..
Thanks
Mark Henderson
02-24-2011 07:58 PM
Just 1 Domain... I am still old school, by creating 3 diffrent backup policy for each server (INC\Daily, Full\Week, Full\Month)
For each one of those, is traffic on the network..
If SLP can limit the traffic to the FC (Disk toTape) this will be a good idea.. (I think this is how SLP works)
02-24-2011 08:40 PM
We re looking to reduce traffic on the network to the clients by implementing synthetic fulls where ever possible. The synthetic can then be ran out to tape from the data domain. If you do 3 policies you are missing out on the easy synthetics. SLP is persistent and does not really make it easy to schedule when the next step will run. We designed the new environment to cope with it. Every thing will land on disk first. Most things will never leave disk (but SLP will duplicate them to another site) The intention is that only long term retention will even hit tape. There will be exceptions but we are planning to reduce the amount of data to the tape significantly.
Mark
02-24-2011 08:49 PM
PLEASE don't create separate policies for full's and incrementals - this will result in incrementals running as full.
Create ONE policy with multiple schedules.
See: http://www.symantec.com/docs/TECH66214
08-09-2011 01:58 PM
We have cut over all of our RMAN to SLP backed Advanced Disk, as well we have all of our daily differential hitting adv-disk and the being duped by SLP.
I'm still working out all the kinks for the DSTU's and making sure we get the dups onto tape.
To answer the question, we seutup an SLP per policy, schedule, which seems to work really well so far.
e.g.
System_Full_Prod Runs once a month Directly to tape
System_Cumu_Prod Runs once a week Directly to tape
System_Incr_Prod Runs daily This is sent to disk and then duped
We don't yet posses the resources to backup 300 TB to disk and haven't invested in dedup just yet.
Come on October 1.
Chris
11-11-2011 05:07 AM
What about Oracle Rman databases backup. We have to specify a script in the job selection, so we have to create a new policy for each method (full, inc).
Does this means the inc is running full?
11-12-2011 05:41 PM