VSS failing backup - DFS

[DanielC1]

Hi all,

We have a problem that DFS optimized backup is failing.
Backup was configured regarding this tutorial: (https://www.veritas.com/support/en_US/article.HOWTO65638).

The problem is that there is about 16TB of data which take a long time to complete and about from 30 shadow copy objects will fail randomly at error #69 (invalid filelist specification). Error message:

Dec 11, 2017 11:51:52 AM - Error bpbrm (pid=23548) from client XXX.XXX.com: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - Estimate:-1 -1
Dec 11, 2017 11:51:52 AM - Error bptm (pid=26968) socket operation failed - 10054 (at ../child.c.1278)
Dec 11, 2017 11:51:53 AM - Error bpbrm (pid=23548) from client XXX.XXX.com: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.JBD - accelerator sent 0 bytes out of 0 bytes to server, optimization 0.0%
Dec 11, 2017 11:51:53 AM - Error bptm (pid=26968) unable to perform read from client socket, connection may have been broken

The Client is windows 2012 with windows deduplication and DFS-R applied. Both master and client have Netbackup 8.0 installed. Also on client side VSS writers looks good they are stable with no errors. VSS shadowstorage is Unbounded which means it is not limited, all shadowstorage is copied to Disk K: which is only for VSS shadowstorage.

No events on windows side.

Please let me know any hints/fixes which can help in this situation.

Thank you,

Daniel

[Lowell_Palecek]

The NetBackup Administrator's Guide Volume I contains additional instructions for when you are backing up a large amount of data. (Page 691 for NetBackup 8.0.) It begins with the following, then continues with instructions to exclude certain paths and include very narrowly defined paths.

>Configure one backup policy for each DSFR server, and in that policy specify only the replication
>folders. A policy for each host's replication data ensures that the DSFR data is backed up within
>a reasonable time window.

[Sujay24]

Hi Daniel,

Increase client read timeout value on Client and Media server:-

Admin console->Host Properties->Media Server->Select Media server used for DFSR backups->Timeout->Set Client Read timeout value to 3600, uncheck Use OS dependent timeout and Set File Brwose timeout to 300

Admin console->Host Properties->Client Server->Select Client server of whose DFSR backup is taken->Timeout->Set Client Read timeout value to 3600, uncheck Use OS dependent timeout and Set File Brwose timeout to 300

If again the backup fails with connection have been broken increase the client read timeout on media and client server to 7200

Add Client resiliency:-

Admin console->Host Properties->Master server->Resilient Network->Add Client name and On resilency