5220 Rebasing

[PD001]

How often will Rebasing run on my 5220? is there a way to monitor other then crcontrol --rebasestate. I'm looking to see when it started and how far along it is in the process. Also can I be notified when it starts and stops? Maybe with opscenter?

Thanks

Pat

[INT_RND · Accepted solution]

I am not aware of an alert for this feature. You could make a script to monitor the status using:

cat /Storage/log/spoold/spoold.log  | grep Rebas

Rebasing happens due to a set of criteria and is not scheduled to happen at regular intervals. You can configure it to happen more or less agressively. Please refer to the PureDisk administration guide starting at page 180:

http://www.symantec.com/business/support/index?page=content&id=DOC5187

[SymTerry]

What version of NetBackup are you on? 7.6 does client side rebasing which happens on the fly. 

[RiaanBadenhorst · Accepted solution]

Hi,

There are quite a few scenarios when it will occur. Take a look at the note

http://www.symantec.com/docs/HOWTO89146

[PD001]

Thanks for the responses, one issue i'm having is I have a 6TB backup job that uses Accleleator and when written to tape with a SLP takes days. I see in HOWTO89146, that the NetBackup Accelerator backups do not pass through the MSDP backup process, so are they not getting deduped?

[RiaanBadenhorst]

Hi,

They are deduplicated, that comment just relates to rebasing and where and how it happens. The approach for accelerator must be slightly different that the rest of the deduped backups.

Is it only this one client/job that takes this long? How long does it take to backup?

[PD001]

This is the largest backup, it take 3 hours to backup , but can take 5 days to write to tape

[RiaanBadenhorst]

Maybe try and do a manual client rebase by adding the CLIENT_POLICY_DATE value to the pd.conf.

http://www.symantec.com/docs/HOWTO70533

[INT_RND]

This is because you cannot write deduplicated data to tape. The data must be rehydrated before a tape image can be made. Like everything, there are trade-offs. Pros and cons.

The alternative would be to write to a DSSU where you can simultaneously write images to MSDP and tape. This would make the initial backup take longer but the creation of tape would be faster. Also, the writing of images from DSSU to MSDP would be very fast. I'm not sure what sort of benefits you would see overall. You would have to perform a test to get a sample of the overall time from backup to tape close.