Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

How to limit SLP replication?

Created: 08 Dec 2012 | 2 comments

Does anyone know how to successfully limit the number of SLP replication jobs, specifically when dealing with MSDP? I have read that by limiting the number of I/O streams on the target site, but this does not seem to work.

I have increased the minimum size of the jobs as a way to create fewer of them, but the bottom line is that eventually there are enough replication jobs to stop the regular backup jobs from running. I have noticed that replication jobs will reach a limit on the target, and instead of being queued, they are active against the source MSDP, sucking up an I/O stream, but not moving any data, claiming that the target has reached its limit.

I understand I can disable the SLP's during busy times, but I don't want that either, I just want there to be fewer jobs running. It seems my only viable alternative is to make the minimum job enormous to limit the number, but this doesn't seem like a good solution to me.

Some sort of limit to the number of replication streams should be available in the SLP. As wonderful as SLPs are, they really are lacking a lot of flexibility that would seem pretty straightforward from a design perspective.

Sorry for the rant, but anyone have any other ideas?

DT

Discussion Filed Under:

Comments 2 CommentsJump to latest comment

RamNagalla's picture

hi ,

i am sure, even for SLP duplication , you need to specify the storage unit and also that storage unit will have  the max jobs for limit, and you can restirict the number the jobs.....this will restict the number of active duplication jobs for the SLP .

hope this helps..

D Thomas's picture

Yes, that is what the documentation says, but it doesn't seem to operate that way. As I mentioned, on the source side the jobs still go active instead of queued, which doesn't make a lot of sense (at least to me).

You don't specify a storage unit with SLP with MSDP - you just wind up specifying target storage, which is the single deduplication pool on the target.

Also, I have two sources heading to he same target. So let's say I have a target with a limit of 30 streams, and I want to make sure that I only use 20 of them for Prod site 1, and 10 for Prod site 2, to make sure they both can meet their RPO, but I can't from the target.

If were able to set a limit of active streams from the source, I could do some sort of load balancing.

I had read in another post that some bigger changes are being made to SLPs in the future in terms of configuration, like creating job windows (I can't believe that doesn't exist already). Maybe I should move my posts to that forum.

Thanks for the insight.

DT