On VMware, I've also seen the version of VMware cause an issue (so-called 
"black screen" on boot, system does not even appear to POST). The target 
VMware host should be at the same or higher level of VMware than that of 
the source VMware host.

Best regards,

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager

"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 2011-06-16 
14:17:44:

> From: "Huebner,Andy,FORT WORTH,IT" <Andy.Huebner AT ALCONLABS DOT COM>
> To: ADSM-L AT vm.marist DOT edu
> Date: 2011-06-16 14:19
> Subject: Re: Restore trouble on Virtuel W2K3 server.
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
> 
> Without any detail it is hard to say why it did not work.
> 
> We have restored many W2k3 servers by dropping an OS down and 
> restoring the old OS on top. We have done it with real and imagined 
servers.
> There are some fatal traps...
> 1. The target of the restore needs to be similar hardware, real or 
imagined.
> 2. The target needs to be the same SP and close to the original in 
> patches.  There are a few patches that can be fatal if not applied 
first.
> 3. We find it best if the target has the same name.  Does not need 
> to be in the domain.
> 4. This one may be just us, but the Windows directory needs to be the 
same.
> 
> There are work arounds to most, if not all, of the above; but for 
> simplicity those rules work.
> We have a batch job that does the TSM part, it is only 2 or 3 commands.
> 
> 
> Andy Huebner
> 
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On 
> Behalf Of Grigori Solonovitch
> Sent: Thursday, June 16, 2011 7:06 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Restore trouble on Virtuel W2K3 server.
> 
> I do not think it is possible to do restore like this - you need to 
> use some Bare Machine Recovery software like TBMR (Bare Machine 
> Recovery for TSM).
> 
> In addition, you can just clone VM instead of using TSM, if source 
> and target servers are VMs.
> 
> Grigori G. Solonovitch
> 
> 
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On 
> Behalf Of Bo Carsten Krogholm Nielsen
> Sent: Thursday, June 16, 2011 2:52 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] Restore trouble on Virtuel W2K3 server.
> 
> Hi all,
> 
> I have restored a W2K3 server in a VM environment, but now it will 
> not back up.
> It is a new server, where I restored the backup from another server.
> 1. Restored C-drive
> 2. SystemState restored.
> 
> Then boot the server, which then stops during boot.
> What went wrong?
> 
> 
> Have fun
> 
> Bo Nielsen
> Senior Technology Consultant
> 
> DONG Energy A/S
> Klædemålet 9
> 2100 København Ø
> Denmark
> 
> Tlf.:      +45 9955 1111
> Mobile +45 9955 5434
> 
> bokni AT dongenergy DOT dk<mailto:bokni AT dongenergy DOT dk>
> www.dongenergy.dk
> 
> 
> Please consider the environment before printing this Email.
> 
> CONFIDENTIALITY AND WAIVER: The information contained in this 
> electronic mail message and any attachments hereto may be legally 
> privileged and confidential. The information is intended only for 
> the recipient(s) named in this message. If you are not the intended 
> recipient you are notified that any use, disclosure, copying or 
> distribution is prohibited. If you have received this in error 
> please contact the sender and delete this message and any 
> attachments from your computer system. We do not guarantee that this
> message or any attachment to it is secure or free from errors, 
> computer viruses or other conditions that may damage or interfere 
> with data, hardware or software.
> 
> This e-mail (including any attachments) is confidential and may be 
> legally privileged. If you are not an intended recipient or an 
> authorized representative of an intended recipient, you are 
> prohibited from using, copying or distributing the information in 
> this e-mail or its attachments. If you have received this e-mail in 
> error, please notify the sender immediately by return e-mail and 
> delete all copies of this message and any attachments.
> 
> Thank you.