Restoring After Executables Disk Crash 

Prerequisites

The procedure described here assumes that all files apart from the R/3 database and transaction logs are on a separate disk. If this disk crashes, you cannot use your R/3 System, your SQL Server or your operating system. Before you can begin to rectify the situation, you need a functioning operating system. In a first step you must therefore install and boot an auxiliary NT System. You can then start the restore procedure from this system.

Procedure

Overview of the Restore Steps

 

  1. Replace the damaged disks.
  2. Install an auxiliary NT system.
  3. Restore the files that were lost on the crashed disk using the most recent full Windows NT backup. Refer to the Windows NT online documentation to find out how to restore an NT backup.

    4. In this disk crash scenario, the R/3 database and transaction logs are unaffected. Do not reload these from the Windows NT Backup.

  4. Reboot your server with the restored, primary NT system.

The executables disk has now been restored to the state it had at the time of the last full Windows NT backup.

The msdb databases may not be up to date. It is therefore recommended that you now restore the most recent backup of this database.
For more information, see Restoring the msdb Database from Device