Creating a System Image

You can use this procedure to create a new system image, such as in the restoration process of a node failure or for deploying new instances for unfolding. If this image is not created, the software on the recovered instance will not match and the database cannot start if a node failure occurs. In addition, you must create a new system image after upgrading software or adding the system to Teradata QueryGrid.

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, Teradata Database 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 charge of less than $1.00. Software upgrades are stored in an AMI in your account for node failure recovery purposes or if you use the Unfold feature. Charges for this AMI vary per customer.

  1. Stop the database.
    # tpareset –x –y stop for swupgrade
  2. Verify the database is in a DOWN/HARDSTOP state.
    # pdestate -a
    Putting the database in this state may take a number of minutes.
  3. Display a list of running nodes by instance ID, BYNET name, and PMA ID.
    # tdc-nodestart-post-swupgrade --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
  4. Specify either the instance ID, BYNET name, or PMA ID to use to create the instance.
    # tdc-nodestart-post-swupgrade --instance-id instance_ID
    # tdc-nodestart-post-swupgrade --bynet-name BYNET_NAME
    # tdc-nodestart-post-swupgrade --pma-id PMA_ID
    For example:
    # tdc-nodestart-post-swupgrade -–bynet-name byn001-03
    where byn001-03 is the BYNET name.
  5. Start the database.
    # /etc/init.d/tpa start
  6. Ensure the database in running again.
    # pdestate -w
    PDE state: RUN/STARTED
    Putting the database in this state may take a number of minutes.

results matching ""

    No results matching ""