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

Have to kill SLP duplication jobs to support a DB restore

Created: 04 Oct 2012 • Updated: 18 Oct 2012 | 7 comments
This issue has been solved. See solution.

Hi,

We are using netbackup7.5 on linux,There is a DB restore of 6.5TB running and speed avgerages between 5-15MB/s whih is slow for our environment.I need to increase speed of this restore.Please let me know what can be done.Below is what I am thinking to do.

We have other DB backups and SLP duplications are running on same media server with good speed,I should not kill backups but can kill SLP duplications,

I see that SLP duplication jobs are at 80-90% complete and job overview shows many backup id's  after running for 11hrs.

Can I kill those SLP duplication jobs?

If I kill them will they start again from scratch,I mean what ever those jobs done in 11 hrs will go waste or it will start dupilcation for left images.

TO KEEP SHORT:If SLP duplication job which is duplicating 10 images is killed after some hours,What happens? 

Please let me know if I fail to explain what I have to say.

Thank you,

Naseer

Discussion Filed Under:

Comments 7 CommentsJump to latest comment

Marianne's picture

If you kill duplication job that is 80-90% complete, it will start from scratch when it is restarted.

It does not help you right now, but Symantec is planning on adding the ability to schedule and suspend duplications. See: https://www-secure.symantec.com/connect/ideas/storage-lifecycle-policies-slp-scheduling-windows-are-coming-help-us-finish-them

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

Mark_Solutions's picture

If in the job window you see a long list of images that it has duplicated then all of those except for the last one have completed and will not have to re-try - only the last one in the list which is the one in progress will need to be re-run

If there is just one image shown then that is the one on progress and will have to re-run from scratch

Hope this helps

Authorised Symantec Consultant

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

nasahasha's picture

Hi Mark,

You mean to say that backup image Id's will be added 1 by 1 to slp duplication job details and last one in the list is in progress and now if I kill the job only last id wil be rerun.

Thanks Marianne,

I just heard from my architects that symantec is adding new tabs to duplication jobs like suspend,finish,kill in 7.6

Mark_Solutions's picture

That is right - your LIFECYCLE_PARAMETERS file is use to specify the size of duplication jobs and this batches them together.

Some jobs may only have a single image but some small jobs can get grouped together into a single job.

As i undertsand it if you cancel that job it will only then fail the last image shown in the list as all of the others have actually completed

Authorised Symantec Consultant

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

SOLUTION
Abhijit Kulkarni's picture

If duplication job, that is duplicating 10 images, is killed in middle then images for which duplication is done, would not be retried. But image duplication that could not happen as job is killed, would get retried in next duplication manager session.