SQL server on EC2 recovery

The primary purpose of any backup application is to allow recovery in the event of a disaster and must also allow for testing recoveries.Clumio allows you to recover a Microsoft SQL database from the backups that have been created and stored in the cloud. You can restore a database as a new database, overwrite the source database, or for log backups, restore the database to a specific point in time.

The recovery options available to you depend on the recovery model of your Microsoft SQL database. Full recovery contains logs which allow for point in time recovery, simple recovery which allows for database recovery, or bulk logged recovery which has limited log records.

The Backup History calendar displays the dates with available backups. A blue dot represents a Database Backup, an orange square represents Point in Time Recovery, and a purple triangle represents a Bulk Logged Recovery. Click the date corresponding to the backup you want to restore. A popup dialog box displays with a list of backups generated on that day.

Each database backup includes an expiry date after which it is no longer available to be restored. The expiry date is based on the retention schedule of the policy covering the backup. Point in Time recovery and Bulk Logged recovery do not show an expiry date.

Space Requirements to restore a database

The following table shows the space requirements to restore Microsoft SQL databases in Clumio. The term "space" in the table refers to the current space used by the database to be recovered.

Overwrite databaseRestore as a new database
>Full Database Recovery1 x space2 x space
Point-in-time Recovery1 x space2 x space

Recover an MS SQL database as a new database

  1. Navigate to AWS > Protect > AWS Account & Region > MS SQL on EC2 and select the Microsoft SQL host or database you want to recover.
  2. On the Backup History calendar, click the date with a blue dot corresponding to the backup you want to recover. The Recover Database dialog box displays.
  3. In the Recover To section, select Recover as a New Database.
  4. To customize the file path, check the Customize file paths check box. Make sure that the directories exist on the target. If the directories do not exist, or there are filename conflicts, the recovery will fail.
  5. If you have chosen a path that contains an existing database, the Overwrite Database dialog box displays. Click Backto cancel the recovery, or Overwrite Database to proceed with the recovery and overwrite the existing database.
  6. Click Recover.

Recover an MS SQL database to a point in time

Point in time recovery is only available for log backups.

  1. Navigate to AWS > Protect > AWS Account or Region > Microsoft SQL on EC2 and select the Microsoft SQL host or database you want to recover.
  2. On the Backup History calendar, click the date with a purple square corresponding to the backup you want to recover. The Recover to a Point in Time dialog box displays.
  3. Use the Pick a Time dropdown to choose the time to recover to. Only the available recovery times are selectable. Times that are not available for recovery are grayed out.
  4. In the Recover To section, choose either Recover a Microsoft SQL database as a new database or Overwrite the source Microsoft SQL database.
  5. Click Recover.

Recover an MS SQL database to an alternate host

Recover a database to an alternate host.

  1. Navigate to AWS > Protect > AWS Account / Region > MS SQL on EC2 and select the Microsoft SQL hostor database you want to recover.
  2. On the Backup History calendar, click the date corresponding to the backup you want to recover. You can do this for point in time recovery, or for database recovery. The Recover Database dialog box displays.
  3. In the Recover To section, select Recover as a New Database.
  4. Use the Host dropdown to choose a different host than was used during the backup.
  5. Choose an instance from the Instance dropdown.
  6. To customize the file path, check the Customize file paths check box. Make sure that the directories exist on the target. If the directories do not exist, or there are file name conflicts, the recovery will fail. If you have chosen a path that contains an existing database, the Overwrite Database dialog box displays. Click Back to cancel the recovery, or Overwrite Database to proceed with the recovery and overwrite the existing database.
  7. Click Recover.