What files are created for Disaster Recovery

DR files are located either
C:\Program Files\ComputerAssociates\ARCserve\dr\<machine name>
or
C:\Program Files\Computer Associates\BrightStor\EB\DR\<machine name>

For remote backups they will also be found under the Client Agent directory.

Here is a typical directory listing for an ARCserve 2000 remote backup.
07/05/2001 02:55p <DIR> ..
07/05/2001 02:55p 0 ARCBKUP.W2K
10/26/1999 07:13a 80,144 e100bnt5.sys
07/05/2001 02:55p 8,192 <machine name>.DRF
07/05/2001 02:55p 12,288 <machine name>_CHEY
07/05/2001 02:55p 8,192 <machine name>_DLST
07/05/2001 02:55p 8,192 <machine name>_DTBL
07/05/2001 02:55p 8,192 <machine name>_PRDS
07/05/2001 02:55p 512 LASTDR.INF
07/05/2001 02:55p 12 macaddr.str
12/07/1999 06:00a 26,060 net557.inf
07/05/2001 02:55p 8,192 nonpnp_drf
07/05/2001 02:55p 8,208 partinfo.ppp
07/05/2001 02:55p 8,192 w2ktcpip_drf
13 File(s) 176,376 bytes

This directory listing will be different depending on things like if it is ARCserve 2000, BAB, or BEB. Also if it is a remote or local backup, type of harddisk subsystem, type of NIC, version of Windows. So depending on these things the file names might be a little different and there might be more or less files.

Here is a description on the files.
W2KRMT.DMP
Size : 1024 bytes
Format : Encrypted dump of NetworkLogInfo {} structure
Use : Show the backup is for a remote machine and stores the machine name of the server and also domain, user name and password needed to access the machine in an encrypted format.

BEBRDR
Size : 0 bytes
Format : Signature file
Use : Backups in BEBR generate this file as a signature to show that improved encryption method ( TngCrypt() ) has been used for storing user name, password etc in W2KRMT.DMP.

CABKUP.W2K
Size : 0 bytes
Format : Signature file
Use : Signature file to show that the backed up machine is W2K.

MACADDDR.STR
Size : 12 bytes
Format : ASCII txt
Use : Stores the Mac address of the backed up machine.

MACHINENAME.DRF
Size: minimum 8k
Format : Registry hive
Use : Matches the data to be restored in DR to the tape, session no etc. At a minimum it should have data for one partition, the system state and DR session. It also contains data like the DR server (DRLocalComputerName), DR client (DRComputerName), DR version and system time. This information is used during remote or local DR to get the data to be restore in the machine.

PARTINFO.PPP
Size : minimum 4014 bytes
Format : Dump of PARTITION_INFORMATION structure
Use : Stores the partition information of the client machine. During the blue screen phase of DR country.sys driver loads this file and restores the original machine partition.

MACHINENAME_DLST
Size : min. 8k
Format : Registry Hive
Use : Stores the: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Cheetah\DiscoveryImplementationList\ASBRDCST hive.

MACHINENAME_DTBL
Size : min 8k
Format : Registry hive
Use :

MACHINENAME_PDRS
Size : min 8k
Format : Registry hive
Use : Stores the HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Cheetah\Products hive.

NETWORK DRIVERS
Size: Varied
Format : Windows driver
Use : Driver for network card(s) in the client machine. Used to install the network card during remote DR in W2K.

NETWORK DRIVER INFORMATION FILES( INF FILES )
Size: Varied
Format : Windows INF file
Use : INF file needed to install network card(s) in the client machine during remote DR.

W2KTCPIP_DRF
Size : min 8k
Format : Registry hive
Use : Used to save network configuration on the client machines. Inside this hive there are nodes for each network interface in the client machine. For example if it has two network interfaces it will have two nodes, ô0ö and ô1ö. The entries in each node will vary depending on if the interface is in static Ip( Figure 2 ) or DHCP( Figure 3 ) mode. These entries are used to configure the tcpip network parameters during DR.

NONPNP_DRF
Size : min 8k
Format registry hive
Use : This file is not used in DR. If the client system has legacy non-pnp and play network adapters , the DMA, IRQ settings of the adapter are stored so that user can read them and manually setup the adapter during DR.

Depending on the version the registry paths might be different.