Skip to main content

Backup to network share

Thread needs solution

When I try to specify a network share I keep getting prompted for cresentila. 

The device in question is an external HD attached to another PC in my network.  I can map a drive letter to it and read and write form the disk just fine.  Only True Image has a problem. 

Both PCs are running Windows 7 Pro. Both use the same userId and password. I tried entering hostname\userid but it says "connection failed"

Did True Image stop supporting backup to network drives? This did not happen on True Image 13.

 

Figured it out. When PC ALPHA wants to backup to a drive owned by PC BRAVO I have to specify ALPHA\userId not BRAVO\userId 

0 Users found this helpful

No, it's a bug in 5554.  There is a hotfix patch for this.  The problem is resolved in the new release of the NG version and should be implemented in the standard version of Acronis 2017 (perpetual or subscription) within a month as posted by Acronis employee Slava in a few other recent posts.

For now, you should grab the hotfix patch.

https://kb.acronis.com/node/59051

Resolution

  1. Replace TrueImage.exe and ti_managers.dll with fixed versions

WPSIII,

True there is a bug in network device authentication in the TI 2017 product that the hotfixes address.  I do not think these fixes will chnage anything for you however as you have found your answer already in which credentials you use to make your connection.

This is getting old.   My backups ran fine for several days. Now I get an error "Unable to create volume snapshot".   I completely ininstalled True Image 2017. Of course it wasn't fully uninstalled until I downloaded and ran the Cleanup Tool. Then I reinstalled and tried another backup.  It never asked me for my credentials but after an hour and a half it failed again with "Unable to create volume snapshot"

Will this patch to build 5554 address that?

I am seriously considering punting True Image and finding another backup pogram. Sure TI has lots of nice features but atually performing a backup is kind of important to me.

I believe the patch would work in your case.  

Please also be aware that there are remote share limitations in Windows as well.  You cannot have 2 sessions in Windows to the same remote device if using different authenticaiton to that device.

Example:

PC has mapped drive on NAS1 with public credentials (authentication session 1 to NAS1)

You then want to setup a backup in Acronis (or some other product) to NAS 1 using credentials (authentication session 2 to NAS 1)

= FAIL for second connection.

However, if all sessions ot the NAS use the same authentication credentials, you're good to go and the bug will be resolved with the patched files until the next standard 2017 update comes along (sometime this month we're told)

https://kb.acronis.com/node/59051

Resolution

  1. Replace TrueImage.exe and ti_managers.dll with fixed versions

 

I installed the hotfix but nothing changed.

I don't think this is an authorization issue.  When I run a backup to either my NAS, a USB attached disk or a local disk, it runs for a while (90 minutes) then fails with "Unable to create volume snapshot".    The disk I am trying to backup contains about 232 GB of data. 

I tried backng up a disk with a lot less data, about 14GB, and that works OK. 

I have another PC running the same version of Windows (7, Pro, 64 Bit)  and the same version of TI. It has no problem backing up a disk of similar size to the same target volumes.  (NAS, local or USB)

I got around the problem by disabling the Volume Shadow Copy service.  But that creates a different problem -- Windows  needs that to create a Restore Point. So unless anyone has any other siggestions I guess I'll have to remember to start the VSC service before applying any Windows maintenance.

 

 

 

How large is the total capacity of the disk you are attempting to backup?  I believe you are running into an insufficient disk space error with VSS.  Probably nothing wrong with VSS itself or True Image in this case as both would appear to be functioning correctly.

 

I have tried multiple scenarios:

Source 1 = 450Gb SSD, 233 Gb in use.  Target = 6Tb NAS with 2.8 Tb free - fails, Target  1TB internal HD, with  918 GB free - fails

Source 2 = 1TB internal HD, 326 GB in use, fails on both targets

Source 3 = 1TB internal HD with about 14Gb in use, backup succeeeds on either target device.

By disabling VSC, the backups complete but take a lot longer ~ 90 minutes vs 45

Meanwhile on another PC I am backing up another 250 GB  SSD, 182 Gb in use to that same NAS.  Works fine with VSC enabled.

 

Based on you being able to connect and the job failing after some time, I agree it's not a connectivity issue. Also since you can further prove it works without vss. You can disable vss just for the backup job and not the entire system. 

Https://forum.acronis.com/45832#comment-346558

i would normally say to start checking USB and power saver settings, but it sounds strictly like vss on this one system. Vss needs to build a snapshot on the local machine which uses cached space so needs it free.  Perhaps because you're creating one large tib, there isn't enough free space on this machine?

check out the ms thread as well. Might be onto something with not having enough space on the system reserved partition. Never considered that before, might be something to it as a lot of people who could not complete vss with local windows backups found they could backup after freeing up at least 40mb on that hidden partition.

https://social.technet.microsoft.com/Forums/windows/en-US/25deba76-464b…

 

In general it is recommended that you have at least 15% to 20% free space for shadow copies and any dis volume.  System Reserve partitiion should have a minimum of 42MB of free space.

You can verify free space on disk volumes by using Disk Management and in the top view looking at the Free space and 5 free columns. 

This is not a question of how much space is available on the destination target disk where your bacvkup is stored but rather the amount of free space on the disk volume being backed up.

None of the volumes being backed up are more than 60% full. My System Reserve Partition is 800 Mb.

Disabling VSS for the specific backup jobs seems to get around the problem, and I can still create System Restore Points. 

Thanks to all for your help

 

WPSIII:

Using your numbers, your System Reserved Partition has about 320 MB of free space. But depending on how accurate your "60% full" estimate is, could the free space on this partition be slightly less than 320 MB? A partition that is >500 MB needs to have 320 MB of free space for VSS to function.

From: https://msdn.microsoft.com/en-us/windows/hardware/commercialize/manufac…

part of this article quoted below(recommendations from Microsoft for the Recovery Tools partition, but the same principle applies for any partition being snapshotted by VSS):

"Recovery tools partition

This partition must be at least 300 MB.

This partition must have enough space for the Windows Recovery Environment tools image (winre.wim, typically between 250-300MB, depending on base language and customizations added), plus enough free space so that the partition can be captured by backup utilities:

    If the partition is less than 500 MB, it must have at least 50 MB of free space.
    If the partition is 500 MB or larger, it must have at least 320 MB of free space.
    If the partition is larger than 1 GB, we recommend that it should have at least 1 GB free.
    This partition must use the Type ID: DE94BBA4-06D1-4D40-A16A-BFD50179D6AC.
    The recovery tools should be in a separate partition than the Windows partition to support automatic failover and to support booting partitions encrypted with Windows BitLocker Drive Encryption.

We recommend that you place this partition immediately after the Windows partition. This allows Windows to modify and recreate the partition later if future updates require a larger recovery image."