The Back Up n00b
I have traditionally been really bad about backing anything up except just making copies of media or documents to an external location. I have owned TI9 for ever and only really half-assed the whole back up process.
I have spent much time here at the forums on and off over the past month reading up in an effort to gain a better understanding of not only making backups but actually recovering from one.
I am about to make a TI rescue CD since I already have backups on an external drive. That just seems like the most straightforward method for a n00b like me out of all the solutions I have read here. Its a good thing I came here because I would have tried to load up TI9 from the factory CD not knowing that I need to make one for the version I am running.
After reading all the different types of backups and tools here I found myself with more questions than answers:
1. Will the rescue CD I create on one XP machine also work on another XP machine running the same version of TI9?
Would it work with a machine running Vista if it had been made from and XP machine or do I need to make a separate rescue CD for Vista?
2.What is the purpose of WinPE, BartPE, and the MustangPEBuilder? I understand that WinPE is for booting into Vista but would it work for XP also? And BartPE is only for booting into XP right? I had a hard time understanding what this has to do with True Image or what its usefulness is. Could someone please explain it in a manner that an idiot would understand?
I am looking for the best solution to be able to manually (for now) back up multiple computers running XP and Vista and also to easily recover from a back up when needed. These back ups are all made to a 1TB external drive. What I have read about being able to boot and recover from a singel device such as an external drive is very appealing to me but the task of setting this up seems daunting. It is not something I have the time to really dive into right now. I am more worried about being able to recover from a back up right now before I move on to one of the “advanced” methods that I read of here.
The TI time bars are notoriously wrong so they can't really be relied on. I use a WinPE disk that has Windows drivers not the Linux ones which are on the recovery CD. Windows ones are faster
Do your first restore and see how long it takes
The verification is very important though as TI clears the destination drive before it starts restoring. If it finds an error in the archive part way it stops so you end up with a cleared destination drive and a backup you can't restore.
I always verify as part of my backup but not as part of my restore (and I do not copy the archive file aware nor defragment the drive it is on so i am comfortable with only validating after backup
As no one has answered you earlier questions I will have a go
1 The recovery CD can be used on any machine as the CD boots into a Linux environment but you should make sure that the version of the CD you made was made from the version of TI that you made the archive with. Acronis states that the archives (tib files) are only one past generation compatible with TI versions. If you upgrade your TI keep your Recovery CD current
2 Using PE is another method of having a recovery disk. Microsoft have very cutdown version of Windows (XP,Vista, Windows7 that can be installed on a CD or USB drive. Acronis provide a "plug in" version of True Image that can be integrated with that PE so when you boot off the CD you get True Image. You download the relevant Windows file from Microsoft. It is called a WAIK
BartPE was a programme that provided an easy way to make a PE CD and integrate a plugins (You can also integrate other programmes.)
MustangsPE Builder does the same function but much better. I use it to build the PE environment I use. Mustang also wrote a plugin for True Image so you can do more things with TI running in the PE environment such as mounting.
The advantage of the PE enviroment is speed and better compatibility with computer hardware especially newer hardware
In my view having a WinPE Cd or booting USB is the easiest way to do recoveries and Mustangs is the easiest way to build it
Thanks for the prompt response. This may seem redundant but for clarities sake I am going to reiterate a few of your comments to help me and anyone else understand it all better.
-A WinPE disk for the rescue CD is faster because it is windows drivers not linux.
-No need to verify on restore if it has already been done with the initial back up. This decreases the back up time.
-PE is just another method of having a rescue disk. It’s faster and more compatible.
-BartPE and MustangPE are used to make a PE disk. The difference is that you have to pay for MustangPE and it offers a plug in for TI that allows more functionality.
BTW at the time of this posting TI shows the verification of the restoration only half complete. Its been an hour and a half so far.
I would second the comments by TATOU.
The time it takes to perform a restore is about the same time it takes to perform a backup when booted from the Rescue CD.
An additional recovery method (which is easy to create) is to create a Grub4dos flash drive (or USB drive or another internal drive. This is bootable method of performing backups or restores using the Acronis Restore disk programs. Check inside my signature index for references to MudCrab's Grub4Dos tutorial. Using this method, you can have Acronis Boot images on the flash drive(s) and choose from a menu of user created boot options such as between PE or Mustang's or standard Acronis CD and the program boots into a startup image of either of these choices.
In reference to [[http://www.wilderssecurity.com/showthread.php?t=185731|this thread called "Fix Vista so a Repair is not needed after restore or clone"]]
From what I understand I do not need a BartPE CD or a Vista DVD to do this correct?
I just need to follow the instructions below this line copied from the above link...right?
If the Command Prompt directory is not the \windows\system32 directory then type the following commands (<ENTER> means to press the ENTER key):
c: <ENTER> cd \windows\system32 <ENTER>
If your Vista partition is a drive letter other than C: then use that drive letter.
Once you're in the \windows\system32 directory, type the commands below:
bcdedit /set {default} device boot <ENTER> bcdedit /set {default} osdevice boot <ENTER> bcdedit /set {bootmgr} device boot <ENTER> bcdedit /set {memdiag} device boot <ENTER>
This assumes that the "default" booting entry in the BCD file is Vista.
After these changes, your bcdedit output will resemble this:
Windows Boot Manager -------------------- identifier {bootmgr} device boot description Windows Boot Manager locale en-US inherit {globalsettings} default {default} displayorder {default} toolsdisplayorder {memdiag} timeout 30 Windows Boot Loader ------------------- identifier {default} device boot path \Windows\system32\winload.exe description Microsoft Windows Vista locale en-US inherit {bootloadersettings} osdevice boot systemroot \Windows resumeobject {d5f6f061-52c6-11dc-8f68-ff6d008c462c} nx OptIn
instead of referencing a partition directly as in the example below:
Windows Boot Manager -------------------- identifier {bootmgr} device partition=C: description Windows Boot Manager locale en-US inherit {globalsettings} default {default} displayorder {default} toolsdisplayorder {memdiag} timeout 30 Windows Boot Loader ------------------- identifier {default} device partition=C: path \Windows\system32\winload.exe description Microsoft Windows Vista locale en-US inherit {bootloadersettings} osdevice partition=C: systemroot \Windows resumeobject {d5f6f061-52c6-11dc-8f68-ff6d008c462c} nx OptIn
Now, if you clone the Vista partition or image it and restore it, you should not have to run a repair. It should boot up properly.
Jason:
You will not need to do the above steps for TI version 11, 2009, or 2010. The advice in the post you have quoted applies to earlier versions of TI.
Yeah it is TI9 (what ever the latest build is) that is running on that particular Vista computer. I just want to make sure it is as simple and straight forward as the post indicates. Looks like it only takes a few minutes.
As long as Vista is installed to the active partition on the disk then yes, the advice will do the trick. If you have a dual-boot or multiboot installation on your PC then don't do it as shown. Describe your installation and we can give specific advice.
It is on an HP with a recovery partition designated as the D drive. What steps would I have to take to make the back up of the recovery partition usable and working if/when I need to use it?
Oh, I also typed in the code as instructed. How do I see the Windows Boot Manager and the Windows Boot Loader out put liek it is in the instructions. I do not know the command to bring it up or where to look for it.
Jason:
To see the BCD open an elevated command prompt and type bcdedit
I don't know how the HP recovery partition works so I probably can't help you there. Perhaps if you post the full BCD it may give clues about how the HP recovery partition works. Open an elevated command prompt and navigate to the desktop. Type bcdedit /enum all > bcd.txt
Open the file bcd.txt on your desktop and copy/paste the output here.
I ran it from sys32 where I was instead of the desktop as instructed. Hope it doesn't make a difference. Sorry it came out sloppy when I pasted it.
Windows Boot Manager
--------------------
identifier {bootmgr}
device boot
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {8c384824-6ff0-11db-8455-0016d303c84f}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
resume No
Windows Boot Loader
-------------------
identifier {572bcd55-ffa7-11d9-aae2-0007e994107d}
device ramdisk=[D:]\sources\boot.wim,{ramdiskoptions}
path \windows\system32\boot\winload.exe
description HP Recovery Manager
osdevice ramdisk=[D:]\sources\boot.wim,{ramdiskoptions}
systemroot \windows
nx OptIn
detecthal Yes
winpe Yes
Windows Boot Loader
-------------------
identifier {current}
device boot
path \Windows\system32\winload.exe
description Microsoft Windows Vista
locale en-US
inherit {bootloadersettings}
recoverysequence {572bcd55-ffa7-11d9-aae2-0007e994107d}
recoveryenabled Yes
osdevice boot
systemroot \Windows
resumeobject {8c384824-6ff0-11db-8455-0016d303c84f}
nx OptIn
Resume from Hibernate
---------------------
identifier {8c384824-6ff0-11db-8455-0016d303c84f}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
pae Yes
debugoptionenabled No
Windows Memory Tester
---------------------
identifier {memdiag}
device boot
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes
EMS Settings
------------
identifier {emssettings}
bootems Yes
Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200
RAM Defects
-----------
identifier {badmemory}
Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}
Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}
Device options
--------------
identifier {ad6c7bc8-fa0f-11da-8ddf-0013200354d8}
description Ramdisk Device Options
ramdisksdidevice partition=D:
ramdisksdipath \boot\boot.sdi
Setup Ramdisk Options
---------------------
identifier {ramdiskoptions}
description Ramdisk Options
ramdisksdidevice partition=D:
ramdisksdipath \boot\boot.sdi
Jason:
That looks good. Your changes are reflected in the BCD output, so you're ready to image/restore your disk with TI9. The restored image should boot into Vista correctly.
However, hibernation and the HP recovery manager won't work because their BCD entries will be "unknown" after imaging. First, the hibernation file (the BCD entry group "Resume from Hibernation") specifically references the C: partition, so after imaging you may find that hibernation doesn't work. But it's easy to fix by turning off hibernation and then turning it back on. Doing this will re-create the correct BCD reference.
It looks like HP did their recovery partition the right way, linking it to the BCD and putting the recovery files on the D: partition. The BCD references D: explicitly, so after you do the restore the HP recovery entries will be listed as Partition=unknown. These can be fixed with the following BCD commands (you might want to copy/paste these):
bcdedit /set {572bcd55-ffa7-11d9-aae2-0007e994107d} device ramdisk=[D:]\sources\boot.wim,{ramdiskoptions}
bcdedit /set {572bcd55-ffa7-11d9-aae2-0007e994107d} osdevice ramdisk=[D:]\sources\boot.wim,{ramdiskoptions}
bcdedit /set {ad6c7bc8-fa0f-11da-8ddf-0013200354d8} ramdisksdidevice partition=D:
bcdedit /set {ramdiskoptions} ramdisksdidevice partition=D:
In other words, they should end up looking exactly like they do in your current BCD.
Let me know if you have any problems. Do you have a Vista DVD for repairs if needed? If not, go here and download the Vista recovery environment and burn it to a CD. Hopefully you won't need it but it helps to be prepared.
Cool, thanks so much for all the great info. I do not plan on using the recovery partiton and its taking up valuable space on the small HD of this 2005 HP laptop. With this I can remove and put it back safely if the computer ever goes to some one else.
Is there a way to paste into cmd prompt?
And I do not have a Vista DVD. I did make the acronis recovery disk and each HP computer allows you to make one set of recovery disks that does contain the information needed to recover.
What is the best way for me to test this Vista backup if I only have one laptop HD at the moment. I have a ton of 3.5" SATA HD's around for desktops.
Jason:
Yes, you can paste into command prompt. Use the Edit menu in the upper-left corner of the window:
The only way to test your backup is to restore it. The best way to do this is to restore to a spare hard disk.
Greetings all.
Had a graphics card installation go bad. When I went to restore using my Acronis boot disk it didn't recognize its own .tib files on my external HD. I have the backups in their own directory on the external HD and within that directory there are three more directories representing one of three computers. The boot disk and backups are all made with the same version. What could have caused this to happen?
As usual, any help is appreciated.
Jason:
Have you ever tested the boot disk with this particular computer to make sure that it saw all connected disk drives, including your external USB disk? If it's a newer PC then TI9, which is an old version, may not have driver support for the newer hardware.
If you have a second internal hard disk or more than one partition on your single internal disk that has enough free space to accommodate your image file then you could copy the image file to the internal disk. Then boot from the TI9 CD and restore the Windows partition from the internal disk.
Yes this back up from its location on this particular external drive has been tested before on this computer. It sees the drive just fine. It even sees the .tib files of the backup tree on the external drive. But when I select the bu I want it says it does not recognize the file. The only thing that I have changed is this computer was a running RAID 5 and now its running RAID 0 but still on the same RAID controller. I don't think that would make a difference though.