Recovers from Bootable Media fine, not from a push over the network
I am using ABR 11.5 that is sitting on top of 17 different domains with a router into each switch (properly configured).
I can successfully make an image of all these machines, but if I attempt to restore the machines using the Restore from the Management station, it will reboot the machine fine, load Acronis where the progress will sit at 15% for 5-10 seconds and then reboot back into the non-restored OS (Win7 32-bit on Dell 960s which uses a static IP). Once it works on those PCs it will be used to restore our Domain Controllers running Server08 64-bit on Dell T310s.
I made a bootable media disk, and it is working fine. The restore was successful.
What could I be possibly missing for the restore over the network?
Details about the ABR Management Station:
Dell PowerEdge 840 running Server2003 R2 SP2 with 262 GB RAID5 HD and 1 GB RAM.
Member of a Workgroup
Thanks!
It's looks pretty graceful to me. It comes up with the post script after it exits that initiates a reboot. I doesn't do anything funny like showing it was rebooted improperly. Here is the log of Recovery while be pushed. It acts as if it finished the recovery before the initial reboot out of the OS.
--------------------
Log Entry Details
--------------------
Type: Information
Date and time: 7/10/2013 1:19:43 PM
Backup plan: [None]
Task: MyRecover_1
Managed entity type: [None]
Managed entity: [None]
Machine: drop200.unit14.ovation.emerson.local
Code: 20,250,682(0x135003A)
Module: 309
Owner: administrator@UNIT14
Message:
Command 'Recovering volumes/Managing ASZ/Applying AUR' is running.
--------------------
--------------------
Log Entry Details
--------------------
Type: Information
Date and time: 7/10/2013 1:19:44 PM
Backup plan: [None]
Task: MyRecover_1
Managed entity type: [None]
Managed entity: [None]
Machine: drop200.unit14.ovation.emerson.local
Code: 20,250,683(0x135003B)
Module: 309
Owner: administrator@UNIT14
Message:
Command 'Recovering volumes/Managing ASZ/Applying AUR' has completed successfully.
--------------------
--------------------
Log Entry Details
--------------------
Type: Warning
Date and time: 7/10/2013 1:19:44 PM
Backup plan: [None]
Task: MyRecover_1
Managed entity type: [None]
Managed entity: [None]
Machine: drop200.unit14.ovation.emerson.local
Code: 9,371,652(0x8F0004)
Module: 143
Owner: administrator@UNIT14
Message:
To complete execution of the running task, a machine restart is required.
Additional info:
--------------------
Error code: 4
Module: 143
LineInfo: 68e1921aca694282
Fields: IsReturnCode : 1, $module : disk_bundle_vs_37608
Message: To complete execution of the running task, a machine restart is required.
--------------------
--------------------
--------------------
Log Entry Details
--------------------
Type: Information
Date and time: 7/10/2013 1:19:44 PM
Backup plan: [None]
Task: MyRecover_1
Managed entity type: [None]
Managed entity: [None]
Machine: drop200.unit14.ovation.emerson.local
Code: 66,556(0x103FC)
Module: 1
Owner: administrator@UNIT14
Message:
Data recovery From: bsp://acronis Backup type: Image Recovery of: Disks
--------------------
Attached is the Windows log file. Nothing out of the ordinary that I can see.
I'd check the following - first, as you are using centralized managed vault, perform restore with the archive stored in a personal vault ( on a network share or even on other partition or disk, not affected by restore, on the same machine. The suspicious thing is that 15% is the same percentage when is decides under Window that reboot is required. May be for some reason the reboot environment requires reboot too (though it obviously shouldn't)
Just as a clarification, I would put an image on say, a USB external drive. Using the Management Station, go to recover, select Data Path when , type in the IP to that machine and navigate to that drive to pull that image? Which would be localized to the machine. I certainly do appreciate your help.
In my initial reply I assumed that you connect to the machine you want to recover directly.
If you perform the recovery from the Management Server (connecting to Management Server and initiating recovery there, specifying which machine to recover to), you can't specify local vault, but instead it's worth trying to connect directly to the machine you want to recover and perform the same locally. In this case you can specify local letter of the USB drive, or network share where archive is stored, or even the same managed vault using bsp:// scheme . If the USB disk is attached to machine being recovered and is available as a shared resource under Windows, it won't be available during recovery in reboot environment.
Do you specify the same vault (I assume it's a centralized managed one, because of bsp:// prefix) when you recover (successfully) from the bootable media?
Yes I specify the same centralized managed vault to pull the image from on the bootable media.