Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

When I backup to a Synology NAS I get random verify errors. If I backup anywhere else it is fine.

Created: 31 Jul 2014 | 9 comments

I am somewhat stumped on this one. 

I run Backup Exec 2010 R3 on a Windows Server 2008 box. I use it to backup 3 2008 server boxes. Those boxes run up to about 20 hyperv virtuals.

I have no difficulty backing up to a variety of locations such as an LTO4 tape library or standalone phisical disk in a physical computer. However, when I back up to my new NAS I ALWAYS get a range of validation errors.

We recently purchased a Synology DS1813+ NAS and whenever I backup my virtuals it appears to back everything up but I always get this error on the verify stage:

Storage device "\\172.20.10.235\Backups" reported an error on a request to read data from media.

Error reported:

The specified network name is no longer available.

V-79-57344-33992 - The backup storage device has failed.

On our most recent backup it failed with this error:

Verify- VRTSRV::\\HyperVCluster1.IDS.com\Hyper-V?HA?VM\IDSDEV1Data for VRTSRV::\\HyperVCluster1.IDS.com\Hyper-V?HA?VM\IDSDEV1\C:\ClusterStorage\Volume1\IDSDEV1\IDSDEV1.vhd is corrupt.

Data for VRTSRV::\\HyperVCluster1.IDS.com\Hyper-V?HA?VM\IDSDEV1\C:\ClusterStorage\Volume1\IDSDEV1\Virtual Machines\FAED0FC6-C508-4D15-8696-8E8A83DDB44F.xml is corrupt.

Data for VRTSRV::\\HyperVCluster1.IDS.com\Hyper-V?HA?VM\IDSDEV1\C:\ClusterStorage\Volume1\IDSDEV1\Virtual Machines\FAED0FC6-C508-4D15-8696-8E8A83DDB44F\FAED0FC6-C508-4D15-8696-8E8A83DDB44F.bin is corrupt.

Data for VRTSRV::\\HyperVCluster1.IDS.com\Hyper-V?HA?VM\IDSDEV1\C:\ClusterStorage\Volume1\IDSDEV1\Virtual Machines\FAED0FC6-C508-4D15-8696-8E8A83DDB44F\FAED0FC6-C508-4D15-8696-8E8A83DDB44F.vsv is corrupt.

Does anyone have any ideas? Is it possible there is some timeout issue when it gets to the verify stage? As I said, it appears to be backing up the virtuals and I can navigate to that share from the backup server with no problem at all.

Operating Systems:

Comments 9 CommentsJump to latest comment

lmosla's picture

try disabling antivirus programs running, the firewall or utilities that might be interfering with the job.

Do you have any Windows Event errors that occur during the backup job?

buck614's picture

Are you talking about on the backup server itself? The backup server has no issue backing up to an EMC VNXE, Hard drive in a computer over a network share, or an LTO4 robotic library. 

In either case the firewall is not turned on on the backup server and it is a dedicated computer with no other real services or roles other than windows.

I ONLY have an issue backing up to the NAS. There is nothing of note in the event viewer other than the Backup Exec job logs I provided above.

VJware's picture

Errors during verify mostly indicate an issue with the network or the hardware itself.

How are the B2Ds connected to the BE media server ? Is it via iSCSI ?

If your NAS is capable of disk write caching, I would recommend to disable it. Additionally, via the BE console, edit the properties of the B2D and ensure the option to preallocate space is disabled.

Try recreating the B2D on the NAS as well.

As you mentioned you always get an error while backing to this NAS. Have you tried to further isolate the error. For egs, have you tried a non-GRT Hyper-V backup, a regular file server backup, a backup without verify to this NAS ?

buck614's picture

Thank you I will try those suggestions.

One question though, where is this?:

Additionally, via the BE console, edit the properties of the B2D and ensure the option to preallocate space is disabled.

buck614's picture

The Hyperv's are located on an EMC VNXE NAS. The Hyperv's are connected to the 3 host computers via an ISCSi connection. The hosts have additional network cards that connect to the house network with a standard gigabit network connection.

The backup server is only connected to the house network. No ISCSI. The Synology is also only connected to the house network. No ISCSI.

Technically the backup server connects to the hosts over the house network and via that host computer communicates with the Hyperv viruals via the Hyperv agent. The backup server sends the backups to the Synology over the house network.

Soooooo, I don't think the Synology has any real interaction with ISCSI. Only the 3 host servers that run the Hyperv virtuals, and the EMC VNXE NAS that holds the VHD virtual files use ISCSI.

Would that eleiminate ISCSI Issues? If I backup those virtuals to a network share on a physical normal hard drive or an LTO4 tape I have no issues.

Does that make sense? 

Larry Fine's picture

Are all the backups targetted to the Synology backups of VMs?  I wonder if the problem is somehow related to the fact that they are VMs?

Have you tried backing up the BE server itself to the Synology NAS?  If that works, then we have some confidence in the Synology and the CIFS connection to it.

If you find this is a solution for the thread, please mark it as such.

buck614's picture

Yes, right now I am only backing up Hyperv's to the Synology NAS. I will back up something file based to the Synology NAS as a test and see if it works.

pkh's picture

Check that your NAS is not formatted to 4k sector sizes which is not supported until Server 2012.  See this

http://stackoverflow.com/questions/9465451/how-can...

If it is formatted to 4k sector size, then you need to reformat it to 512e sector size.

buck614's picture

I think it is 512. Here is the output:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\idsadmin>fsutil fsinfo ntfsinfo i:
NTFS Volume Serial Number :       0x00802e41802e3e12
Version :                         3.1
Number Sectors :                  0x00000001d1bcafff
Total Clusters :                  0x000000003a3795ff
Free Clusters  :                  0x000000001bfd1ddd
Total Reserved :                  0x0000000000000000
Bytes Per Sector  :               512
Bytes Per Cluster :               4096
Bytes Per FileRecord Segment    : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length :           0x000000004cd00000
Mft Start Lcn  :                  0x00000000000c0000
Mft2 Start Lcn :                  0x0000000000000002
Mft Zone Start :                  0x000000001e032fe0
Mft Zone End   :                  0x000000001e03f800
RM Identifier:        8FF2EA7F-1764-11E4-B5C7-001FBC026BAD