RestoreTableToPointInTime

Restores the specified table to the specified point in time within
EarliestRestorableDateTime and LatestRestorableDateTime.
You can restore your table to any point in time during the last 35 days.
Any number of users can execute up to 4 concurrent restores (any type of restore)
in a given account.

When you restore using point in time recovery, DynamoDB restores your table data to
the state based on
the selected date and time (day:hour:minute:second) to a new table.

Along with data, the following are also included on the new restored table using point
in time recovery:

Global secondary indexes (GSIs)

Local secondary indexes (LSIs)

Provisioned read and write capacity

Encryption settings

Important

All these settings come from the current settings of the source table at the time
of restore.

Errors

For information about the errors that are common to all actions, see Common Errors.

InternalServerError

An error occurred on the server side.

HTTP Status Code: 500

InvalidRestoreTimeException

An invalid restore time was specified. RestoreDateTime must be between EarliestRestorableDateTime
and LatestRestorableDateTime.

HTTP Status Code: 400

LimitExceededException

There is no limit to the number of daily on-demand backups that can be taken.

Up to 50 simultaneous table operations are allowed per account. These operations
include CreateTable, UpdateTable,
DeleteTable,UpdateTimeToLive,
RestoreTableFromBackup, and RestoreTableToPointInTime.

The only exception is when you are creating a table with one or more secondary indexes.
You can have up to
25 such requests running at a time; however, if the table or index specifications
are complex, DynamoDB might temporarily
reduce the number of concurrent operations.

There is a soft account limit of 256 tables.

HTTP Status Code: 400

PointInTimeRecoveryUnavailableException

Point in time recovery has not yet been enabled for this source table.

HTTP Status Code: 400

TableAlreadyExistsException

A target table with the specified name already exists.

HTTP Status Code: 400

TableInUseException

A target table with the specified name is either being created or deleted.

HTTP Status Code: 400

TableNotFoundException

A source table with the name TableName does not currently exist within the subscriber's account.

HTTP Status Code: 400

See Also

For more information about using this API in one of the language-specific AWS SDKs,
see the following: