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

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

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a

Debugging a Tridion 2011 Event System

OK, so you wrote your Tridion Event System. Now it's time to debug it. I know this is a hypothetical situtation -- your code never needs any kind of debugging ;) but indulge me... Recently, Alvin Reyes ( @nivlong ) blogged about being difficult to know how exactly to debug a Tridion Event System. More exactly, the question was " What process do I attach to for debugging even system code? ". Unfortunately, there is no simple or generic answer for it. Different events are fired by different Tridion CM modules. These modules run as different programs (or services) or run inside other programs (e.g. IIS). This means that you will need to monitor (or debug) different processes, based on which events your code handles. So the usual suspects are: dllhost.exe (or dllhost3g.exe ) - running as the MTSUser is the SDL Tridion Content Manager COM+ application and it fires events on generic TOM objects (e.g. events based on Tridion.ContentManager.Extensibility.Events.CrudEven