Page Comparison

...

you can start the restore process on your own.

Table of contents

...

General usage instructions

The general unsage instructions for the cloud managment tool suite r3 can be found here.

Step-by-step guide

Show help context

~$ r3 db restore -h
Create a Restore Database Server from a Snapshot.

optional arguments:
  -h, --help            show this help message and exit
  --env ENVIRONMENT, --environment ENVIRONMENT
                        The short name of the desired Environment (default:
                        this).
  --loglevel {INFO,ERROR}
                        Define Loglevel for Execution (default: INFO)

  snapshot_id           SnapshotIdentifier of a Snapshot to restore a Database
                        Server from.
  --db-instance-class INSTANCE_CLASS
                        DB instance class of restore database

Restore a database from a snapshot

1. Obtain the identifier of the snapshot, whose data you want to restore using "r3 db list".

2. Initiate the restore process and wait until it finishes: r3 db restore <snapshot-id>

3. Retrieve the database endpoint provided at the end of the process

   Code Block
   language text title database restore example linenumbers true
   ~$ r3 db restore restore-snapshot-2017-10-23-10-31 # Response 2017-10-23 12:45:37,051 - r3-osumi - INFO - Starting DB Restore: This process can take up to 15 Minutes! 2017-10-23 12:45:37,051 - r3-osumi - INFO - Starting restore for Snapshot restore-snapshot-2017-10-23-10-31 2017-10-23 12:45:37,261 - r3-osumi - INFO - Got details on restore-snapshot-2017-10-23-10-31 2017-10-23 12:45:37,261 - r3-osumi - INFO - Got VPCID vpc-75e3561c for Target Env {'Environment': 'test', 'Company': 'root360', 'Project': 'backend'} 2017-10-23 12:45:37,390 - r3-osumi - INFO - Got Param Group ralf-osumi-test-rds-r3rdsparamgrouputf8-5j7zdzwn3ypf 2017-10-23 12:45:37,881 - r3-osumi - INFO - Got Security Groups ['sg-2146d148'] 2017-10-23 12:45:37,917 - r3-osumi - INFO - Got DBSubnetGroup root360-backend-test-vpc-rdsdbsubnetgroup-1kztrdy6yo728 2017-10-23 12:45:37,917 - r3-osumi - INFO - Waiting for restore-snapshot-2017-10-23-10-31 to be available 2017-10-23 12:45:37,917 - r3-osumi - INFO - Creating Safety copy restore-snapshot-2017-10-23-12-45 of restore-snapshot-2017-10-23-10-31 2017-10-23 12:45:38,122 - r3-osumi - INFO - Waiting for Snapshot Copy restore-snapshot-2017-10-23-12-45 2017-10-23 12:46:55,542 - r3-osumi - INFO - Started Restore for restore-db-2017-10-23-12-45. Waiting on return signal... 2017-10-23 12:54:27,451 - r3-osumi - INFO - Modify after Restore for restore-db-2017-10-23-12-45 2017-10-23 12:54:27,824 - r3-osumi - INFO - Wating to perform Restart after modify. 2017-10-23 12:54:57,983 - r3-osumi - INFO - Updating status for restore-db-2017-10-23-12-45 2017-10-23 12:55:28,173 - r3-osumi - INFO - Updating status for restore-db-2017-10-23-12-45 2017-10-23 12:55:58,355 - r3-osumi - INFO - Updating status for restore-db-2017-10-23-12-45 2017-10-23 12:56:28,546 - r3-osumi - INFO - Updating status for restore-db-2017-10-23-12-45 2017-10-23 12:56:28,626 - r3-osumi - INFO - Initiated reboot of Instance. Environment: test Company: root360 Project: backend +-------------+-------------------------------------------------------------------------+ | Resource | Identifier | +-------------+-------------------------------------------------------------------------+ | Endpoint | restore-db-2017-10-23-12-45.cw8zdc1gbk6g.eu-central-1.rds.amazonaws.com | | Safety Copy | restore-snapshot-2017-10-23-12-45 | +-------------+-------------------------------------------------------------------------+

   
   

4. Using the provided endpoint you can now proceed, e.g. connect to the database from the Jump-Server or any application instance.

   
   

   Info
   title Database User and Password
   On database restore, database users and passwords are inherited from the origin database, so you can connect seamlessly with your known credentials.

   
   

Related article

...