Be carefull with that Desaster Recovery Guide, sometimes you won't be able
to
recover your system-disk.
Legato confirmed that there is a bug in 5.5 and below.
The reason is, that NT4 in some cases can't recover some open files (like
ntdll.dll, smss.exe), it will restore them as .Axxx-files and NetWorker does
use the MOVEFILE_DELAY_UNTIL_REBOOT flag with MoveFileEx()and the
PendingFileRenameOperation key in registry. After that, registry will be
restored and, of course, the above key/flag in registry are "blow'n in the
wind"
Read the folllowing procedure, we got in that pitfal several times, two
years ago.
Recovery of a Windows NT4 systen partition with Legato Networker < 5.7
Because of bugs in the Legato Networker version 5.x a Windows NT system
partition cannot be recovered directly. An additional Windows NT
installation is
required to correct the filesystem after the recovery before the final
reboot can take place.
The machine to be recovered has to be prepared before the recovery can take
place:
The hardware configuration has to be very identical to the configuration
during backup:
- SCSI controller must be of same type and installed in the same slot
- Network controller must be of the same type and installed in the same slot
- The hard disk configuration must be similar in size and type.
- The filesystem must be the same type (FAT or NTFS) as during backup.
- The software configuration has to be nearly identical to the configuration
during backup:
- The operating system version must be the identical and installed in the
same location
- The service pack level must be identical
- The networker software must be the identical and installed in the same
location
The system configuration has to very similar to the configuration during
backup
The first action is to install a temporary Windows NT system on the machine
which is
needed to do a correction after the recovery is completed.
- Install Windows NT using the same version as the original installation
- Install the operating system in the directory "C:\CRASHNT".
- Do not install any optional items
- Do not install networking
- Do not specify a password
- Install the same service pack on the temporary system as used on the
original
installation
- Boot the temporary system and rename the file "BOOT.INI" to
"CRASHBOOT.INI"
The next action is to install another Windows NT installation in the
original location to be
used to recover the system from the networker server.
- Install Windows NT using the same version as original
- Use the same location for the operating system as original
- Use the same network drivers as original
- Use the host name and IP-address as original
- Install as a member server in a workgroup
- Do not enter an Administrator password
- Install the service pack and hotfixes (hotfixes only if NTFS related)
- Install the Networker client software in the same location as original
Recover -s <networker server> -iY -a REGISTRY: C:\ -s <networker server>
Explanation:
-s name of Networker server holding the index files
-iY = -f Force overwrite -a REGISTRY: C:\ Path of partition to be recovered
The recovery of a system partition must include the registry and the system
data.
A log file of the recovery is created in the root directory
of the system drive named "networkr.log".
Do not reboot the system immediately after the recovery has been completed.
Before rebooting the system rename the file "C:\BOOT.INI" to
"C:\NEWBOOT.INI", then
rename the file "C:\CRASHBOOT.INI" to "C:\BOOT.INI".
Reboot the system. After reboot the temporary system wil be loaded which is
necessary to
make corrections before the recovered system can be booted succesfully.
1) Find the file "NTDLL.DLL" in the SYSTEM32 directory of the recovered
system. If
another file exists with a name like "NTDLL.DLL.A*" then delete the file
"NTDLL.DLL" and rename "NTDLL.DLL.A*" to "NTDLL.DLL".
2) Find the file "SMSS.EXE" in the SYSTEM32 directory of the recovered
system. If
another file exists with a name like "SMSSS.EXE.A*" then delete the file
"SMSS.EXE" and rename "SMSS.EXE.A*" to "SMSS.EXE".
3) Start the registry editor (REGEDT32.EXE)
- Select the key "HKEY_LOCAL_MACHINE"
- Use the the menu item "REGISTRY / Load Hive ....", select the file
"C:\NETWORKR\system" and give it the name "READ".
- Use the the menu item "REGISTRY / Load Hive ....", select the file
"..system32\config\system" in the recovered Windows NT directory and give it
the name "WRITE"
- Open the key "HKEY_LOCAL_MACHINE\READ\Select" and note the value of
"Current"
- Open the key
"HKEY_LOCAL_MACHINE\READ\ControlSet00{x}\Control\SessionManager
whereby {x} is the value in previous "Current"
- Select the value "PendingFileRenameOperations",open the value for edit,
use Ctrl-C to copy the contents.
- Open the key "HKEY_LOCAL_MACHINE\WRITE\Select" and note the value of
"Current".
- Open the key
"HKEY_LOCAL_MACHINE\WRITE\ControlSet00{x}\Control\SessionManager
whereby {x} is the value in previous "Current"
- Create a value "PendingFileRenameOperations" with the type
REG_MULTI_SZ,open
the value for edit, use Ctrl-V to insert the contents from clipboard.
Rename the file "C:\BOOT.INI" to "C:\CRASHBOOT.INI", rename the file
"C:\NEWBOOT.INI" to "C:\BOOT.INI".
Reboot the machine to startup the recovered system. After startup the
following cleanup
operations should be done:
- Delete the directory "C:\NETWORKR"
- Delete the directory "C:\CRASHNT"
- Delete the file "C:\CRASHBOOT.INI"
- Check the virtual memory settings
- If a domain controller then synchronize with the domain.
regards
Klaus Grohal
-----Ursprüngliche Nachricht-----
Von: SUBSCRIBE NETWORKER Anonymous [mailto:devnull AT adc.idt DOT com]
Gesendet am: Mittwoch, 21. August 2002 23:00
An: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Betreff: [Networker] Restore from Scratch
Hello All,
I searched the archives and google. Couldnt find suitable docs.
Was wondering if you guys could help me with the same.
I have Legato 5.5.1(need to upgrade) running on Solaris 8(clients and
server), and i am on the lookout to for some documentation/procedure to
restore my root disk from scratch in the event that it crashes.
I am considering the event where i need to pull out the disk that just
died, put in a new disk, boot from network, make the partitions as before
on the new disk and then restore the whole filesystem using legato.
Does anyone have experience doing this ?
Your input will be much appreciated.
Best Regards,
/dev/null
devnull AT adc.idt DOT com
--
Note: To sign off this list, send a "signoff" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
