Video Screencast Help

Storage Lifecycle Policies (SLP) Scheduling Windows Are Coming!- Help Us Finish Them

Created: 16 Apr 2012 • Updated: 26 Oct 2012 | 18 comments
Peter Imming's picture
15 Agree
0 Disagree
+15 15 Votes
Login to vote
Status: On Roadmap

 

Hello,
 
 
 
I know there have been a number of requests on the Ideas forum about Storage Lifecycle Policies. We just wanted to say "Thank You!" and that we are listening to them and activitly incorporating the suggestions as we can.
 
One of the most frequently asked for requests is being able to schedule Storage Lifecycle Policies and when the duplication will occur.
 
We are building this feature now.
 
It will allow you to have a duplication window, much like a backup window, that you can set for when the duplication jobs will occur after the backup is completed. We think this will meet the needs of being able to schedule duplications for large numbers of jobs.
 
Much like a backup window, the SLP window will have an "end time" of where no more new duplication jobs will be kicked off. 
 
Here is where we need your help.smiley
 
What would like us to do with your currently running Duplication SLP jobs that run past the "end time?
 
Here are the choices we have on the tabl
 
  1. Kill the Job (wherever it is when the Duplication window runs out)
  2. Kill the job after "X" hours past the Duplication window (basically allows the Duplication job to run for a set period of time post the close of the Duplication Window)
  3. Suspend the duplication job (whever it is when the Duplication window runs out, try to suspend the job. )
  4. Finish the current image, then attempt to suspend
  5. Finish the current image only if its already X % complete (for very large images that may take a while to complete before suspending the duplication job)
  6. Other- You choose

Our questions for you to consider are:

  • Which would be your preference for most of your jobs?
  • Are there any of the above that you would NEVER use?
  • Are we missing a key choice for you?

Thanks in advance for your time and input. We hope to be much more active on these Ideas posts going forward.

 

Sincerely,

Peter

Peter Imming, Sr. Product Manager, NetBackup

 

 

 

 

 

Comments 18 CommentsJump to latest comment

Bmitche's picture

I like all of the options listed....I like choices. Different circumstances will allow me to choose which option fits the situation at that time. When I switched from Arcserve to Netbackup late last year...I lost the ability to (easily)schedule the duplications....so it's nice to see it is finally being looked at. Thanks

+1
Login to vote
StefanosM's picture

I think that 4. finish the current image, then attempt to suspend, is ok. I prefer to keep it simple. 

+2
Login to vote
Kerry LeRoy's picture

Finish the current image would be great, and even better if you could limit it to images 75% complete or more.  Getting this feature added would prevent our Operators from having to kill hundreds of duplication jobs every day, while trying to avoid killing valid backups that may be running as well.  Thank you for finally getting to this feature.

+1
Login to vote
chack22's picture

Multiple options would be nice. Can we assume that suspending would be available via CLI or GUI so we could suspend on demand as opposed to only having the option available in a schedule?

+2
Login to vote
D.Peppas's picture

I agree with Kerry LeRoy , Finish the current image (note: finish the current image in the job, not the whole job) and then kill the remaining jobs.

0
Login to vote
Liliana Windver's picture

Hello

All choices looks great for the jobs that started and are in progress !!!

Would be there any option on having a possibility to force the SLP manually to bring jobs in NOT_STARTED mode ( mean not queued already) to queued/active/in progress ?

I have a customer that have a mixed environment of small and large images that need to be duplicated through SLP to a DR site ( copy 2,3,4 to disk and tapes) and according to SLP Best Practices document changing parameters influence the behavior but it's not solve it and the bottom line is that most of the time many jobs are in NOT_STARTED mode forcing client ( according to site SLA) to cancel and do the copies through GUI , not through SLP.

Besides several parameters we don't have any possibility to influence SLP behaior on when are good circumstances to queue and start the duplications .

The internal algorithm of decisions cannot let us influence the behavior and it's hard to find a good adjustment of those parameters without better understanding of internal decisions.

 

Regards

 

Liliana Windver

 

 

+2
Login to vote
RonCaplinger's picture

Is this going to be a system wide option, or will this be configured at the Storage Unit or Storage Group level, or is this policy or media server based? 

We use SLP's to back up to disk, replicate that data across a WAN using OST, and then duplicate to tape at the new location.  We would want to be able to schedule both the replications across the WAN and the duplications at each location separately and to have a choice of the options you listed above.

+1
Login to vote
Blobjung's picture

I run a similar process that Ron explained above.  I backup to a MSDP, duplicate to a MSDP at my DR site and then copy certain images to tape for retention requirements.  

The duplication from the MSDP to tape at the DR site will have a 24 hour window since the traffic will not be seen by the users.  

The MSDP to MSDP duplication across the WAN might be limited.  I would like to finish any images that have started and then hold any unduplicated images until the "window" opens again.  

I can see who all 5 options listed above could be used.

 

Thanks

 

0
Login to vote
Peter Imming's picture

Hi All, 

 

Thanks for the great and varied replies. We are still working through the delicate balancing act of providing you with the flexibility you need while still trying to keep it simple enough for all with the right defaults.

Based on the replies, here is what we are currently thinking as the choices and the defaults. We think this will work for most of your situations described above. Let us know how we did. 

Again, this is not a promise of delivery, just a discussion ;-)

Here would be the ordering and defaults of the choices for what would happen at the END of the Duplication Window to running Duplication processes. 

The concept is that these choices are "progressive" to allow you to gracefully control how to handle the duplication processes at the end of the window from least aggressive to most to help build a workflow.

 

1) Allow duplication job to complete current image past the end of the Duplication Window

1a) Allow to run "X" Hours past the end of the Duplication Window (the duplication will run for your designated number of hours past the end of the Duplication Window and then Suspend automatically to resume automatically during the next Duplication window)

1b) Cancel the duplication process at the end of the Duplication Window regardless of progress.

 

The real advantage of this model is that the new "Suspend" process will be graceful and will automatically resume without admin intervention at the next Duplication Window open.

How useful is it to have the ability to suspend manually from console and command line?

Will this work for your needs? Do you need the ability to Cancel vs. Suspend since Suspend will automatically resume from the pause.

 

Thanks in advance for taking the time to reply.

 

Peter

 

Peter Imming, Sr. Product Manager, NetBackup

Peter Imming, Sr. Product Manager, NetBackup, Symantec peter_imming@symantec.com

0
Login to vote
MSchmalfuss's picture

Peter,

 

Thanks for taking an interest in our needs!

Similar to others, I use SLPs to make a copy 2 at our Disaster Recovery site. I can see where suspending them could be very useful. In our environment we always let them run to completion because they don't impact out LAN and are limited in number so as not to use too many of our Data Domain streams at night.

For me, scheduling a start window would be great as it would allow me to maximize by backup resources during peak times and then begin the dupes a little later.

Anxious to see how this pans out!

 

Mike

0
Login to vote
Morten Seeberg's picture

Finish the current image, then suspend and continue when window opens again.

Running images should be allowed to finish, much like regular backup windows.

Did you restore something today?

0
Login to vote
Marianne's picture

The ability to suspend ANY kind of duplication job is what has been missing all along.

We hope that this feature will be extended to all forms of duplication (Vault, manual, etc...)

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

0
Login to vote
Genericus's picture

I would like to see the ability to assign individual lines seperate priority or start times...

 

So SLP

backup @ priority 2000

duplicate immediately @ priority 1000 - display in schedule column as DR copy

duplicate again at later time - @ priority 200 - display in schedule column as long term copy

 

I do not see a need to cancel, but I think more options are better.

I use scripted calls to active or inactive specific backupids to prevent SLP from running...

Currently it is is very tough to determine which section of the SLP is running - adding an option to name the sections like schedules show on the activity screen would be nice...

 

 

NetBackup 7.5.0.3 on Solaris 10
EMC 4206 VTL
acsls 7.3.1
SL8500 LTO5

+1
Login to vote
JasonP_76's picture

Hi Guys,

Any idea when this is going to be implemented / released ?

Thanks

0
Login to vote
Nicolas Horchower's picture

Hello,

Will this schedule will be SLP wise (like indexing job on index server), or will it be possible to setup the schedule per SLP ?

In this case, you should be able to let the admin setup how to handle the SLP end per SLP.

Today we use duplication to tape and also duplication between sites. Both needs different window, and also different ending (duplication to tape must complete, duplication between site can be suspended or stopped if too slow <60% done at the end of the schedule).

--
NH

0
Login to vote
StefanosM's picture

you can create as many schedules as you want and then assign one of them to a duplication job.

So yes, you can have a schedule per SLP if you want.

 

0
Login to vote
Nicolas Horchower's picture

Great, any ETA ? will it be in 7.6 or 7.5.x ?

 

--
NH

0
Login to vote
Justin Trouble's picture

My preference would be suspend the duplication jobs, as we have some huge duplications which take many many hours.

I'd avoid canceling jobs unnecessarily.

Suspending duplication jobs from the console and command line would be very useful.

0
Login to vote