Backup to NAS blocks with error : 0x00040001+0x00040001+0x0000FFF0+0x80070040
Hi,
One of my backups to a NAS server repeatedly blocks with error 0x00040001+0x00040001+0x0000FFF0+0x80070040 and asks to retry or quit.
Retrying gaves same error.
This error seems to be unknown in KB.
This backup saves ProgramData folder. This may be related to problem since Acronis database is in there.
Thanks for help, this backup was added to save Acronis data !


- Log in to post comments

Thanks, Steve
<?xml version="1.0" encoding="UTF-8" ?>
<log uuid="BE0DE008-A467-4DBA-A463-0450939937E1" product="True Image" version="19.0" build="6027" task="6979941A-C8FC-4EC1-9645-57CF02636EB1" task_name="ProgDataLG" >
<event id="1" level="2" module="100" code="0" time="1458587649" message="Backup reserve copy attributes: format tib; need_reserve_backup_copy false; " />
<event id="2" level="2" module="100" code="2" time="1458587649" message="Operation ProgDataLG started manually." />
<event id="3" level="2" module="100" code="0" time="1458587649" message="Operation description: Stage Description." />
<event id="4" level="2" module="100" code="0" time="1458587650" message="Backup reserve copy attributes: format tib; need_reserve_backup_copy false; " />
<event id="5" level="2" module="316" code="0" time="1458587650" message="Opération : Sauvegarde" />
<event id="6" level="2" module="100" code="11" time="1458587650" message="Priority changed to Low." />
<event id="7" level="2" module="11" code="1008" time="1458587745" message="<bold>Créer une archive de sauvegarde</bold><endl/><tabpoint value=30><indent value=4>Depuis :	<indent value=10><textcolor value="navyblue">C:\ProgramData\ </textcolor></indent><indent value=4><endl/>Vers le fichier :	<indent value=10><textcolor value="navyblue">"ProgDataLG_inc_b1_s2_v1.tib"</textcolor></indent><indent value=4><endl/>Compression :	<indent value=10><textcolor value="navyblue">Normal</textcolor></indent><indent value=4><endl/></indent><endl/>" />
<event id="8" level="2" module="100" code="0" time="1458587759" message="Écriture d'une version incrémentielle sur le fichier : ProgDataLG_inc_b1_s2_v1-2.tib" />
<event id="9" level="2" module="4" code="1" time="1458587784" message="Une erreur s'est produite pendant la lecture du fichier." line_tag="0x1D8EAB676A3F695B" >
<error>AQEABABbaT9qZ6uOHVVuZSBlcnJldXIgcydlc3QgcHJvZHVpdGUgcGVuZGFudCBsYSBsZWN0dXJlIGR1IGZpY2hpZXIuAFBhdGgAVwAkbW9kdWxlAE4AAAAAAAAAAAABAAQAXSCxn9ws63xVbmUgZXJyZXVyIHMnZXN0IHByb2R1aXRlIHBlbmRhbnQgbGEgbGVjdHVyZSBkdSBmaWNoaWVyLgBmdW5jdGlvbgBBUmVhZEZpbGUAJG1vZHVsZQBOAAAAAAAAAAAA8P8AAPS47WS9/Si9TGUgbm9tIHLDqXNlYXUgc3DDqWNpZmnDqSBu4oCZZXN0IHBsdXMgZGlzcG9uaWJsZQBjb2RlAE5AAAeAAAAAACRtb2R1bGUATgAAAAAAAAAAAA==</error>
</event>
<event id="10" level="2" module="4" code="1" time="1458587784" message="Une erreur s'est produite pendant la lecture du fichier." line_tag="0x7CEB2CDC9FB1205D" hide="1" />
<event id="11" level="2" module="0" code="65520" time="1458587784" message="Le nom réseau spécifié n’est plus disponible" line_tag="0xBD28FDBD64EDB8F4" hide="1" />
<event id="12" level="2" module="4" code="1" time="1458587819" message="Une erreur s'est produite pendant la lecture du fichier." line_tag="0x1D8EAB676A3F695B" >
<error>AQEABABbaT9qZ6uOHVVuZSBlcnJldXIgcydlc3QgcHJvZHVpdGUgcGVuZGFudCBsYSBsZWN0dXJlIGR1IGZpY2hpZXIuAFBhdGgAVwAkbW9kdWxlAE4AAAAAAAAAAAABAAQAXSCxn9ws63xVbmUgZXJyZXVyIHMnZXN0IHByb2R1aXRlIHBlbmRhbnQgbGEgbGVjdHVyZSBkdSBmaWNoaWVyLgBmdW5jdGlvbgBBUmVhZEZpbGUAJG1vZHVsZQBOAAAAAAAAAAAA8P8AAPS47WS9/Si9TGUgbm9tIHLDqXNlYXUgc3DDqWNpZmnDqSBu4oCZZXN0IHBsdXMgZGlzcG9uaWJsZQBjb2RlAE5AAAeAAAAAACRtb2R1bGUATgAAAAAAAAAAAA==</error>
</event>
<event id="13" level="2" module="4" code="1" time="1458587819" message="Une erreur s'est produite pendant la lecture du fichier." line_tag="0x7CEB2CDC9FB1205D" hide="1" />
<event id="14" level="2" module="0" code="65520" time="1458587819" message="Le nom réseau spécifié n’est plus disponible" line_tag="0xBD28FDBD64EDB8F4" hide="1" />
<event id="15" level="3" module="316" code="1" time="1458587851" message="Terminated by user." />
<event id="16" level="2" module="103" code="0" time="1458587854" message="Le message électronique a été envoyé avec succès." />
<event id="17" level="3" module="103" code="0" time="1458587854" message="Batch operation has been terminated by user." />
</log>
Sorry it is in french. Looks like one of old backups is corrupt (read error) ?
- Log in to post comments

Jacques,
This is what I see in the Acronis log file.
8 | 2 | 100 | 0 | 1458587759 | Writing an incremental version of the file: ProgDataLG_inc_b1_s2_v1-2.tib |
9 | 2 | 4 | 1 | 1458587784 | An error occurred while reading the file. |
10 | 2 | 4 | 1 | 1458587784 | An error occurred while reading the file. |
11 | 2 | 0 | 65520 | 1458587784 | The specified network name is no longer available |
12 | 2 | 4 | 1 | 1458587819 | An error occurred while reading the file. |
13 | 2 | 4 | 1 | 1458587819 | An error occurred while reading the file. |
14 | 2 | 0 | 65520 | 1458587819 | The specified network name is no longer available |
15 | 3 | 316 | 1 | 1458587851 | Terminated by user. |
Question: Have you created an initial full backup for the ProgDataLG_full_b1... tib file?
The messages suggest you are trying to create an incremental backup based on the full backup image.
Does the full backup file exist on your NAS?
The 'error occurred while reading the file' suggests there is a problem in this area?
Are you running other backups successfully to the same NAS?
The specified network name is no longer available suggests a problem resolving the network resource?
If you are trying to backup only the ProgramData\Acronis folders then try creating a new backup specifying only those as the source folders rather than the whole of the ProgramData folder structure which may include other active application data from other programs running on your system.
- Log in to post comments

8 | 2 | 100 | 0 | 1458587759 | Writing an incremental version of the file: ProgDataLG_inc_b1_s2_v1-2.tib |
Based on the -2 in the file name, it looks like something went wrong with that incremental.
I usually would not suggest manually moving files, but in this case, I would as doinng this has helped me with similar issues (assuming it's not another networking error or the network location disks do not have bad sectors on them).
Copy those incremental backup files off of the original storage location manually with Windows file explorer (don't delete just yet though, just in case). b1_s2_v1-2.tib / b1_s2_v1-1.tib / b1_s2_v1.tib and anything else incremental that may have been created after that point so far for this particular backup.
After that, attempt to RECOVER from within the Windows Acronis application. It will immediately prompt a warning that files are missing and ask you to locate them or ignore them. IGNORE them until the prompts go away and that should update the database now that they've been moved.
Then run your backup job again and hopefully it will work as expected - you may end up wit a very large 1st incremental or a new full, but hopefully the backup will actually continue on if there are no other underlying issues with the network location. If it works, the real test will be to see if the next incremental looks alright after that too.
- Log in to post comments

There is a full_B1... file, but opening it with tib explorer runs ok for 1st levels but then crashes windows explorer.
Other backups to same NAS have no problem, the network share can be accessed.
There are other folders backups than Acronis in Progdata.
- Log in to post comments

The entire backup may be corrupt - not sure to be honest, but if it can't read the data in the full, that could be preventing the incrementals from being able to b made if it can't tell what has changed.
Do you have space enough to start a completely new backup task and let it run a new full to see how that goes and then monitor for the new incrementals?
If/when you have time, you may want to run drive diagnostics on your NAS (does it have its own tools built in?) to make sure the disk(s) are not dirty or failing. NAS is harder to trouble shoot because of the complextity of the network connections as well - dropped packets / connections during a backup could be a source of corruption too or limited NAS CPU/memory if it's too overloaded during a backup (say if the backup is large and/or other access like sharing media from it is taxing the system too much).
- Log in to post comments

Thanks.
The NAS should be OK, since other backups are.
I shall clone backup and start from a new full.
Good night.
- Log in to post comments

Clone backup was successfull.
Thanks
- Log in to post comments

Awesome, glad to hear it!
- Log in to post comments