Backup Exec 16 VSS issues with server 2012 R2
I have a new setup with Backup Exec 16 installed on Windows Server 2012 R2 64-bit. Mostly working fine with 2 virtual hosts and an exchange server, and speed is good. However, we also have a new file server to back up which is experiencing some difficulty.
The server is running windows server 2012 R2 and has over 64TB of storage, so we initially ran into the error:
Final error: 0x8004230c - 0x8004230c (2147754764)
Backup - Snapshot Technology: Initialization failure on: "System?State". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).
V-79-10000-11223 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot technology that you selected cannot snap this volume. Some reasons for this could be:
- The snapshot provider that you selected does not support the volume that you are trying to snap. Try selecting the default snapshot provider, and then run the job again.
-A disk with a size greater than 63 terabytes or a 4K sector disk may exist on your computer. These types of disks can cause VSS to stop unexpectedly when it creates snapshot.
We reconfigured the storage in the RAID controller so that all disks presented to the OS are 62TB or less. All disks are also either 512 or 512E sectors.
After running a test backup, the error was gone. However, a week later after migrating data to the new server, the same error returned. Data backs up OK, but volume shadow copy is not used.
I've tried the following to resolve the issue:
* Rebooting the target server
* Removing and re-installing the remote agent, 3 times so far.
* Completely rebuilding the Backup Exec 16 server from bare metal.
There are no errors in any logs for VSS or VSC. vssadmin list writers shows no issues.(All writers present and stable) When the backup starts, the VSSVC.exe and VDS.exe services show up in task manager temporarily, but the system quickly falls back to normal file copies. VSS fails on all volumes and system state, not just the large ones. All other servers back up correctly.
Testing with Windows Server Backup, Veeam Endpoint Backup FREE, and just manually creating a shadow copy on the server all succeed.
The only thing I can think of is that the agent is timing out too early or testing for an issue and failing too quickly? I also don't know why the job succeeded once before more data was copied to the server.
For the 63TB issue you can create/adjust a registry key
http://www.veritas.com/docs/000024505
- however be aware that the 63TB is kind of a Microsoft recommended limit for VSS operations and as such using larger volumes and increasing this too far might introduce other issues (timeouts etc)
Also be aware that the way you calculate 63TB might be at fault as the limit is 57.3TB if using by 1024 multipliers/divisors
If it does not exist already you create it and as far as I know you do it on the server being backed up , however it won't harm to do it on both places.