Invalid volume, Shadow Copy creation is assumed - SAFE Backup
If you get this warning within your backup set: "Invalid volume G:\ (Shadow Copy creation is assumed)" (could be a different drive letter) please follow these steps to fix.
First make sure you are on our most current client so post 8.3.0.30
Go to this location C":\Program Files\ then open the file that corresponds to your backup software, there will be a cb.opt file, and open the file in notepad.
Then modify the line " "com.ahsay.obx.core.backup.file.ShadowCopy.disableAddAllVolumes=" & put "true" after the equals.
Save the file.
Run a backup & it will be successful
Related Articles
Troubleshooting VSS errors – SAFE Backup
Disclaimer: VSS is an OS component, the steps mentioned below should only be performed by your system admin and/or after consulting Microsoft. We cannot take responsibility for faults caused by following the below steps. VSS error codes and their ...
Basic Troubleshooting Guide for VSS – SAFE Backup
Disclaimer: VSS is an OS component, the steps mentioned below should only be performed by your system admin and/or after consulting Microsoft. We cannot take responsibility for faults caused by following the below steps. This article provides the ...
View the debug.log files – SAFE Backup
You will only really need to view this in the case of a missed backup, as this log will tell you when the next backup will run. To view the scheduler log, open file explorer and go to the C drive, open Users and select the user account that the ...
Stop a running backup – SAFE Backup
If a backup is running and you want to stop it, open system tray and you will see the SAFE Backup icon, it will be spinning if the backup is running. Right click on this and go to “Stop Running Backup” – you will then need to select the set name that ...
"Invalid byte 1 of 1" error when opening the backup client - SAFE Backup
Guide for the steps to take if, when opening the backup client, you get a message that says "Invalid byte 1 of 1-byte UTF-8 sequence". This is caused by corruption in the .acb or .obm folder. Open file explorer and navigate to the .acb (single user) ...