Skip to main content

AWS RDS Backup Restore

This post describes a backup/restore procedure for the Content Manager database in an Amazon Web Services (AWS) environment). The database is a MSSQL instance running on as Amazon Relational Database Service (RDS).

The existing database is from an SDL Tridion 2013 environment, and as such, after the restore in the new SDL Web 8.5 environment, it will have to be upgraded to SDL Web 8.5.

Performing the backup implies taking the database offline and executing the stored procedure:

exec msdb.dbo.rds_backup_database 'Tridion_cm_2013', 'arn:aws:s3:::mybackup/Tridion_cm_2013.bak'

The procedure is described in

Performing the restore implies executing the following stored procedure in the new RDS database:

exec msdb.dbo.rds_restore_database 'Tridion_cm_2013','arn:aws:s3:::mybackup/Tridion_cm_2013.bak',''

While the restore is running, you can track the progress by calling rds_task_status

exec msdb.dbo.rds_task_status @task_id=4

The restore process is quite lengthy, but a log is available in one of the fields returned by rds_task_status:

Task execution has started.
Tridion_cm_2013.bak: Completed processing 5.02% of S3 chunks.
RESTORE DATABASE successfully processed 9358282 pages in 1409.730 seconds (51.862 MB/sec).
Tridion_cm_2013.bak: S3 processing completed successfully
Command execution completed successfully.

As usual, after restore, the old database logins are not available anymore, because they have been disassociated between the old and new databases instances. The existing TCMDBUser user must be altered in order to associate it with the new TCMDBUser user from the new database:



Popular posts from this blog

Scaling Policies

This post is part of a bigger topic Autoscaling Publishers in AWS . In a previous post we talked about the Auto Scaling Groups , but we didn't go into details on the Scaling Policies. This is the purpose of this blog post. As defined earlier, the Scaling Policies define the rules according to which the group size is increased or decreased. These rules are based on instance metrics (e.g. CPU), CloudWatch custom metrics, or even CloudWatch alarms and their states and values. We defined a Scaling Policy with Steps, called 'increase_group_size', which is triggered first by the CloudWatch Alarm 'Publish_Alarm' defined earlier. Also depending on the size of the monitored CloudWatch custom metric 'Waiting for Publish', the Scaling Policy with Steps can add a difference number of instances to the group. The scaling policy sets the number of instances in group to 1 if there are between 1000 and 2000 items Waiting for Publish in the queue. It also sets the

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: I stumbled upon the following post from 2008 (!!!), , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as

Toolkit - Dynamic Content Queries

This post if part of a series about the  File System Toolkit  - a custom content delivery API for SDL Tridion. This post presents the Dynamic Content Query capability. The requirements for the Toolkit API are that it should be able to provide CustomMeta queries, pagination, and sorting -- all on the file system, without the use third party tools (database, search engines, indexers, etc). Therefore I had to implement a simple database engine and indexer -- which is described in more detail in post Writing My Own Database Engine . The querying logic does not make use of cache. This means the query logic is executed every time. When models are requested, the models are however retrieved using the ModelFactory and those are cached. Query Class This is the main class for dynamic content queries. It is the entry point into the execution logic of a query. The class takes as parameter a Criterion (presented below) which triggers the execution of query in all sub-criteria of a Criterio