I have kind of an odd question. We have a VMware file server that has the primary data drive (D:) set to be compressed within Windows. During busy times where our system generates thousands of statements, the files server sometimes can’t keep up and we have problems. The plan to fix this is:
- Run a CommVault incremental backup of the virtual file server.
- Stop CommVault backups of the file server
- Create a new, uncompressed 8TB E: drive
- Shut down the application so nobody makes changes to the files.
- Run a script to sync the old, compressed D: to the new, uncompressed E:
- Unmount the existing compressed D:
- Rename the new uncompressed E: to D:
- Reboot the file server and check the “new” D:
- Bring the system online
- Complete a business test of basic functionality
- Run a full CommVault backup and enable regularly scheduled backups
Other than ensuring that CommVault does not attempt to run a backup while all the changes are taking place, I don’t think there’s anything special I need to do to ensure CommVault is happy. We have a history of how long full backups take so we’re aware that the last step will run for several hours.
Can anyone think of anything else I need to be aware of?
Thanks in advance.
Ken
