Forum Discussion
CasparThorup
Level 3
Hi Peter,
We had a terrible time upgrading our appliances from 8.0 to 8.1.1 due to the conversion. My experiences were as follows:
- As long as the conversion process was in its initial stages <20-40%, backups would perform very poorly. This is partially due to the fact that fingerprints for incoming data needs to be converted on the fly. The jobs would sometimes complete, but more often than not they would not finish.
- We had a lot of VMware Accelerator jobs, which were failing in a large scale. This was caused by the issue above, which overloaded spoold and forced it to restart.
Our actions to mitigate these problems were:
- Disable any secondary SLP processing until conversion finished.
- Disable Accelerator for all VMware jobs, as the Accelerator proccesing is happening on the backup host (media server) as opposed to the client.
- Set the conversion mode to Fast, and let it run around the clock. Please note that if the spoold proccess crashes and restarts, then the conversion will default to normal again.
We have an MSDP pool of 186GB, which finished after less than two weeks.
I hope this might help you, its not an easy upgrade, but after doing the above actions we managed to get through it relatively unscathed.
Caspar
jjimenez2
6 years agoLevel 5
Hi how we know the status of msdp conversion? running background?
- Marianne6 years agoLevel 6
Hi jjimenez2
Have you read through this section of the Upgrade Guide?
About MSDP rolling data conversion
......
You can manage and monitor the rolling data conversion using the crcontrol
command. More information about its use is available.
See the NetBackup Deduplication Guide and the NetBackup Commands Reference Guide.
Related Content
- 13 years ago
- 10 years ago