Image based backup is a pain

Some of them. This one has the boot info in the Windows partition (Windows 7 Premium x64). But to put the boot info in the recovery partition seems inconvenient indeed.

About the SRP: I do not see what the problem is. Just backup it also. To restore to a new disc, first replicate in it the old partition structure, then restore each partition to the corresponding empty partition.

About imaging being difficult: it is. The prerequisite is to understand the basic operation of discs and partitions. To avoid problems, I try to keep all things as simple as possible.

(I am using imaging since the days of Drive Image 2002, I have had very few problems. I learned many basic things reading the excellent old Acronis forum. Now I see much confusing information.)

 

My guess is Dell don't want to use up all 4 partition slots. If you bought the computer with the following...

SRP
Dell Utility Partition
Dell Recovery Partition
Win7 Partition

...then you wouldn't be able to create another primary partition. But it means you have to image the 10 GB Dell Recovery Partition just to have a backup of a few MB of booting files.

Since BitLocker (the main reason for the SRP) is only available with Win7 Enterprise and Ultimate, having booting files outside of the Win7 partition is just making life a little more difficult for no gain.

 

Could they use GPT disks on 64-bit systems? This would remove the 4-partition limit, and I understand that Windows 7 can boot from GPT on 64-bit.

 

Sounds reasonable. But we'll have to get away from the PC/BIOS.

At present I'm only using GPT on data HDs.

http://en.wikipedia.org/wiki/GUID_Partition_Table

 

I'm trying to make a unattended Windows 7 without a SRP. i found a hack that modifys winsetup.dll inside a wim file, that stops the SRP being created on install but doesnt work for unattended though. If anyone interested i post info.

There is a program to mount wim files.

I have now got a unattended setup file that installs Program Data and Profile directory onto D drive.

 

Dear Mark,

Can you please posts these two hacks, attended and unattended?

Best regards,

KOR!

 

I have been following this thread and as a non-technical individual I can say that the solutions most if not all of you are offering do not make things any simpler for me, quite the opposite but thats OK I think, I am comfortable with the process and protective measures I have in place.

One thing I have been thinking about is the roll that virtualization can play in this area. If you have for example VMware you could quickly and easily create virtual machines of you PC and put them on an external device, then if there is an issue with the PC it would be easy to gain access to the VM on another PC and use it as a base going forward. No downtime at all other than the time nec to get access to a working PC with the required VM loader.

Now I could be very wrong about the effectiveness of this, it is also possible that my understanding of virtualization is incorrect. I have read a bit about virtual machines (on these forums) and in my limited understanding this seems like a reasonable approach. I do understand that this does not do anything for the messed up PC but a full format and installation of Windows and then the installation of VMware would bring this PC back to life quickly enough. No?

Am I out to lunch on this.

PS: one day when time permits or necessity demands I will get into virtual machines, for now its just something I am casually interested in.

Sorry if this is off topic.

 

bgoodman4,

Which OS do you have and are you using an imaging app?

 

I have XP and will have to go to virtual machine eventually as I use Lotus 123 for a rather complicated spread sheet I use for business.

On my desktop I use ShadowProtect and on my Laptop I use RollBack Rx and had been using DriveCloner Rx weekly to image my drive with Rx installed. Once a month I uninstall Rx and image with Paragon and then reinstall Rx. Daily I upload my critical data to iDrive (on-line storage).

I guess from the limited replies virtualization is not considered as a workable (albeit not less complicated) solution here.

 

@KOR read last post
www.msfn.org/board/topic/137245-never-create-system-reserved-partition/
a wim file can be mounted using dism and imagex if you have automated deployment kit installed.

if not familar you can download Winmount.

 

Hello, I'm extremely new to the system image, I have some doubts:

I am seriously thinking about using Paragon Backup & Recovery 2011 (Advanced) Free (http://www.paragon-software.com/home/db-express/)

1. Has anyone used this program?
2. What was your experience?
3. Could someone pass instructions to backup and restore (using the Paragon)?
4. If I select Backup C: /, and give my HD problem, if I buy another I can restore the system image perfectly (including boot)?
5. You find it best to keep the image of the system included in Windows 7?
6. Could anyone give me some better free option?

Thanks in advance, I'm completely noob on the subject.

 

The unallocated can be moved to the end. If c reclaim that space, means all of c data has to be moved which takes times and added risk moving it. Like you say best leave it where it is.

 

Brian, all of that can be done with one line from ms. laughs.

bcdboot c:\windows /s c:

It recreates the boot folder and creates a new bcd store on the drive you specify.

http://technet.microsoft.com/en-us/library/dd744347(WS.10).aspx

To stop install creating SRP. Create full partition just before using Diskpart. Diskpart can be ran automated in a script file using the /s command. Make script ask what size you want partition or just make system partition big enough preconfigured. Copy the script to your install DVD iso, so you can run it each time.
https://www.wilderssecurity.com/showpost.php?p=1820289&postcount=51

Note: the repair option of Windows 7 will be unavailable from the F8 boot menu if you delete the system reserved partition. You have to rely on the setup DVD for that.

 

Mark,

If you use the batch file method the Repair Option is still available from the F8 menu.

 

Dear Mark,

Thank you for the SRP thread. I have download the patched winsetup from the site.

I have messed up my desktop and need your, Panagiotis, Brian, Pete, Sadeghi85, Aaron .... expertise to help me in the following thread:

https://www.wilderssecurity.com/showthread.php?p=1832667#post1832667

Best regards,

KOR!

 

KOR, I wish I could be of help, but I'm still (very happily) using WinXP.

However, I'm sure the others can and will help...

Aaron

 

I assumed because of no SRP. If your batch has repair menu then bcdboot should too. OEM doesnt' have repair menu as repair not even on DVD. One time i didnt have repair menu.

Are you sure you have REPAIR with no SRP BY F8?

 

Yes, it is running now. I'm at the System Recovery Options window.

 

Brian, It is said the repair tools are also kept in SRP. If you delete SRP, the repair tools must also get destroyed. Repair is in \Recovery folder.

It probably this. If you initially create partition before with no SRP, it creates repair in c. Thats why you have it. If it creates SRP, it puts there, so if you delete SRP, no repair. So if that true better to create partition before, than getting rid of SRP after. or copy the \Recovery folder.

 

Mark,

I have a series of Win7 images so I can easily do tests.

The current test was with a SRP/Win7 system. I used the batch file (Terabyte method) to copy the SRP contents to the C: drive. I then deleted the SRP. Repair still works fine.

 

Mark, I had a look at this method and compared it to the Terabyte method. As you have indicated, when using the above command line you lose the Windows Recovery Environment. You also lose Ramdisk Options. I'm not sure what that does but it is present in BING BCD Edit.

 

Brian, did you do a test from scratch? creating a SRP default install?

I can see recovery option in bcd if i type bcdedit /enumall. It probably say unknown or identifier messed up if not there. It can be corrected with bcdedit. What is interesting it possible to move recovery to another drive such as d,changing the c:\recovery part in bcd. In fact having a recovery on c or boot makes no sense. If you delete SRP in true test then where is the recovery coming from? Must be c:\recovery but then it should be in SRP. It possible if used repair dvd after , the recovery files are added,fixed. incidentally i found a MS file with a unfriendly name called bsdhdcfg.exe that sets up recovery and bitlocker files on a drive.
It possible when you change the offset restoring, the identifier,guid are then pointing wrong so no boot but thats another matter.

 

I used a standard SRP/Win7 setup. Win7 had been installed to unallocated space so a 100 MB SRP had been created.

 

If windows create a 100mb SRP, will install the recovery winre.wim in the main OS partition.
If it creates a 200mb(or more) SRP, will install the winre.wim in the SRP.
Windows installer choice depends on the available free space used to install the OS.

Brian did not have to fix the bcd entries because it was already in the OS.

Panagiotis