FAQ for DBS sandbox instances
This page answers common questions about the sandbox feature of Database Backup (DBS).
Pricing
How am I charged for the sandbox feature?
See DBS sandbox fees.
Restore time range
What is the time range for restoring sandbox instance data?
The available restore range depends on whether log backup (also called incremental backup) is enabled for the source database instance.
| Log backup status | Restore range | Granularity |
|---|---|---|
| Enabled | From when the most recent full backup set was created (before sandbox was enabled) to when the last binary log file was created | Accurate to the second |
| Disabled | From when the most recent full backup set was created (before sandbox was enabled) to when the last full backup set was created | Full backup timestamps only |
To enable log backup, see:
-
ApsaraDB RDS for MySQL: Use the log backup feature for an ApsaraDB RDS for MySQL instance
-
Self-managed databases: Enable or disable incremental log backup
What is the most recent point in time I can restore to?
The most recent restore point depends on whether log backup is enabled for the source database:
-
Log backup disabled: The most recent restore point is when the last full backup set was created.
-
Log backup enabled: The most recent restore point is when the last binary log file was created.
To find the exact restore point:
-
ApsaraDB RDS source: Go to the Backup and Restoration page in the ApsaraDB RDS console.
-
Self-managed database source: Go to the details page of the backup schedule in the DBS console.
Why can I only restore to a point in time when a full backup set was created?
Log backup is disabled for the source database instance. Without binary logs, DBS cannot replay incremental changes and can only restore to full backup set timestamps.
To restore to an arbitrary point in time, enable log backup. See:
-
ApsaraDB RDS for MySQL: Use the log backup feature for an ApsaraDB RDS for MySQL instance
-
Self-managed databases: Enable or disable incremental log backup
Creating a sandbox instance
Do the specifications of a sandbox instance affect the restore time?
No. Restore time is independent of sandbox instance specifications. Higher specifications improve query performance after restore, but do not speed up the restore process itself.
How long does it take to restore sandbox instance data?
Restore time depends on the restore method and the volume of binary logs to replay:
| Restore method | Speed | Notes |
|---|---|---|
| Restore to a snapshot | ~2 minutes per 1 TB | Fastest method; recommended when the target time aligns with a snapshot |
| Restore to a specific point in time | 512 MB per 5 minutes (binary log replay) | DBS first restores to the nearest snapshot before the target time, then replays binary logs to reach the exact point |
When restoring to a specific point in time, total time = snapshot restore time + binary log replay time.
When does DBS generate snapshots for sandbox instances?
DBS generates snapshots in the following situations:
-
When the sandbox feature is enabled for the first time.
-
When a full backup set is created for the source database instance.
-
(Log backup enabled only) On a rolling basis as DBS reads binary log files, approximately every 10 minutes.
Using a sandbox instance
How do I connect to a sandbox instance?
Connect using the virtual private cloud (VPC) endpoint of the sandbox instance. The endpoint is listed in the sandbox instance list.
For step-by-step instructions, see Use DMS to access sandbox instances or Use ECS to access sandbox instances.
Why can't I log on to a sandbox instance with an account created after the sandbox was created?
Sandbox instances reflect the state of the backup data used to create them. Accounts created after the sandbox instance was created do not exist in that backup data.
Log on using the database accounts and passwords that existed in the source database when the backup data was captured — that is, accounts created before the sandbox instance was created.
How do I keep the data in a sandbox instance?
Use Data Transmission Service (DTS) to migrate the data to an ApsaraDB RDS for MySQL instance. See Migrate data from a sandbox instance to an ApsaraDB RDS for MySQL instance.