Failure to restore from a tib file
I am running Acronis 11 build 8,101 on a Dell computer running Windows XP SP3 (up to date).
I want to use Acronis to always have a recent operating System (C: drive) disk as a full backup (so - one disk in computer, one recent backup as a reserve). This allows physical swap out to a very recent full operating system disk in case of a disaster, and has been very helpful in the past.
I had been accomplishing this task by utilizing the cloning feature of Acronis, but recently started to have some trouble with Acronis doing this approach.
I was advised (on this forum) instead to create a current .tib file and then create my "recent backup" hard disk from that file. This seemed quite convenient as I was able to schedule weekly .tib file images (in the middle of the night on Sunday night), and I could create my "recent backup" hard disks weekly from the .tib files without rebooting the computer, waiting for cloning to complete, concerns about power glitches during cloning etc.
At first this process appeared to work, but then it again gave trouble. Although Acronis apparently though that it had created a "recent backup" hard disk after running the "Restore" function, in fact no backup operating system disk was created.
I tried wiping the target disk, wiping and formatting, etc. but none of these measures seems to affect the outcome.
Sometimes I can create a "recent backup" hard disk, sometimes not.
One clue is that, in the case of failure to properly create a "recent backup" hard disk, the system reboots. In the case of successful creation of a "recent backup" hard disk, the system does not reboot - and the newly created operating system disk boots up and works fine when swapped out with the old hard disk.
Any help understanding this mysterious behaviour and what to do about it would be sincerely appreciated!
Robert Abbe
- Se connecter pour poster des commentaires
Robert, you stated:
"One clue is that, in the case of failure to properly create a "recent backup" hard disk, the system reboots. In the case of successful creation of a "recent backup" hard disk, the system does not reboot - and the newly created operating system disk boots up and works fine when swapped out with the old hard disk."
This may be due to the wrong destination disk being selected as the restore target. It the correct destination drive is selected, and is not the active OS drive, the system will not reboot to perform the restore. If the destination is the active OS (the drive that you are making backups from), then a reboot is necessary to restore the disk.
Be SURE to check which disk the restored image is being written to. From your description, it looks as though you may be occasionally restoring to your current active drive instead of the target drive.
- Se connecter pour poster des commentaires
Hi - thank for all the comments.
First of all, some background information on my system etc:
Mainboard : Dell 0YC523
Chipset : Intel 945P
Processor : Intel Pentium D 820 @ 2800 MHz
Physical Memory : 3072 MBDDR2-SDRAM
Video Card : AMD Radeon HD 6450
Hard Disk : PLEXTOR PX-128M5Pro (128GB)
Hard Disk : Seagate ST3250310AS (250GB)
Hard Disk : Seagate ST3250310AS (250GB)
Hard Disk : Western Digital WD3200AAJS-00RYA0 (320GB)
DVD-Rom Drive : SONY DVD-ROM DDU1615
DVD-Rom Drive : Optiarc DVD RW AD-7201A
Monitor Type : HannsStar HL269DPB - 26 inches
Monitor Type : Unspecified
Network Card : Intel PRO/1000 PL Network Connection
Operating System : Microsoft Windows XP Professional 5.01.2600 Service Pack 3 (32-bit)
DirectX : Version 9.0c (September 2006)
Manufacturer : Dell Inc.
Mainboard : Dell 0YC523
Bios : Dell Inc.
Chipset : Intel 945P
Physical Memory : 3072 MB DDR2-SDRAM
LPC bus : Yes
PCI Bus : Yes
Bus PCI-Express : Yes
USB Bus : Yes
SMBus/i2c Bus : Yes
Bus HyperTransport : No
Bus QPI : No
Bus CardBus : No
Bus FireWire : Yes
Processor : Intel Pentium D 820
Frequency : 2800 MHz - (current : 2792.95 MHz)
Number of Core : 2
Support : Socket 775 LGA
Data Cache L1 : 2 x 16 KB
Trace Cache L1 : 2 x 12 Kµops
Cache L2 : 1024 KB
FPU Coprocessor : Present
Core 1 Activity : 4%
Core 2 Activity : 13%
Current Display : 3200 x 1080 pixels at 60 Hz in True Colors (32-bit)
Number of monitor : 2
Brightness Adjustment : Yes
Monitor Type : Plug and Play Monitor
Video Card : AMD Radeon HD 6450
OpenCL : Yes
OpenGL : Yes
GDI Plus : Yes
Direct2D : No
Number of Disk Controller : 2
Number of USB-Disk Controller : 1
Number of Hard Disk : 4
Number of CD-ROM Drive : 2
Drives Letters :
Floppy Disk : 3½" HD (1.44 Mo)
Type ofmouse : HID-compliant mouse
Type ofmouse : Logitech HID-compliant Unifying Mouse
Type ofmouse : HID-compliant mouse
Type ofkeyboard : USB Human Interface Device
Type ofkeyboard : USB Human Interface Device
Joystick : None
HID Devices : Yes
Modem : Intel(R) 537EP V9x DF PCI Modem
TWAIN Device : CanoScan LiDE 210
TWAIN Device : Canon MP620 ser_000085F57E5C
TWAIN Device : WIA-Canon MP620 ser_000085F57E5C
TWAIN Device : WIA-CanoScan LiDE 210
TWAIN Device : WIA-CardScan 600c
WIA Device : WIA Canon MP620 ser_000085F57E5C
WIA Device : WIA CanoScan LiDE 210
WIA Device : CardScan 600c
Devices UPnP : 1
SCSI Host #0 : 4 Devices
SCSI Host #1 : 2 Devices
Bluetooth Device : Broadcom 2045 Bluetooth 2.0 USB Device
Bluetooth Device : Broadcom 2045 Bluetooth 2.0 USB Device
Bluetooth Device : Broadcom 2045 Bluetooth 2.0 USB Device
Bluetooth Device : Broadcom 2045 Bluetooth 2.0 USB Device
Bluetooth Device : Broadcom 2045 Bluetooth 2.0 USB Device
Drive : TEAC USB HS-CF Card USB Device
Drive : TEAC USB HS-MS Card USB Device
Drive : TEAC USB HS-SD Card USB Device
Drive : TEAC USB HS-xD/SM USB Device
Trusted Platform Module : No
All of that said, I ALWAYS create a full disk mode Backup, selecting the checkbox for the entire disk (not just individual partitions).
Also, I ALWAYS am very careful to restore to the target disk, not the current C drive (current boot disk).
Here is what I found:
The next time I tried to restore to a target disk, the operation aborted and my system announced that this was due to a file system error. I then rebooted to DOS and diskchecked ALL disks (no repair), including the target disk to which I wished to restore. There were no file system errors, all disks were reported to be in good health.
Next, I rebooted to non-network safe mode. Following this, I closed all remaining unnecessary processes. then, I attempted to create a backup boot disk from the latest saved .tib file. This operation now completed . Of course it took a while.
Next, I replaced the current boot disk with the newly created (from the .tib file) boot disk. It worked flawlessly.
Next, I rebooted to full windows and created a bootable Rescue Media (CD) from Acronis.
Next, I rebooted to the Rescue Media and attempted to create a new boot disk from the same .tib file. This process also completed flawlessly and, as before, when I replaced the current boot disk with the newly created (from the .tib file) boot disk, it worked flawlessly.
Since then, as I have used the system and the boot disk morphs continuously with use, new .tib files are created weekly (always validating) and the Rescue Media approach continues to produce flawless boot disks.
My conclusion is that there is something about Acronis which is very sensitive to other running processes, since Acronis seems to work ok in a very curtailed Safe mode (and of course from DOS/Rescue Media). In normal Windows mode, the restore function seems quite flaky and random (at least on my system, which is generally stable otherwise).
Thanks for your help and advice!
- Se connecter pour poster des commentaires