Help deciphering a backup error log
Thread needs solution
Hello,
I have a machine (Windows Server 2011) that is persistently failing to backup to a Quantum RDX device attached to another server on the LAN, always with a similar error to that provided in the log below.
I'm not convinced the backup medium is at fault as there are 5 other servers being backed up to this device on a daily schedule, all of which have no such issues.
Would someone be able to shed some light on the cause of the error below?
Thanks in advance!
<?xml version="1.0" encoding="UTF-8" ?>
<log uuid="293C24C4-5450-486E-8965-D1AFC40145BF" product="Acronis Backup & Recovery 10" version="10.0" build="17552">
<event id="1" level="2" module="100" code="0" time="1318960975" message="VSS Mode:none" />
<event id="2" level="2" module="100" code="0" time="1318960975" message="Compression: 3" />
<event id="3" level="2" module="100" code="0" time="1318960975" message="Encryption:none" />
<event id="4" level="2" module="100" code="0" time="1318960975" message="Split: auto" />
<event id="5" level="2" module="100" code="0" time="1318960975" message="Multivolume snapshot:Disabled" />
<event id="6" level="2" module="1" code="1008" time="1318960976" message="<bold>Create Full Backup </bold><endl/><tabpoint value=30><indent value=4>From: <indent value=10><textcolor value="navyblue">NTFS (C:), Data (E:), Exchange (F:)</textcolor></indent><indent value=4><endl/>To file: <indent value=10><textcolor value="navyblue">"\\servername\budr\vol\165594578237930\VolBackup\20111018 19.00.10\volBackup.tib"</textcolor></indent><indent value=4><endl/><textcolor value=0x00ff0000>Password protected</textcolor><endl/>Compression: <indent value=10><textcolor value="navyblue">Normal</textcolor></indent><indent value=4><endl/>Exclude: <indent value=10><textcolor value="navyblue">Files matching mask</textcolor></indent><indent value=4><endl/>Match criterion: <indent value=10><textcolor value="navyblue">C:\Users\username.DOMAINNAME\AppData\Local\Temp\acr27E3.tmp, </textcolor></indent><indent value=4><endl/></indent>" />
<event id="7" level="2" module="100" code="0" time="1318961022" message="<bold>1. Creating partition image </bold><endl/><indent value=4>Hard disk: <indent value=10>1</indent><indent value=4><endl/>Drive letter: <indent value=10>C:</indent><indent value=4><endl/>File system: <indent value=10>NTFS</indent><indent value=4><endl/>Volume label: <indent value=10></indent><indent value=4><endl/>Size: <indent value=10>199.9 GB</indent><indent value=4><endl/></tabpoint></indent>" />
<event id="8" level="2" module="100" code="0" time="1318962142" message="<bold>2. Creating partition image </bold><endl/><indent value=4>Hard disk: <indent value=10>2</indent><indent value=4><endl/>Drive letter: <indent value=10>F:</indent><indent value=4><endl/>File system: <indent value=10>NTFS</indent><indent value=4><endl/>Volume label: <indent value=10>Exchange</indent><indent value=4><endl/>Size: <indent value=10>200.0 GB</indent><indent value=4><endl/></tabpoint></indent>" />
<event id="9" level="2" module="100" code="0" time="1318962730" message="<bold>3. Creating partition image </bold><endl/><indent value=4>Hard disk: <indent value=10>3</indent><indent value=4><endl/>Drive letter: <indent value=10>E:</indent><indent value=4><endl/>File system: <indent value=10>NTFS</indent><indent value=4><endl/>Volume label: <indent value=10>Data</indent><indent value=4><endl/>Size: <indent value=10>250.0 GB</indent><indent value=4><endl/></tabpoint></indent>" />
<event id="10" level="4" module="1" code="502" time="1318968249" message="Operation with partition '0-0' was terminated. Details: <indent>Write error. Error code: 0x70004 Tag: 0x9D2DE1F088CBC4D8 Error occurred while creating the file. Error code: 0x4000A function = "CreateFileNoCacheW", filename = "\\?\UNC\servername\budr\vol\165594578237930\VolBackup\20111018 19.00.10\volBackup3.tib" Tag: 0xF35F747B3B21F7EF The system cannot find the path specified Error code: 0xFFF0 code = 2,147,942,403 (0x80070003) Tag: 0xBD28FDBD64EDB8BC</indent>" line_tag="0xA164035B3FF39281" />
<event id="11" level="4" module="7" code="4" time="1318968249" message="Write error" line_tag="0x9D2DE1F088CBC4D8" />
<event id="12" level="4" module="4" code="10" time="1318968249" message="Error occurred while creating the file." line_tag="0xF35F747B3B21F7EF">
<field name="function" type="TIdentifier">CreateFileNoCacheW</field>
<field name="filename" type="TString">\\?\UNC\servername\budr\vol\165594578237930\VolBackup\20111018 19.00.10\volBackup3.tib</field>
<event id="13" level="4" module="0" code="65520" time="1318968249" message="The system cannot find the path specified" line_tag="0xBD28FDBD64EDB8BC">
<field name="code" type="TULong64">2147942403</field>
</event>
</event>
<event id="14" level="4" module="100" code="103" time="1318968249" message="Failed to perform the backup operation." />
<event id="15" level="4" module="100" code="0" time="1318968250" message="Operation is failed at attempt: 1" />
<event id="16" level="4" module="100" code="0" time="1318968250" message="Timeout before next attempt: 10 sec..." />
<event id="17" level="2" module="100" code="0" time="1318968260" message="VSS Mode:none" />
<event id="18" level="4" module="100" code="206" time="1318968260" message="The file name, location or format '\\servername\budr\vol\165594578237930\VolBackup\20111018 19.00.10\volBackup.tib' is not valid." />
<event id="19" level="4" module="100" code="4" time="1318968260" message="Write error." />
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 27
Comments: 1940
Ok thanks. Well it worked fine to an alternate location on the same server and to a NAS, but would continuously fail when backing up to the RDX. However, we moved the RDX to a different server and it began to back up correctly to it.
I believe the reasons for this are (these are still under investiation) that there is an issue with SMB1 & SMB2 between Windows Server 2003 and Windows Server 2008 R2 and 2011 boxes, where the microsoft hotfix addressing this very issue has not resolved the problem.
Sad face.