Wow, what a thread...
Ok, I got the part about AD restore mode, but when I do a system state restore, am I not assuming that I have a 'fresh' system state to restore from? Does the snapshotting create a SS backup? If not, is that something else that needs to be accomplished?
Not to get off-subject of this thread, but this is real important info...
We have experienced the described server lockup issue on one of our servers the other day. What is interesting is that we don't have a Kaseya/backup agent on this server, it simply runs SQL 2000 and usesa retail version of Acronis True Image Server 9.1 (build 3677) that is scheduled to do an image backup of all partitions to a NAS nightly. Looking through the Acronis log it appears that the system locked up right after the backup started. The last log entry read:
"Locking partition C:..."
The following night the server backed up successfully.
I got a reply from John Nuttall concerning the lockup problem:
Author: john nuttall
Date: 2:28:16 pm 19-Sep-06
please see this information from Acronis Support
We have a workaround that is worth trying. At this point we surmise that
there can be a conflict with the HDD Controller.
The workaround will be to create a maxsplitblock key.
Here are the instructions:
1. Run regedit and find
"HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicessnapmanParameters" registry key:
2. Add "Parameters" key if it does not exist yet:
3. Add new "DWORD Value"
4. Set the new item's name to "MaxSplitBlock" and its value equal to "100" (decimal):
5. The workaround is completed:
Please reply back if the issue persists and we will continue investigation.
I did this for the 4 servers in question. Each time I had to create the Parameters key. Now I just wait and see.