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

Track logs and renaming policy

Created: 23 Jan 2014 • Updated: 13 Mar 2014 | 4 comments
This issue has been solved. See solution.

We have track logs and accelerator enabled and have just succesfully completed backing up a Netbackup client with a massive amount of data We however need to rename the policy and was wondering how that will affect the track logs as the policy name is included in the location of the logs ... Or is it just a simple case of renaming the policy and then renaming the folder path of the track logs on the client to correspond to the policy name ??

Thanks for all your help 

Operating Systems:

Comments 4 CommentsJump to latest comment

Riaan.Badenhorst's picture

It will say there is no previous accelerator backup and do the whole thing. I've not tried to rename the track logs. It might also depend on the naming in the puredisk database, not sure.

Try it with a test policy. Backup, rename policy, rerun (which will do all of it), rename policy and rename the track logs, rerun again.

Report back

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Mark_Solutions's picture

It writes the information to the de-dupe etc.

If you change the policy name and track log the backup will just fail with a plugin error

Sorry it cannot be done - unless you could also manipulate the de-dupe database - but you really dont want to go there!

#edit#

If you did rename the policy and the track log directory to suit and have found out it now does not work - you should find you can rename them back and it will still use the old track log

Authorised Symantec Consultant

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

yobole's picture

so you saying if I rename the policy a new tracklog will be created from scratch .. thats so not good !!!

Mark_Solutions's picture

Now here's a thing - but i dont suggest you do it!!!

The dedupe catalog structure is \databases\catalog\2\client\policyname\

If you run the new policy with the new name it fails, but creates the new directory structure with just the _dirpo_ file in it.

If you then copy all files from \client\policyname to \client\newpolicyname\ then the accelerator backup works with the renamed track log

So the reason for the failure is that it needs to look in the correct place within the dedupe database for it to work

Of course for this to work means potentiall corrupting your de-dupe database!!!! SO DONT DO IT !!!

Just to explain that it is not just the policy name and the track log name that matters, it is the de-dupe database location too.

Hope this clarifies things

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