Veritas Backup exec v15

Hi All,

 

I have received the below error during backup. I have ran the cmd VSSADMIN LIST WRITERS and found all writters are running normal without any errors. Any suggetion on the below.

 

Job ended: 08 December 2019 at 05:22:25
Completed status: Failed
Final error: 0xe000fed1 - A failure occurred querying the Writer status. See the job log for details about the error.
Final error category: Resource Errors

For additional information regarding this error refer to link V-79-57344-65233


Backup
V-79-57344-65233 - Snapshot Technology: Initialization failure on: "\\XXXXXXX.corp.root.global\System?State". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot technology error (0xE000FED1): A failure occurred querying the Writer status. See the job log for details about the error.

Check the Windows Event Viewer for details.

Writer Name: Background Intelligent Transfer Service, Writer ID: {4969D978-BE47-48B0-B100-F328F07AC1E0}, Last error: The VSS Writer ran out of memory or resources (0x800423f1), State: Stable (1).

Writer Name: File Server Resource Manager, Writer ID: {12CE4370-5BB7-4C58-A76A-E5D5097E3674}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during prepare backup operation (7).

Writer Name: System Files, Writer ID: {E8132975-6F93-4464-A53E-1050253AE220}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during prepare backup operation (7).

Writer Name: Windows Management Instrumentation, Writer ID: {A6AD56C2-B509-4E6C-BB19-49D8F43532F0}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during prepare backup operation (7).

Tags (2)
1 Reply
Highlighted

Re: Veritas Backup exec v15

Writer Name: Background Intelligent Transfer Service, Writer ID: {4969D978-BE47-48B0-B100-F328F07AC1E0}, Last error: The VSS Writer ran out of memory or resources (0x800423f1), State: Stable (1).

Above error indicates that VSS is not able to allocate enough memory required to create snapshot. Following steps may help,

1. Schedule the backup job when there is less I/O on disk. 

2. Run backup after production hours.

3. Run "Resource Monitor" to check if there is any other application on the server using lot of memory or generating lot of disk I/O.