cancel
Showing results for 
Search instead for 
Did you mean: 

Windows Passive cluster node 'Shadow Copy Components' backup is failing with status 13

BalajiP
Level 3

Hi,

The Master Server NBU version 7.0.1 on Windows 2003 R2 Std. And the client server NBU version 7.0.1 on Windows 2008R2 Std. I have suggested the customer to upgrade the environment which will be delayed due to
critical legacy applications' compatibility. But, I need to fix this backup failure issue on high priority.

The backup of 'Shadow Copy Components' for passive node cluster is failing with status 13. This was getting backed successfullly when it was active node and started failing post fail over. Below are the error details available from detailed status of backup job.

31/07/2017 17:32:51 - estimated 2404041 Kbytes needed

31/07/2017 17:33:05 - connecting

31/07/2017 17:33:06 - connected; connect time: 00:00:01

31/07/2017 17:33:06 - begin writing

31/07/2017 17:33:29 - Error bpbrm(pid=201460) from client aaaaaa: ERR - Volume resolution error for (System State:\System Files\System Files)

31/07/2017 17:33:31 - Warning bpbrm(pid=201460) from client aaaaaa: WRN - can't open object: Shadow Copy Components: (BEDS 0xE000FECB: A failure occurred accessing the backup component document.)

31/07/2017 17:33:32 - Warning bpbrm(pid=201460) from client aaaaaa: WRN - can't open object: Shadow Copy Components:\Registry\Registry (BEDS 0xE000FED3: A failure occurred setting the Component backup status.)

31/07/2017 17:33:33 - Warning bpbrm(pid=201460) from client aaaaaa: WRN - can't open object: System State: (WIN32 -536805685: Unknown error)

31/07/2017 17:33:33 - Warning bpbrm(pid=201460) from client aaaaaa: WRN - can't open directory: System State:\Internet Information Serv (WIN32 -536805685: Unknown error)

31/07/2017 17:33:33 - Error bpbrm(pid=201460) from client aaaaaa: ERR - Error encountered while attempting to get additional files for Shadow Copy Components:\

31/07/2017 17:33:33 - Error bpbrm(pid=201460) socket read failed, An existing connection was forcibly closed by the remote host.  (10054)

31/07/2017 17:33:33 - Error bptm(pid=199048) socket operation failed - 10054 (at child.c.1294)     

31/07/2017 17:33:33 - Error bpbrm(pid=201460) could not send server status message      

31/07/2017 17:33:33 - Error bptm(pid=199048) unable to perform read from client socket, connection may have been broken

31/07/2017 17:33:36 - end writing; write time: 00:00:30

file read failed(13)

 Please let me know if any logs need to be captured to understand the issue. Thanks.

 

3 REPLIES 3

Thiago_Ribeiro
Moderator
Moderator
Partner    VIP    Accredited

Hi,

You are using nbu version no more supported..if were you I'll update this environment asap..Master/Media and clients..

So as this version no more supported, is difficult to find some documents (manuals), but you can find some articles that maybe can help you..

Take a look:

https://www.veritas.com/support/en_US/article.TECH161331

https://vox.veritas.com/t5/NetBackup/Error-13-when-backingup-the-Shadow-Copy-Components/td-p/150081

https://vox.veritas.com/t5/NetBackup/System-state-Shadow-Copy-Components-backup-failing-with-error/t...

https://vox.veritas.com/t5/NetBackup/13-file-read-failed/td-p/426784

I hope can help you.

 

Regards,

 

Thiago Ribeiro

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
There is absolutely no reason why you should still be on 7.0.1.

You can upgrade the NBU servers to 7.7.3 or 8.0 and W2003 clients to 7.6.1.2.
There were fixes for SCC in 7.1.x and 7.6.x updates.

VSS could also be the cause.
Microsoft had hotfixes when W2003 was still supported.

Your management should invest in replacing the legacy unsupported application.

The below blog was made for Windows 2008 mainly, but has helped me identify a lot of VSS issues/problems.

https://blogs.technet.microsoft.com/askcore/2010/06/18/reasons-why-the-error-enumeration-of-the-file...

There has also been a technote about the passive node failing on shadow copy components also for Windows 2008 but probably worth a look too.

 

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue