That's exactly what we ran into. We tried NODENAME in addition to
VIRTUALNODENAME and neither worked. It appears the machine name must be
the original server name and if you already have a server with that name on
your network you can start another with the same name just to perform the
restore.
Jeff Connor
Niagara Mohawk Power Corp
"Prather, Wanda" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 05/16/2001
10:26:05 AM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: Windows 2000 Bare Metal Recovery and System Object restore pr
oblem
I haven't tried it myself, but I don't think so. Tivoli states that the
Windows MACHINE ID must be the same when restoring "system objects", not
just the TSM nodename.
.
-----Original Message-----
From: Hrouda Tomáš [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 16, 2001 2:15 AM
To: [EMAIL PROTECTED]
Subject: Re: Windows 2000 Bare Metal Recovery and System Object restore pr
oblem
Wouldn't help you to use the same TSM client nodename as original server
(otherwise to use virtualnodename) only for a moment of restore system
objects and after restore change client nodename back?
Tom
> -----Původní zpráva-----
> Od: Jeff Connor [SMTP:[EMAIL PROTECTED]]
> Odesláno: 15. května 2001 22:44
> Komu: [EMAIL PROTECTED]
> Předmět: Windows 2000 Bare Metal Recovery and System Object restore
> problem
>
> Our NT admins requested that we build one server(HCB1) from another
> servers
> backups(SYR1). The servers are Windows 2000 Advanced Server running
> service pack one with identical hardware. Our TSM server is V4.1.2 on
> AIX
> 4.3 and the Windows Client is 4.1.2.14. We used the TSM B/A CLI with
the
> virtualnodename option to succesfully restore the SYR1 servers C: drive
to
> the HCB1 server. We then attempted to restore the system objects but
> could
> not access them from the CLI or the GUI.
>
> We got into TSM GUI on the original server, SYR1, and where able to see
> the
> subfolders under system objects. Under HCB1 using virualnodename SYR1 we
> cannot see the system object subfolders. We checked the gray box and
> attempted the restore but received zero objects inspected or backed up.
>
>
> We contacted TSM support who informed me that Bare Metal Restore and
> associated Redbooks are not supported. However, after the level one
> person
> spoke to level two, they informed me that you could recover a Windows
2000
> server from the ground up if the target system for the restore is the
same
> local machine name as the original server. This is due to the fact that
> the Windows 2000 System Objects are stored using the local machine name
in
> TSM and can't be restored to a new location like a drive file space can.
>
> Has anyone else attempted what we tried or does anyone have any comments?
> We have been able to restore a server and it's registry to another server
> with a new name under Windows NT 4.0, using a temporary copy of NT
> installed to a folder called Wintemp, then coming up under the original
> name after restore/re-boot using the normal WINNT folder. It looks like
> this is not possible with Windows 2000 and TSM due to the way TSM stores
> the system object backups.
>
> Comments?
>
> Jeff Connor
> Niagara Mohawk Power Corp.
> ---
> Příchozí zpráva neobsahuje viry.
> Zkontrolováno antivirovým systémem AVG (http://www.grisoft.cz).
> Verze: 6.0.225 / Virová báze: 107 - datum vydání: 22.12.2000
>
---
Odchozí zpráva neobsahuje viry.
Zkontrolováno antivirovým systémem AVG (http://www.grisoft.cz).
Verze: 6.0.225 / Virová báze: 107 - datum vydání: 22.12.2000
