I have fixed it for the specific error as shown in this thread as below...It only took a month. Thx for the support VERITAS. NOT!
Team, had a niggling backup problem for the last month that came out of the blue one day. The following is the resolution should you ever get this error as was quite difficult to ascertain and repair.
1) you receive the following error:
- Backup - Shadow?Copy?Components Shadow?Copy?Components
A failure occurred accessing the Writer metadata.
2) Apply the following hotfix and reboot the server: (Note: This hotfix is only available from Microsoft through logging a call so I have put it into the following Unisys share).
- \\Aubne1-r1\Shared\TAFE QLD UNISYS\Ops SS\BackupExec\VERITAS_MS_Hotfix-833167\WindowsServer2003-KB833167-x86-ENU.EXE
3) You will then get a new error as below:
- Backup - \\SERVER1
OFO: Initialization failure on: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
VSS Snapshot error. Out of disk space or no NTFS volume found while creating snapshot. Add one or more NTFS drives that have at least 100 MB of free space for each volume that will be snapped.
4) Modify the backup job to only backup the system state as shown below:
5) You will also need to modify the root cause of the problem which is the fact that BE is registering that the shadow copy free space for drive C:\ is insufficient, even if it is disabled and not in use, which is quite bizarre but correct after numerous test backups, enabling and disabling etc:
- Set the size of the Shadow copy volume to > 100MB. As in the example I set it to 300MB and worked ok. Again Note: this is even though the shadow copy is set to disabledâ¦
This should resolve the issue and you should get 100% backups from then on in. I will also be posting to the Veritas website as there is no resolution yet on a huge forum article about this problem.