Download
1 / 29
290 likes | 306 Vues
Bare Metal Restore 4.6. Dissimilar System Restore: An Introduction. Agenda. Dissimilar System Restore (DSR) Overview BMR 4.6 New Concepts DSR Notes and Caveats Screen Shot Recoveries. DSR Overview.
E N D
Bare Metal Restore 4.6 Dissimilar System Restore: An Introduction
Agenda • Dissimilar System Restore (DSR) Overview • BMR 4.6 New Concepts • DSR Notes and Caveats • Screen Shot Recoveries
DSR Overview • Dissimilar System Restore allows a BMR user to recover a Windows system to target hardware that is completely different from the source hardware. • Users require this capability when: • No identical replacement hardware components or systems are available. • The user desires to migrate or upgrade to different hardware. • DSR builds on BMR 4.5’s Dissimilar Disk Restore (DDR) feature. • DDR is still a BMR feature. • DDR can be used with DSR as needed.
DSR Overview • DSR gives BMR a unique differentiator: • Automated system recovery to completely different hardware is something no other product can do. • Competitive products will have issues when Windows objects such as the Registry, device drivers, OS kernel, or Hardware Abstraction Layer (HAL) are restored to dissimilar hardware that has different devices, bus architecture or chipsets. • DSR addresses many key issues such as: • New NIC and/or MSD drivers may be inserted. • Windows system files may be changed. • IP information may be changed. • Extensive registry changes are always required and are handled automatically by BMR. • Changes are persistent after the restore is complete.
DSR Overview • The source and target systems may differ in: • Manufacturer and model • Number and type of processors (32 bit only) and associated changes such as different Hardware Abstraction Layer (HAL) • Number and brand of video adapters • Number and brand of Network Interface Cards (NICs) • Number and type of Fibre Channel Host Bus Adapters (HBAs) • Number and type of Mass Storage Controllers (MSDs) • Number and size of disk drives (Dissimilar Disk Restore - DDR -rules apply) • IP and Network Configuration • Example: AMD CPU single processor IDE-based Gateway source system could be restored to an Intel CPU multi-processor RAID/SCSI-based Dell target system.
BMR 4.6 New Concepts • Client configurations • A client configuration is an extension of what was previously called the client “meta-data”. • A client configuration is an encapsulation of the data that describes a BMR client. • Each time the BMR Save Configuration Utility runs a “current” configuration is generated. • The BMR sever can maintain multiple different client configuration files for each BMR client. • User may copy, edit, and merge configurations. • Except for the “current” configuration (which is created by bmrsaveconfig), client configurations are created by BMR users.
BMR 4.6 New Concepts • Windows restore process changes: • All of the BMR client-related screens on the Administration GUI have been converted to allow manipulation of client configurations and some new screens have been created. • In order to restore a system, you first select the configuration you wish to restore with. • For “simple” (simple = non-DSR, non-DDR, no IP changes) restores, the user may select and use the “current” configuration. • For DSR restores, DDR restores, and restores requiring changes to the IP configuration, the user will copy the “current” configuration, edit the configuration as necessary for the dissimilar target hardware, then save the configuration with a new name for use in the restore. • Tabs are available to edit network configuration, MSD and NIC drivers, and to specify which Windows Service Pack to use during the restore.
BMR 4.6 New Concepts • Windows restore process changes (cont.): • As was true in BMR 4.5, DDR disk mapping is done on the BMR client during restoration with the DDR mapping utility. • In BMR 4.6 the mapping utility has been enhanced to support Windows 2000 Dynamic Disks, and also to simplify the mapping process by allowing drag and drop. • The mapping utility also allows the user to change the partition size and type (striped, mirrored, RAID 5, etc.).
BMR 4.6 New Concepts • Unix restore process changes • Although DSR is not yet supported on Unix platforms, some of the concepts developed for DSR on Windows apply. • In order to restore a system, you first select the configuration you wish to restore with. • For “simple” (simple = non-DDR, no IP changes) restores, the user may select and use the “current” configuration. • For DDR restores and restores requiring changes to the IP configuration, the user will copy the “current” configuration, edit the configuration as necessary for the dissimilar target hardware, then save the configuration with a new name for use in the restore. • As was true in BMR 4.5, Unix DDR restores utilize a discovery agent to identify disks available for restore. The DDR discovery agent is invoked from the client configuration screen any time prior to Prepare to Restore. • Tabs are available to edit network configuration and to allow selection of a “discovered” volume configuration to use in the Unix DDR mapping interface.
BMR 4.6 New Concepts • Unix restore process changes cont.) • The Unix restore process now has a DDR-related "Discover" function that captures target system disk configuration information into a special client configuration file that is used during Unix DDR.
DSR Notes and Caveats • When performing DSR, the Prepare-To-Restore function of the BMR Web Administration GUI is more complex. The following steps are required at Prepare to Restore time: • The user must edit a client configuration to specify driver and network changes. • The user must specify the MAC address of each NIC. • The Windows Service Pack level used during BMR restore must match the original system; the appropriate Windows Service Pack is specified by the user at Prepare to Restore time.
DSR Notes and Caveats • New MSD and NIC Drivers may need to be added ahead of time with the Create Package Wizard. • This occurs typically when the target hardware is different than the source hardware and the drivers are not available on the Windows installation media. • Driver addition is done easily via the “create package” wizard from any Windows BMR client. • A manual administrator login on the restored system is required to finish the restore.
DSR Notes and Caveats • DSR supports Windows NT and 2000 but not Windows Server 2003 or Unix (yet). • DSR does not support cross-OS restores; e.g.,an NT source system cannot restore as a Windows 2000 target system. • NICs and MSDs must be PCI-based. • NICs must be ethernet. • Dissimilar Disk Restore (DDR) supports Windows 2000 Dynamic Disks but not VERITAS Volume Manager (yet). • SAN?
Screen Shot Recoveries • Windows “simple” restore • Windows DSR/DDR restore
