Trouble Restoring System State Windows Server 2008

mjames1337
mjames1337 used Ask the Experts™
on
Someone has broken Exchange badly by installing a new application on the server.  I have plenty of full backups to external hard drives and all I need to do is restore the system state.  I have tried the command line string that Microsoft walks you through and every combination I can think of.  The trouble is that the examples all use network shares for the backup source whereas my backups are going to the strangely create volume label that Microsot autocreates in the backup wizard.  The label is this exactly pasted straight from disk management:
clbmail 2009_12_04 11:03 DISK_02

My successful backups have all run at 9:00PM every night and I'm trying to get 6-29-10.  My server name is clbadmin.  Has anyone ever gotten this to work using external hard drives?

I have tried these commands to restore system state:

wbadmin start systemstaterecovery -backupTarget:clbmail 2009_12_04 11:03 DISK_02
ERROR - Command syntax incorrect. Error: 2009_12_04. See usage below.

wbadmin start systemstaterecovery -version:06/29/2010-21:00 backupTarget:clbmail 2009_12_04 11:03 DISK_02

Any help would be greatly appreciated.  If someone can tell me the exact command that they have gotten to work before on a system state restore, I would be very grateful.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
I have you try to share the disk that hosts the backup files. The change the disk_02 to the share name. Are these file on a san directly connected what is the external disk type and connection type?

Author

Commented:
I have not tried that because I'm new to the 2008 server backup system and afraid to do anything with the drive.  It's just  your typical external usb hard drive.  The backup system  actually mounts the drive and not the OS.  The backup system when you check status can only locate the media with the screwy volume label that it randomly creates.  I don't want to corrupt the data.  
Opps a long day and the baby was and still is crying. I meant to say share the disk that hosts the backup file and try the restore command from that new share. Making sure the logon account has full access.
Starting with Angular 5

Learn the essential features and functions of the popular JavaScript framework for building mobile, desktop and web applications.

Ahh why not copy the back up file to an internal drive with a share and run the command. I think may be the is the fact that you are using a usb drive and not a share for the backup location.
Sorry just to highlight, you should copy the backup file and not move this will for sure not affect your current backup file... Not that they seem to work any way but better safe then sorry.

Author

Commented:
It looks like I will have to try sharing it somehow when I get back there in the morning since that's all the solutions I see on the web as well as here.  I tried to open the drive from Disk management but there was not a drive letter associated with it so I could not view what was there even though the backup system sees the data as a successful backup.  I may just take the drive out of the enclosure and clone it to be safe.    Thank you for your comments.  I will post the result tomorrow.
Good luck and please update this as Im curious now

Author

Commented:
Yes, me too.  For years I have been used to just running the ntbackup and restoring system state in a 15 minute deal for 2003 and 2000 servers when someone screwed something up on the configuration side.  They gotta make it difficult now.

Commented:
If you can not see your backup hard drive froma windows PC try a live CD of linux to copy the files from the hard drive to a PC. Once on a PC you can put on a server or where you want.
Listen to me guys.  Again, the system state restore has saved my behind for 10 years when a customer has installed something and F'ed up the install.  I 'm sure that I have saved more time in troubleshooting (usually at least 4 hours on average) and gotten the problem solved in 15 minutes when some employee took it upon themselves to install an accounting application and not pay attention to the wizard questions like "Do you run SMTP on this server?" and "Ok, Would you like to install our SMTP components" then completely overwrite all of your own transport rules bidirectionaly.  I have to be honest but I'm going to stay on SBS 2003 for a while for this reason from a support standpoint.   I had multiple employees working this ticket and combined they had 6 Microsoft employees avoid the thought and conversation regarding a system state restore.  Total avoidance!!!! What the heck?  Why even bother writing the code for this so-called Dos command solution that noone wants to support?  My theory is based on the voice I'm hearin inside of my head again saying, "Man, it's another group of 20 somethings who don't know how to work themselves through DOS based command line scripting or Batching so to speak so they all completely 100% avoided supporting that "so-called" restore solution.

Author

Commented:
Microsoft had no solution to system state restore

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial