Acronis True Image Causing unexpected Reboots 6008
have backups scheduled to run a 8PM on 2 different servers. Both servers had unexpected rebotos very close to these schedule backup job times and I believ it is related. Is there any known issues about this ?

- Log in to post comments

Server R2 Standard Edition Service Pack 2 Build 3790
Version: 9.5-8173
Our Acronis is pushed out with Kaseya
- Log in to post comments

I am experiancing same issue. I ran a backup manualy to verify. The server reboots suddenly durring the backup process.
I have a Server 2008 Standard SP2 (running SQL and TS) / TI Echo Server build 8203
I made a registry change that fixed this issue for a few days. I am experiancing this again today however.
The registry change was found on a 3rd party forum and is as follows:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\snapman\Parameters registry key;
- Add Parameters key if it does not exist yet;
- Add new DWORD Value;
- Set the new item's name to MaxSplitBlock and its value equal to 100 (decimal);
- reboot the server
------------------------------
I have updated acronis to build number 8353, but I have not tested with this build as this server is in a production environment and must wait till after hours to reboot.
I will post again if this fixes the issue.
James Lindsay
Senior Network Admin
Computers Unlimited
- Log in to post comments

I have tested using build 8353. Unexpected Reboot Problem remains.
The last Aconis log entry is "Locking Partition C"...
I see a new build of 8398. I will be testing this next week.
Any Idea's Aconis?
James Lindsay
- Log in to post comments

I have tested using build 8398. The Unexpected reboot issue remains.
I have talked with acronis support and they believe is has to do with "snapman" entries in the registry.
I have removed the "snapman 380" entries. I have also installed the SnapAPI update...
Nothing has resolved the issue as of yet.
James
- Log in to post comments

Well here is a new development for me.
I found a difference in the systems that I am running.
I have 2 systems:
1. Server 2008 X64 SP2 running Exchange and Acronis TI Echo Server build #8398 -(THE ACRONIS BACKUPS WORK LIKE A CHARM)
2. Server 2008 x64 SP2 running SQL 2008 and Acronis TI Echo Server build #8398 -(THE ACRONIS BACKUPS CAUSE SYSTEMS HARD LOCKS, BSODs, and SUDDEN REBOOTS)
----------------------------------------------------------
When I log into system number one (FUCTIONAL BACKUP) and run an elevated command prompt with the "vssadmin list providers" command it lists only two:
1.
Microsoft Software Shadow Copy provider 1.0
...
..
Version: 1.0.0.7
2.
Acronis VSS HW Provider
...
..
Version: 1.0
---------------------------------------------------------
When I log into system number two (NON-FUCTIONAL BACKUP) and run an elevated command prompt with the "vssadmin list providers" command it lists three:
1.
Microsoft Software Shadow Copy provider 1.0
...
..
Version: 1.0.0.7
2.
Acronis VSS HW Provider
...
..
Version: 1.0
3.
Acronis VSS SW Provider
...
..
Version: 1.0
-----------------------------------------------------
I am also getting numerous VSS errors in the event log when running Microsoft Backups on server number two.
Event ID 22 and Event ID 12292
Maybe the Acronis VSS or SnapAPI is wrong or corrupted on system two?
I hope this helps with a diagnosis.
I am going to remove acronis and its VSS providers from system two to see if that resolves the error in the event log and MS Backup. I will post what I find in the next few days.
James
- Log in to post comments