User guide

5. Click Resize.
6. Click Status, and review the resize status information to see the resize progress.
Step 5: Copy Post-Snapshot Data from the Source
to the Target Cluster
For the purposes of this tutorial, this step provides a simple set of COPY statements to load data from
Amazon S3 into Amazon Redshift. This step is included to simulate bringing the target cluster up-to-date
with the same data as the source cluster. It is not meant to demonstrate an effort to bring an actual
production environment into line between the source and target cluster. In production environments, your
own ETL process will determine how load your target cluster with all the same data as the source cluster
after the snapshot was taken.
If there have been multiple loads after the snapshot was taken, you’ll need to make sure that you rerun
the loads in the target database in the same order as they were run in the source database. Additionally,
if there continue to be loads into the source database while you are working on bringing the target cluster
up-to-date, you will need to repeat this process until the target and source match, and find a suitable time
to rename the clusters and switch applications to connect to the target database.
In this example, let’s suppose that your ETL process loaded data into the source cluster after the snapshot
was taken. Perhaps Amazon Redshift was still in the process of restoring the target cluster from the
snapshot, or resizing the target cluster. There were some new categories, events, dates, and venues
added to the TICKIT database.You now need to get this same data into the target cluster before you
switch to use it going forward.
API Version 2012-12-01
233
Amazon Redshift Management Guide
Step 5: Copy Post-Snapshot Data from the Source to
the Target Cluster