Dear all,
After a sudden death of the drive in my PC due to the (then) famous hard drive firmware bug I started to getting very worried on running backup regularly. I did have regular backup to the most important files from one partition to another partition, but that was all gone because all of them resided in the failed disk.
After a month of chaos, I finally realized that was a bug in the firmware and sent it to the vendor for the drive recovery. Now I got it back and bought another drive for backup purpose, the next best thing to do is the all-time important: the backup.
Knowing that the only way to create a VSS backup for all the volumes in disk 0 to disk 1 is wbadmin, so I have:
wbadmin start backup -backuptarget:e: -include:c:,d: -vssFull -quiet
When doing the end-to-end testing for the restore, the only way I could (instead of GUI):
wbadmin start recovery -version:08/31/2010-20:58 -items:d: -itemtype:Volume -backupTarget:e: -recoveryTarget:d: -quiet
C:\>wbadmin start recovery -version:08/31/2010-20:58 -items:d: -itemtype:Volume -backupTarget:e: -recoveryTarget:d: -quiet
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.
Warning: The START RECOVERY command is not supported in this version of Windows.
The operation ended before completion.
C:\>
Can anyone point out that this is the best approach in terms of backup/restore in Windows 7 (x64 Ultimate) using Microsoft's VSS implementation? The start recovery command seems not supported, what gives? Or I overlooked something in the Windows backup/restore GUI tools? Thanks in advance :)