Video Screencast Help

SLP tracking question

Created: 24 Feb 2013 • Updated: 21 Apr 2013 | 1 comment
This issue has been solved. See solution.

Windows 2008r2, NetBackup

Hello all,

I am using SLP to duplicate data between my primary and secondary DataDomains. I do this because the native DataDomain replication has burned me badly before, and I also dont have very much visibility (if any) into specifically what got duplicated and what didnt, hence, using SLP instead.  I know that it is preferable to have fewer SLP policies than many, but I'm running into a minor tracking issue. My SLP policies are only divided up between retention times, so I might have the clients in many different backup policies that have a 30 day retention, being replicated all under the same SLP policy, called DD1_to_DD2_30Days, for example. So, what happens is that when I look in the activity monitor, I see a huge list of SLP jobs with the same name, and I have to click through them looking at the job details, or get into the catalog and search for "copy 2" to see a particular duplicated job. What I would like to do is to not only divide the SLP jobs by retention, but also by client type, I.E, Unix, NDMP, CFS, Windows, VM's, Exchange, etc. So, I might end up with 20 to 30 SLP policies, once each are configured for type AND retention. Is this a feasible solution to help me better track which SLP job duplicated what data, or is there a better way to do that?

Thank you,


Discussion Filed Under:

Comments 1 CommentJump to latest comment

Nicolai's picture

I seee the issue you are having. 30 SLP is no problem - I got system with manny more.

Can bpimagelist do the job for you ?
bpimagelist has some options regarding SLP's  e.g.
-option LIST_COMPLETE_COPIES   Do not report fragments of a duplicate copy that is still in process
Reports only the images that the storage lifecycle has not completely processed. This option cannot be used with the stl_complete option
-stl_name storage_lifecycle_name
Specifies a storage lifecycle name to be used when you select images. Only images with the specified storage lifecycle name are selected.

Assumption is the mother of all mess ups.

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