Example Scenarios for Updating Host Name References

Example 1: The Machine Name Has Changed in a Single-Machine Deployment

In this example, a single-machine deployment is installed on HOST01.example.com, and the name of the machine has been changed to HOST99.example.com. All occurrences of the machine's fully qualified name and short name need to be updated throughout the deployment to refer to the new name.
Diagram of single-machine deployment with a change to the host machine name
In this scenario, you would use the Update Host Name References tool as follows:
  1. Create a complete system backup of the machine, including a correct backup of the metadata server.
  2. Start the metadata server and stop all of the other servers.
  3. Run the Update Host Name References tool on the machine.
    In the Specify Host Names dialog box, you must enter both the fully qualified host names and the short host names. (You cannot perform a DNS lookup when the name of an existing machine has changed.) You do not need to enter the IP address, because it remains the same in this scenario. Specify the following:
    • Old host name: HOST01.example.com,HOST01
    • New host name: HOST99.example.com,HOST99
    • Perform DNS lookup: Not selected
  4. Perform the necessary manual steps, as listed in the report. Because the metadata server host name has changed, update the connection profiles for client applications where necessary.
  5. Start the servers and perform the validation steps.
  6. Create a complete system backup of the machine, including a correct backup of the metadata server.

Example 2: The Name of a SAS Application Server Host Machine Has Changed

In this example, The SAS Metadata Server, SAS Application Server, and SAS middle tier are installed on separate machines. The SAS application server is installed on a machine called APP01.example.com, and the name of this machine has been changed to APP99.example.com. All occurrences of the application server machine's fully qualified name and short name need to be updated throughout the deployment to refer to the new name.
Diagram of single-machine deployment with a change to the application server host machine name
In this scenario, you would use the Update Host Name References tool as follows:
  1. Create a complete system backup of each machine in the deployment, including a correct backup of the metadata server.
  2. Start the metadata server, and stop all of the other servers.
  3. Run the Update Host Name References tool on MET01.example.com.
    In the Specify Host Names dialog box, you must enter both the fully qualified host names and the short host names. (You cannot perform a DNS lookup when the name of an existing machine has changed.) You do not need to enter the IP address, because it remains the same in this scenario. Specify the following:
    • Old host name: APP01.example.com,APP01
    • New host name: APP99.example.com,APP99
    • Perform DNS lookup: Not selected
  4. Run the Update Host Name References tool on APP99.example.com. In the Specify Host Names dialog box, make exactly the same entries that you made in step 3.
  5. Run the Update Host Name References tool on MID01.example.com. In the Specify Host Names dialog box, make exactly the same entries that you made in step 3.
  6. Perform the necessary manual steps, as listed in the report.
  7. Start the servers and perform the validation steps.
  8. Create a complete system backup of the deployment, including a correct backup of the metadata server.

Example 3: The Network Domain Name Has Changed

In this example, a SAS deployment is installed in a network domain called example.com, and the domain name has been changed to orionstarsports.com. All occurrences of fully qualified host names in the deployment need to be updated to incorporate the new domain name.
Diagram of single-machine deployment with a change to the network domain name
In this scenario, you would use the Update Host Name References tool as follows:
  1. Create a complete system backup of each machine in the deployment, including a correct backup of the metadata server.
  2. Start the metadata server, and stop all of the other servers.
  3. Run the Update Host Name References tool on MET01.orionstarsports.com.
    In the Specify Host Names dialog box, you need to enter only the fully qualified host names, because the short host names and the IP addresses remain the same in this scenario. You cannot perform a DNS lookup when the names of existing machines have been changed. Specify the following:
    • Old host name: MET01.example.com,APP01.example.com,MID01.example.com
    • New host name: MET01.orionstarsports.com,APP01.orionstarsports.com,MID01.orionstarsports.com
    • Perform DNS lookup: Not selected
  4. Run the Update Host Name References tool on APP01.orionstarsports.com. In the Specify Host Names dialog box, make exactly the same entries that you made in step 3.
  5. Run the Update Host Name References tool on MID01.orionstarsports.com. In the Specify Host Names dialog box, make exactly the same entries that you made in step 3.
  6. Perform the necessary manual steps, as listed in the report. Because the fully qualified host name for the metadata server has changed, update the connection profiles for client applications where necessary.
  7. Start the servers and perform the validation steps.
  8. Create a complete system backup of the deployment, including a correct backup of the metadata server.

Example 4: A Single-Machine Deployment Has Been Cloned to Another Machine

In this example, a single-machine deployment is installed on HOST01.example.com, and the deployment has been cloned to another machine called HOST99.example.com. In the new deployment, all references to the fully qualified host name, short host name, and IP address need to be updated to refer to the new host machine.
Diagram of a single-machine deployment cloned to a new machine
In this scenario, you would use the Update Host Name References tool as follows:
  1. Create a complete system backup of HOST01.example.com, including a correct backup of the metadata server.
  2. Set up the new machine (HOST99.example.com) by using cloning, ghosting, or virtualization software. For details, see Step 3: Change Existing Names at the Operating System Level, or Set Up New Machines to Be Identical to the Current Machines.
  3. Start the metadata server on the new machine (HOST99.example.com). Stop all of the other servers on the new machine, and stop the middle-tier processes on the old machine (HOST01.example.com).
  4. Run the Update Host Name References tool on HOST99.example.com.
    In the Specify Host Names dialog box, you need to enter only the fully qualified host names. The DNS lookup identifies all other forms of the host names so that they can be updated correctly. Specify the following:
    • Old host name: HOST01.example.com
    • New host name: HOST99.example.com
    • Perform DNS lookup: Selected
  5. Perform the necessary manual steps, as listed in the report. Because the metadata server host name has changed, update the connection profiles for client applications where necessary. If the deployment includes a middle tier, and if the new deployment will be running concurrently with the old deployment, then the multicast parameters might also need to be modified.
  6. Start the servers and perform the validation steps.
  7. Create a complete system backup of the new machine, including a correct backup of the metadata server.

Example 5: A Multiple-Machine Deployment Has Been Cloned to a New Set of Machines

In this example, a multiple-machine deployment is installed on MET01.example.com, APP01.example.com, and MID01.example.com. Cloning software has been used to create a mirror of the deployment on a different set of machines called MET02.example.com, APP02.example.com, and MID02.example.com. In the new deployment, all occurrences of each machine's fully qualified name, short name, and IP address need to be updated to refer to the new machines.
Diagram of a multiple-machine deployment cloned to a new set of machines
In this scenario, you would use the Update Host Name References tool as follows:
  1. Create a complete system backup of each machine in the original deployment, including a correct backup of the metadata server.
  2. Set up the new machines (MET02.example.com, APP02.example.com, and MID02.example.com) by using cloning, ghosting, or virtualization software. For details, see Step 3: Change Existing Names at the Operating System Level, or Set Up New Machines to Be Identical to the Current Machines.
  3. Start the metadata server on the new metadata server machine (MET02.example.com). Stop all of the other servers in the new deployment, and stop the middle-tier processes in the old deployment.
  4. Run the Update Host Name References tool on MET02.example.com.
    In the Specify Host Names dialog box, you need to enter only the fully qualified host names. The DNS lookup identifies all other forms of the old and new host names so that they can be updated correctly. Specify the following:
    • Old host name: MET01.example.com,APP01.example.com,MID01.example.com
    • New host name: MET02.example.com,APP02.example.com,MID02.example.com
    • Perform DNS lookup: Selected
  5. Run the Update Host Name References tool on APP02.example.com. In the Specify Host Names dialog box, make exactly the same entries that you made in step 4.
  6. Run the Update Host Name References tool on MID02.example.com. In the Specify Host Names dialog box, make exactly the same entries that you made in step 4.
  7. Perform the necessary manual steps, as listed in the report. Because the metadata server host name has changed, update the connection profiles for client applications where necessary. If the new deployment will be running concurrently with the old deployment, then the multicast parameters might also need to be modified.
  8. Start the servers and perform the validation steps.
  9. Create a complete system backup of the new deployment, including a correct backup of the metadata server.

Example 6: The Metadata Server Has Been Cloned to a New Machine

In this multiple-machine deployment example, cloning software has been used to move the metadata server from a machine called MET01.example.com to a new machine called MET99 example.com. All occurrences of the qualified name, short name, and IP address for the metadata server host machine need to be updated throughout the deployment to refer to the new host machine.
Diagram of a multiple-machine deployment with the metadata server cloned to a new machine
In this scenario, you would use the Update Host Name References tool as follows:
  1. Create a complete system backup of the deployment, including a correct backup of the metadata server.
  2. Set up the new machine (MET99.example.com) by using cloning, ghosting, or virtualization software. For details, see Step 3: Change Existing Names at the Operating System Level, or Set Up New Machines to Be Identical to the Current Machines.
  3. Start the metadata server on the new machine (MET99.example.com). Stop all of the other servers in the deployment.
  4. Run the Update Host Name References tool on MET99.example.com.
    In the Specify Host Names dialog box, you need to enter only the fully qualified host names. The DNS lookup identifies all other forms of the host names so that they can be updated correctly. Specify the following:
    • Old host name: MET01.example.com
    • New host name: MET99.example.com
    • Perform DNS lookup: Selected
  5. Run the Update Host Name References tool on APP01.example.com. In the Specify Host Names dialog box, make exactly the same entries that you made in step 4.
  6. Run the Update Host Name References tool on MID01.example.com. In the Specify Host Names dialog box, make exactly the same entries that you made in step 4.
  7. Perform the necessary manual steps, as listed in the report. Because the metadata server host name has changed, update the connection profiles for client applications.
  8. Start the servers and perform the validation steps.
  9. Create a complete system backup of the deployment, including a correct backup of the metadata server.
Copyright © SAS Institute Inc. All rights reserved.