Video Screencast Help

Does SLP has flexibility to run replicaqtions at a particular time

Created: 08 Jan 2013 • Updated: 18 Jan 2013 | 10 comments
This issue has been solved. See solution.

Hi Guys,

  I have a 24*7 backup environment in frequency based backups. Now I ought to change it run only in non production hours. As I have data domain at back hand and it has certain limit on I/O streams it can have, So I want during the non-production hours all my streams should be used by backups and doesn't gets compromised by replication using any stream and then in production hours I want all the replication to run. Is there is fleixibility in SLP. As in any parameter in LIFECYCLE_PARAMETERS file for replications.

Please help me out with a possible options I have with SLP.



Comments 10 CommentsJump to latest comment

Will Restore's picture

See Marianne's post in this recent thread

"SLPs cannot be scheduled or controlled. It is designed to run duplication as soon as possible after the backup. Future NBU releases will probably have SLP scheduling feature."

Will Restore -- where there is a Will there is a way

mph999's picture

I bellieve this feature is under consideration for a future release.


Regards,  Martin
Setting Logs in NetBackup:
Nicolai's picture

You can write a script to enable SLP processing in the morning and disable them when the backup windows opens.

nbstlutil inactive -lifecycle <lifecycle name> -wait
nbstlutil active -lifecycle <lifecycle name> -wait
For scripting you need to use the "-wait" parameter

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Sid1987's picture

Hi Nicolai,

Just make me understand more about when you say we disable the SLP during backup window. Will the backups configured in SLP run, and there will be track of which one's have already run so that when we enable the SLP it will pick the backups which ran when SLP was disabled and duplicate them.


Sid1987's picture

Hi Nicolai,

One more question, what is priority between a same priority backup and duplication job, which will take the drive first?


Fabrice P.'s picture

Yes the backups will run.

You can check the images in replication pending state for a particular SLP using this command:

nbstlutil stlilist -U -image_incomplete -lifecycle [SLP NAME]

Authorised Symantec Customer ;)

Sid1987's picture

Ok the backups will run and will there be a track to catch up the backup images when SLP was disabled to duplicate them when SLP is enabled?

And what about the priority between a backup job and duplicate job?


Fabrice P.'s picture

For the first question, yes.

About priority, there is the priority of the backup job itself (configured on the backup policy). The prority of the duplication process is defined in the SLP ("priority for secondary operations").

If 3 jobs let's say backup/duplication/restore have the same priority level, I believe restore will go first, then backup, then duplication but i'm not 100% sure.

Authorised Symantec Customer ;)

Mark_Solutions's picture

Making an SLP inactive does not affect the backup stage - just the "lifecycle" of the duplicated images so not duplications or replications will run.

Once made active again it will start to run all images that are waiting for their lifecycle to complete (duplicate / replicate)

Priorities can be set in the policies and SLPs and all defaults can be set in the Master Servers Host Properties.

A simple cron or windows scheduler job could be used to run the script / batch file with the commands in to control the SLP behavoir

Authorised Symantec Consultant . Expert Partner.

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Genericus's picture

I use this and it works fine - I use cron to inactivate SLP policies to allow the tapes to clear before vaulting, then reactivate them after vault.

Please note - the SLP decision tree does not use priority only. If you have a bunch of SLP waiting to run, it will check to see if the source tape is in use (because it can't load it to read, if it is busy writing), it will also check to see if a particular media server/tape combination is already active. Then it will use priority.

For example, if you are duplicating an 1 year tape via media server1, and you have two duplications queued:

one for 1 year on media1 at 100 priority, and one for infinite on media2 at 500 priority

The duplication for 1 year on media server1 will go next, since the tape is already loaded.

NetBackup on Solaris 10
EMC Data Domain 990 & 7200 VTL via FC
acsls 8.3.0
SL500 & SL8500 LTO5