When a new system image is created, Vantage re-provisions hot standby nodes based on the new system image.
Creating a system image requires a reboot of the target node used to create the image. On a single-node system, the system image creation process automatically targets the one available node. After the system reboots, monitor the status of the instance using the AWS CloudWatch logs in /var/log. If you do not complete this procedure, Vantage uses the image generated when you deployed the instance.
When the software upgrade script runs as a part of the following procedure, it creates a temporary d2.xlarge instance and a 350 GB EBS volume. This instance and volume is automatically deleted, but you will incur a minimal charge. Software upgrades are stored in an AMI in your account for node failure recovery purposes or if you scale out. Charges for this AMI vary per customer.
- Stop the database.
# tpareset –x –y stop for swupgrade
- Verify the database is in a DOWN/HARDSTOP state.
# pdestate -a
PDE state: DOWN/HARDSTOPPutting the database in this state may take several minutes. - Display a list of running nodes by instance ID, BYNET® name, and PMA ID.
# tdc-image --list-nodes
Following is an example of output:Instance ID Bynet Name PMA ID -------------------- ---------------- ---------------- i-1a78a202 byn001-01 33 i-78a40160 byn001-02 34 i-2bd57033 byn001-03 35 i-5bd87d43 byn001-04 36 i-1878a200 byn001-05 37 i-a57ba1bd byn001-06 38
- Specify the instance ID, BYNET name, or PMA ID to use to create the instance.
# tdc-image --instance-id instance_ID # tdc-image --bynet-name BYNET_NAME # tdc-image --pma-id PMA_ID
For example:# tdc-image -–bynet-name byn001-03
where byn001-03 is the BYNET name. - Start the database.
# /etc/init.d/tpa start
- Ensure the database is running again.
# pdestate -w
PDE state: RUN/STARTEDPutting the database in this state may take several minutes.