Migrating the database to Amazon RDS

Expand all | Collapse all

You can migrate your Kaspersky Security Center database from an on-premises device to an Amazon S3 instance that supports Amazon RDS. To do this, you need an S3 bucket for an RDS database and an IAM user account with AmazonS3FullAccess permission for this S3 bucket.

To perform the migration of the database:

  1. Make sure that you have created an RDS instance (refer to Amazon RDS reference pages for more information).
  2. On your physical Administration Server (on-premises), run the Kaspersky Backup utility to back up Administration Server data.

    You must make sure that the file is named backup.zip.

  3. Copy the backup.zip file to the EC2 instance on which Administration Server is installed.

    Make sure that you have enough disk space on the EC2 instance on which Administration Server is installed. In the AWS environment, you can add disk space to your instance to accommodate the process of database migration.

  4. On the AWS Administration Server, start the Kaspersky Backup utility again in interactive mode.

    The Backup and Restore Wizard starts.

  5. At the Select action step, select Restore Administration Server data and click Next.
  6. At the Restore settings step, click the Browse button next to the Folder for storage of backup copies.
  7. In the Sign In to Online Storage window that opens, fill in the following fields and then click OK:
    • S3 bucket name
    • Backup folder
    • Access key ID
    • Secret key
  8. Select the Migrate from local backup option. The Browse button becomes available.
  9. Click the Browse button to choose the folder on the AWS Administration Server where you copied the backup.zip file.
  10. Click Next and complete the procedure.

Your data will be restored to the RDS database using your S3 bucket. You can use this database for further work with Kaspersky Security Center in the AWS environment.

The addresses of web pages cited in this document are correct as of the Kaspersky Security Center release date.

See also:

Scenario: Deployment for cloud environment

Page top