Aller au contenu principal

backup to NAS fails after 1st backup

Thread needs solution

True image 2018, fully up to date

I get repeat errors 

W000B007F: Error 0xb007f: The initial full backup version is not accessible at the moment

I am backing up to a WD EX2100 NAS drive at 02:30 

If I start the backup manually (say at 07:30) it always completes without error

The NAS is set never to sleep or power down

0 Users found this helpful

hmmm.....seems that my Acronis system report is 10 Mb so have uploaded it here   

https://drive.google.com/open?id=1RdCuRt-0MSwHAstgVlK0xkhxG-SbX_7T

should have added that I am backing up two hard drives on incremental backup

As stated, it ALWAYS works when I try it manually

The only thing I can think of is that the NAS has not woken up from hibernation in time for Acronis to find the file.

Maybe a pre-command that runs a batch file on the NAS, then a delay before the backup task starts.

Ian

Thanks for your prompt reply...but,as stated the NAS is on 24/7 and does not hibernate or sleep

When I used to hibernate the NAS overnight I did in fact run this simple batch file as a task a few minutes before Acronis starts to  ensure boththe PC and the NAS were ready.........I have tried running it despite no longer needing it but it made no difference

file :

del \\Wdmycloudex2100\pc\wakeup-nas.txt
copy D:\Misc_Updates\NAS\Wakeup-NAS.txt \\Wdmycloudex2100\pc

David, the detailed view of your backup log (from the report zip) shows the following:

07/09/2019 08:57:26 :974   +00:00 16284 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
07/09/2019 08:57:26 :974   +00:00 16284 I00640002: Operation NVMe Samsung SSD 970 2B2Q started by schedule.
07/09/2019 08:57:28 :103   +00:00 16284 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
07/09/2019 08:57:28 :105   +00:00 16284 I013C0000: Operation: Backup
07/09/2019 08:57:28 :106   +00:00 16284 I0064000B: Priority changed to Low.
07/09/2019 08:57:28 :121   +00:00 16284 W000B007F: Error 0xb007f: The initial full backup version is not accessible at the moment.
| error 0xb00eb: Network disconnected.
| error 0x40015: Network disconnected.
| error 0xfff0: The specified network name is no longer available
| code: 0x80070040

07/09/2019 08:57:28 :131   +00:00 16284 E000B03E9: Error 0xb03e9: Cannot open the backup.
| function: TrueImage::Archive::BackupArchiveOperationImpl::DoPrepare
| error 0xb00eb: Network disconnected.
| error 0x40015: Network disconnected.
| error 0xfff0: The specified network name is no longer available
| code: 0x80070040

07/09/2019 08:57:28 :158   +00:00 16284 E013C0005: Error 0x13c0005: Operation has completed with errors.

I have abbreviated the log detail to show just the key messages, but the bottom line is suggesting a network connection issue where the error code 0x80070040 is being returned by Windows.

Maybe just try updating the source and destination in the backup task... Even if they end up appearing exactly ly the same in the GUI. Can't hurt and may resolve the issue.

You mention that this backup successfully runs when started manually.  When do you have the backup scheduled to run?  If right after system startup, is it possible you have some network instability that settles down by the time you manually start it?  It would be interesting to see the results of a ping to the NAS issued from the ATI pre/post command option.

Bobbo:.... not quite sure what you mean / how to do this - I have deleted and re-created the tasks many times

 

Patrick:......Backup is scheduled to run at 02:30, as mentioned in my first post, 5 minutes before that happens the PC powers on and runs a small batch file to delete and re-copy a small file to the NAS - this is a throwback from the days when I used to power the NAS down overnight but I kept it running.......and surely as that runs it indicates the network connection to the NAS is good ?

Backup is scheduled to run at 02:30, as mentioned in my first post, 5 minutes before that happens the PC powers on and runs a small batch file to delete and re-copy a small file to the NAS - this is a throwback from the days when I used to power the NAS down overnight but I kept it running.......and surely as that runs it indicates the network connection to the NAS is good ?

David, when you run the batch file to the NAS, are you using the same credentials for the NAS that will be used by ATI to do the backup?  If not, that could be a part of the issue here.

The alternative here would be to use your batch file as a Pre Command for your backup task so that everything is being done using the same NAS credentials.

I am not KNOWINGLY using any "credentials" as such....I just connect to the NAS

David Faulkner wrote:

I am not KNOWINGLY using any "credentials" as such....I just connect to the NAS

Hmm. Is the share you are accessing a public or private share? If private, then you must be using Windows' saved copy of the credentials.

As I recall (and I could be very wrong), WD allows multiple users (with different credentials) to have access to the same share so the credentials Windows uses could be different than the credentials given to ATI.

David Faulkner wrote:

Ah, with that explanation it is a public share

Well, that makes it more puzzling (to me). Everybody uses the same credentials for a public share so there can be no conflict there ... unless you also have a private share on that same NAS.

Windows has a restriction that a user can use only one set of credentials to access a single NAS - either no credentials (for a public share) or one userid/password for a private share. (I think any number of shares can be accessed if the all use the same credentials.) If you open a connection to a public share, you cannot open a connection to a private share on that same NAS.

If this sounds like your problem there is a trick for circumventing it. Windows uses either an IP address or a DNS name to identify the NAS and doesn't do any cross checking. So you could use the DNS name to access one share and the IP address to access another share.

But I suspect this is not your problem.