Recover Your Data Quickly: Disaster Recovery Techniques with ARCserve  Disaster Recovery

Agenda  Goals of Disaster Recovery Software  Disaster Recovery with ARCserve  How DR Works in ARCserve  Creating Disaster Recovery Bootkits  Performing Your Disaster Recovery  Where to look for more information  Question & Answer  Goals of Disaster Recovery Software  Disaster Recovery with ARCserve  How DR Works in ARCserve  Creating Disaster Recovery Bootkits  Performing Your Disaster Recovery  Where to look for more information  Question & Answer

Goals of Disaster Recovery Software  Bring back the machine to its original state  Bring back the machine quickly  Bring back the machine easily  Automated partition recovery  Automated driver installation  Automated OS configuration  Bring back the machine to its original state  Bring back the machine quickly  Bring back the machine easily  Automated partition recovery  Automated driver installation  Automated OS configuration

ARCserve Disaster Recovery Provides...  Remote Disaster Recovery  Automated Partition Recovery  No Special Backups Needed  On Demand Creation of Boot Disks/Tapes  Supports backups made with:  MTF formatted tapes  ARCserve RAID sets  In SAN environments  Remote Disaster Recovery  Automated Partition Recovery  No Special Backups Needed  On Demand Creation of Boot Disks/Tapes  Supports backups made with:  MTF formatted tapes  ARCserve RAID sets  In SAN environments

Disaster Recovery with ARCserve  ARCserve Disaster Recovery is now available for:  Windows NT  Windows 2000  Novell NetWare 4.x  Novell NetWare 5.x  Linux  ARCserve Disaster Recovery is now available for:  Windows NT  Windows 2000  Novell NetWare 4.x  Novell NetWare 5.x  Linux

Disaster Recovery Do's & Don'ts  Do:  Update DR tapes/floppies whenever there are system changes  Test DR procedures  Make sure DR tapes/floppies are safely stored Store tapes and DR bootkits together Tapes and bootkits are properly labeled  Don't use DR software for:  Server Migration  As a chance to do a hardware upgrade  To clone servers  Do:  Update DR tapes/floppies whenever there are system changes  Test DR procedures  Make sure DR tapes/floppies are safely stored Store tapes and DR bootkits together Tapes and bootkits are properly labeled  Don't use DR software for:  Server Migration  As a chance to do a hardware upgrade  To clone servers

How Disaster Recovery Option Works on NT/2000  DR information collected during full backups only  Data stored in ARCserve$/DR/  DR recovery information can be created three ways:  Generic Bootdisks Windows NT only  Machine Specific Bootdisks Will auto-partition machine, restore settings  Bootable Tape OBDR support  CD Based DR Coming Soon!  DR information collected during full backups only  Data stored in ARCserve$/DR/  DR recovery information can be created three ways:  Generic Bootdisks Windows NT only  Machine Specific Bootdisks Will auto-partition machine, restore settings  Bootable Tape OBDR support  CD Based DR Coming Soon!

Disaster Recovery Option Limitations  DR on Windows 2000 does not currently support  Remote DR for 2000 machines (coming soon)  Tape based OBDR support (coming soon)  DR over SANs (coming soon)  Generic DR bootdisks System State makes machine specific bootkits a requirement  EISA Partitions  Must be restored before DR begins  RAID Arrays  Must be setup before DR begins  DR on Windows 2000 does not currently support  Remote DR for 2000 machines (coming soon)  Tape based OBDR support (coming soon)  DR over SANs (coming soon)  Generic DR bootdisks System State makes machine specific bootkits a requirement  EISA Partitions  Must be restored before DR begins  RAID Arrays  Must be setup before DR begins

Performing Your Backups  Must be full backups  Icon for the machine should be full green  Backups of remote machines MUST be made through the NT/2000 client agent  Check activity log for warnings/errors related to DR process  A few open files should not affect the DR process  Errors to look for are: Run Windisk to generate DR information Failed to create DR information errors  Must be full backups  Icon for the machine should be full green  Backups of remote machines MUST be made through the NT/2000 client agent  Check activity log for warnings/errors related to DR process  A few open files should not affect the DR process  Errors to look for are: Run Windisk to generate DR information Failed to create DR information errors

Creating Your Bootkit  Bootkit wizard  Wizard shows which bootkits are available (OS dependent)  Bootkit requirements  4 disks for Generic NT  5 disks for Specific NT/2000  1 tape for OBDR (NT only)  If using disks, Disaster Recovery uses:  Modified versions of Windows NT/2000 setup disks  ARCserve specific recovery disks  Bootkit wizard  Wizard shows which bootkits are available (OS dependent)  Bootkit requirements  4 disks for Generic NT  5 disks for Specific NT/2000  1 tape for OBDR (NT only)  If using disks, Disaster Recovery uses:  Modified versions of Windows NT/2000 setup disks  ARCserve specific recovery disks

Steps for Creating Your Bootkit 1.Select your Bootkit type 2.Select your ARCserve Server 3.If using floppies:  Select Generic or Machine Specific  For Specific disks, select the machine to create disks for 4.Start the Bootkit creation. 1.Select your Bootkit type 2.Select your ARCserve Server 3.If using floppies:  Select Generic or Machine Specific  For Specific disks, select the machine to create disks for 4.Start the Bootkit creation.

What’s on the Boot Disk?  First 3 are modified NT setup disks  4th disk contains the ARCserve recovery software  5th disk contains machine specific information  Network drivers  System and Security registry hives  Partition information (partinfo.ppp)  Found on the 3rd bootdisk  Should be removed when: Using RAID arrays Using EISA partitions Trying to disable the auto-partitioning  First 3 are modified NT setup disks  4th disk contains the ARCserve recovery software  5th disk contains machine specific information  Network drivers  System and Security registry hives  Partition information (partinfo.ppp)  Found on the 3rd bootdisk  Should be removed when: Using RAID arrays Using EISA partitions Trying to disable the auto-partitioning

Troubleshooting Bootkit Creation  If machines do not appear as available for DR in the Bootkit Wizard:  Check that full backup was performed  Check for errors in the activity log  If the Bootkit Wizard is unable to copy files to disk:  Make sure disks are formatted  Damaged disks may not have full capacity  Use chkdsk to check for disk capacity  If hardware is changed, or reconfigured  Run a new full backup  Update the bootkit!  If machines do not appear as available for DR in the Bootkit Wizard:  Check that full backup was performed  Check for errors in the activity log  If the Bootkit Wizard is unable to copy files to disk:  Make sure disks are formatted  Damaged disks may not have full capacity  Use chkdsk to check for disk capacity  If hardware is changed, or reconfigured  Run a new full backup  Update the bootkit!

Performing Disaster Recovery  What do you need to perform a DR?  Tape with full machine backup  ARCserve DR Bootdisks (if using disk based method)  Windows NT or 2000 CD  Hardware specific drivers (with NT 4.0)  For the most part, disk-based DR is following onscreen prompts 1.NT 4.0 – The first step. Do I choose custom or express setup?  Choose custom if Changing the hard drive Need to load hardware specific drivers  What do you need to perform a DR?  Tape with full machine backup  ARCserve DR Bootdisks (if using disk based method)  Windows NT or 2000 CD  Hardware specific drivers (with NT 4.0)  For the most part, disk-based DR is following onscreen prompts 1.NT 4.0 – The first step. Do I choose custom or express setup?  Choose custom if Changing the hard drive Need to load hardware specific drivers

Performing Disaster Recovery (con’t) 2.Once the NT/2000 setup disks are finished, the DR wizard starts:  DR wizard allows you to select the tape drive where the backup session is located.  Select the partition to recover  Modify partition information 3.Selecting the tape device to use for the DR  Supports remote on NT  Local on NT and Once the NT/2000 setup disks are finished, the DR wizard starts:  DR wizard allows you to select the tape drive where the backup session is located.  Select the partition to recover  Modify partition information 3.Selecting the tape device to use for the DR  Supports remote on NT  Local on NT and 2000

Performing Disaster Recovery (con’t)  Assign the backup sessions to partitions  The DR Wizard allows: Creation of partitions Modification of partition information/size Assigning of sessions to different partitions  Start your restore!  Assign the backup sessions to partitions  The DR Wizard allows: Creation of partitions Modification of partition information/size Assigning of sessions to different partitions  Start your restore!

Special Considerations  Language/OS Support  Check release notes for supported NT/2000 versions  Using MTF tapes  ARCserve can not determine if sessions are full or partial  DR does not support all automated features  Windows 2000 systems with single instance store:  Run AsSISChk.exe from ARCserve directory after booting up Completes restoration of SIS specific information  Machines with EISA partitions:  ARCserve does not recover EISA information  Recreate EISA/other partitions before starting DR process Using DR wizard to repartition may destroy EISA information  Language/OS Support  Check release notes for supported NT/2000 versions  Using MTF tapes  ARCserve can not determine if sessions are full or partial  DR does not support all automated features  Windows 2000 systems with single instance store:  Run AsSISChk.exe from ARCserve directory after booting up Completes restoration of SIS specific information  Machines with EISA partitions:  ARCserve does not recover EISA information  Recreate EISA/other partitions before starting DR process Using DR wizard to repartition may destroy EISA information

What To Look Out For  Custom Setup (NT 4.0)  Make sure the latest drivers are on hand for equipment  If the hard drive was switched  Drives must be attached to the machine like the previous Replace SCSI drives with SCSI, IDE with IDE Attach to the original controller card  Drives must be the same size or larger than original  Switching other hardware  Hardware should be replaced by the same model  After DR is over, NT/2000 will be looking for the original hardware The restored registry thinks it’s on the original machine! Blue screens will occur as the machine boots up, looking for the original SCSI controller, etc.  Custom Setup (NT 4.0)  Make sure the latest drivers are on hand for equipment  If the hard drive was switched  Drives must be attached to the machine like the previous Replace SCSI drives with SCSI, IDE with IDE Attach to the original controller card  Drives must be the same size or larger than original  Switching other hardware  Hardware should be replaced by the same model  After DR is over, NT/2000 will be looking for the original hardware The restored registry thinks it’s on the original machine! Blue screens will occur as the machine boots up, looking for the original SCSI controller, etc.

The Last Resort: What to do if you have an issue 1) Reinstall the OS to x:\tempNT 2) Reapply service packs 3) Reinstall ARCserve or the NT/2000 Client Agent 4) Reapply ARCserve or Client Agent patches 5) Restore the volume 6) Alter the boot.ini to point to the x:\winnt directory Check support document for more information 1) Reinstall the OS to x:\tempNT 2) Reapply service packs 3) Reinstall ARCserve or the NT/2000 Client Agent 4) Reapply ARCserve or Client Agent patches 5) Restore the volume 6) Alter the boot.ini to point to the x:\winnt directory Check support document for more information

Where to Look for More Information:  Option/Agent Specific Manuals  Doc directory on the product CD  ARCserve 2000 manuals are posted on esupport.ca.com   Solution Center: eSearch  Solution Center: Support Wizard  Product Specific FAQ's and Infodoc Indexes  eNews  Bi-monthly technical newsletter  eNews archives at esupport.ca.com  Option/Agent Specific Manuals  Doc directory on the product CD  ARCserve 2000 manuals are posted on esupport.ca.com   Solution Center: eSearch  Solution Center: Support Wizard  Product Specific FAQ's and Infodoc Indexes  eNews  Bi-monthly technical newsletter  eNews archives at esupport.ca.com

WebCast Schedule - Join us next week for...  Wednesday, November 15  12:00 PM EST  New ARCserve Announcements - Tune in to find out the latest data protection advancements in ARCserve 7 for NetWare and Linux  Register:  Wednesday, November 15  12:00 PM EST  New ARCserve Announcements - Tune in to find out the latest data protection advancements in ARCserve 7 for NetWare and Linux  Register:

Questions?