Aller au contenu principal

New install - The host is unreachable ...... But it lies!!!

Thread needs solution

Dear Acronis,

I have just done a rebuild on our machine that looks after backups, using Windows 7 Enterprise, 64 bit.

I have various mapped network drives to our fileserver which all work without any issues at all.

Last night I did a fresh install of Acronis backup, and configured it to backup one of the mapped drives: \\fileserver\shares

This morning I was presented with the following in the log:

Error code: 7
Module: 4
LineInfo: 5b75ea8b7ea6a998
Fields: $module : disk_bundle_vs_43956
Message: The host is unreachable. Trying to reestablish network connection...
--------------------

I have triple checked all the shares/mapped drives, and there is no issue with them at all. All had remained connected and accessible throughout the night.

This has been confirmed by looking at the Synology NAS box where the share originate.

Could you please assist?

Thanks

Fichier attaché Taille
log.zip 1.79 Ko
0 Users found this helpful

Hello Graeme,

Network shares are mapped exclusively for a specific user and not as a general OS-wide level. The behavior you describe is probably related to this: the drives are mapped using credentials that are different from the credentials used by our services for backup.

In this case, the mapped drives would effectively not exist from the point of view of our services, which would lead to the errors you describe.

I would suggest using the UNC share paths directly: put \\fileserver\shares in the "where to backup". This configuration is much more stable. If this is not possible, could you please explain why? What do mapped drives offer (for backup purposes) compared to direct network share access?

Thank you.

Many thanks for the quick reponse Igor.

I should of mentioned in the post that I did input via its UNC share path and not via the mapped drive, in actual fact the mapped drives don't show up in the application.

I have just changed some permissions on the NAS box where the shares are, and running a quick backup now to see if that resolves the issue.

Regards

Graeme