Backup still hanging at 75% even after v17437

Only way i could kill the task was to stop the mms service. Naturally the service hung up while stopping, although it did kill the backup task. Now all my options to start/stop the mms service is greyed out.

I've use this command to kill the service from its hung up state: taskkill /f /pid "pid#here"

Now that the service is back up and running, I've attempted to perform another backup. Backup hangs at 0% now. I checked the task options and it cannot find the xml file for the task on my NAS device..

I can easily browse to the NAS and see the xml, but Acornis cannot find it nor does it prompt me for the network credentials.

FYI, I've uninstalled and re-installed build 17437 this morning..

Hi Jordy

This might be a silly question but have you tried backing up to another network share (not the NAS unit) or other local HDD to see if you have the same issues as yet?

Reason for the question is I’ve seen many customers have issues with Linux based NAS units and credentials/permissions and this might be the cause of the issues.

What else you can try and do is create a new NAS share with a new username (eg, Username: Acronis) when connecting to the network share in Acronis make sure you enter the username as NASNAME\USERNAME so it knows to authenticate as a local user on the Linux based nas and not via a domain. (eg, Username: NAS\Acronis OR 192.168.0.1\Acronis).

Create a folder from the Acronis interface to ensure the folder created is using the Acronis username then setup a new backup job this should help ensure no previous permissions are causing issues.

You can also check the permissions of the XML file you can see and mentioned above you might find the NAS unit has different permissions/users assigned for that file than what Acronis is using the read/write to the NAS unit.

With the tasks getting stuck at 0% make sure you don’t have any VSS errors/issues on the server or no HDD bad blocks or file system errors on your server... run a file system check on your server partitions and check the windows event logs for errors/details on what is causing the snapshot to fail.

Good luck.

Thanks for the reply.

Creating the Acronis user worked. All though, about a week later the backups starting hanging up at 4%. I cloned the backup task and changed the name of the xml. The backups started working again. Why are the xml files breaking? If I cannot use the old xml file, can i still recover my old backups?

Hi Jordy,
Thanks for the update and glad to hear things are working better with your NAS unit since creating a dedicated user. If you are still having some issues with backups hanging I would suggest looking into the network transfer speed throttling in your backup job. (http://www.acronis.com/support/documentation/ABR11/index.html#1291.html) We’ve also noticed with some lower end NAS units if you push too much data to them they can go offline, reboot, not respond in the require period of time..etc..etc. (many little issues like this)...

We have found if you reduce the network transfer speed in your ABR11 backup job it will not stress your NAS unit as much and give it time to keep up with the data being received. When a backup is running you can check what transfer speed you are getting to your NAS (eg, 60MB/s) then you can edit your Network transfer speed down to say 50% if you running on a gigabit network, this should also help stabilise your backups jobs.

Hope that helps, all the best!