Chapter 12 - Renaming a Server
You need to rename a server when:
![]() |
Replacing an old server with a new one |
![]() |
Giving a new name to an existing server |
To rename a server, you follow a procedure similar to the one used when re-installing software. The goal is to return the server to the network in the state it was in prior to the name change. Since the server name is linked to information in StreetTalk and STDA databases throughout the network, you need to eliminate references to the old server name.
Caution: Once you begin to reload server information, you cannot reverse the procedure.
Always load the most recent complete system backup and subsequent incremental backups. If you do not load a full system backup, you must manually enter the start-up information for the server as you would during an initial installation (server name, first group name, and first organization names).
Steps Involved in Renaming a Server
This section describes the steps for renaming a server. Renaming a server requires a considerable amount of time, depending on the number of services and StreetTalk groups residing on the server. Plan on allowing a minimum of five hours to complete the necessary procedures.
Read this section in its entirety before renaming a server. Renaming a server involves the following eight steps:
1. Preparing - Create backups and record current server and service configurations.
2. Moving services and groups - Delete existing services that are located on the server, then move all StreetTalk groups to backup media.
3. Re-installing system software - Remove the existing name of the server by reloading system software from release media, treating the server as if it were the first server on a network.
4. Renaming the server - Provide the server with a new name, and other first server information.
5. Restoring server information - Re-enter the server configuration, install third-party software, and reapply patches.
6. Moving StreetTalk groups - Move StreetTalk groups from tape back to the server.
7. Restoring Services - Create and restore services.
8. Administering the server - Verify that the server is operating properly. Edit user profiles and verify administrative access to the server.
Each step is described in detail in this chapter.
Caution: Renaming a server can cause StreetTalk problems on your network if the procedures are not followed carefully. Before you begin, make sure you are familiar with all the procedures involved in renaming a server.
![]() |
Create two complete system backups and confirm the readability of the media (tape or diskettes). A second backup is useful should problems occur when restoring information from the first backup. Refer to Chapter 3 for information on creating a complete backup. |
![]() |
Run the REPORT program for the server, and specify all groups maintained on the server. This program creates an on-line file that lists the complete StreetTalk information for the server. The file provides further backup protection in case there is a problem during the renaming procedure. |
![]() |
Use the OPERATE command to review your server configuration. You will re-enter configurations when you add the services later in the server renaming process. For more information on using the OPERATE command, refer to the Command Reference. |
![]() |
Record the names of all services located on your server. |
![]() |
Write down all of the server configuration information. This includes LAN card configuration, file cache and communications buffer allocation, TCP/IP configuration, remote server connections, and scheduled backup times. These configurations will need to be re-entered later in the server renaming process. |
![]() |
Locate the following items: - Worksheets - For recording the server and service configuration information you need when you restore services. - Documentation - The procedures in this section include references to the following Banyan documentation: |
You are now ready to begin moving services and groups. Continue with the procedure in the next section.
Moving Services and Groups from the Server to Backup Media
You need to delete services before moving groups from the server. Deleting services cleans up StreetTalk information associated with groups, so that StreetTalk errors do not occur when you remove groups.
Remove a service only if it actually resides on the server you are renaming. The Service Monitor screen displays information about a service even if the service's StreetTalk group resides on another server. Its status appears on the Service Monitor screen as "Inconsistent" during the remainder of the server renaming process. The service operates properly after the renaming process is complete.
Caution: If you delete your own group or the services in your group, you lose the ability to use the network or administer servers.
To Delete Services on the Server
1. From a DOS workstation, enter MSERVICE. The Manage Services screen appears.
2. Choose SEARCH for other services. The Search For Services screen appears.
3. Choose Services on a Particular Server. The list of servers on the network appears.
4. Choose the server from which you want to delete services. The Manage Services screen appears.
5. Choose SELECT from list below. The first service on the list becomes highlighted.
6. Choose the service you want to delete. The Manage A Service screen appears.
7. Choose CONTROL the service. The Control A Service screen appears.
8. Choose STOP service. The service stops.
9. Press ESC. The Manage A Service screen appears.
10. Choose DELETE service. You are prompted to confirm that you want to delete the service.
11. Choose YES. The service is deleted.
12. From the Operator Menu on the server console, choose Shut down server software and return to the OPERATOR MENU. Refer to Chapter 1 for information about shutting down server software.
13. Move all groups on the server to backup media except the group servername@Servers (refer to Chapter 3 for information about moving StreetTalk groups). Move each group to its own tape or diskette.
Note: You do not back up the group servername@Servers because, after the renaming process, you manually rebuild the group to restore any list (such as an AdminList) that existed for it.
14. Restart the server while it is connected to the network. This process informs the other servers that the groups of this server were removed from the network. The time required for all servers in your network to acknowledge the removal varies, depending on the size of your network.
Note: Verify that WAN connections to your network are operating. Otherwise groups may be in contention.
15. Verify that all servers on the network have removed information for the deleted groups by running MGROUP from different DOS workstations on your network. When you can no longer access these groups from anywhere on the network, you are ready to reload your system software.
Before re-installing system software, complete the following tasks:
![]() |
Remove the server from the network by disconnecting all of its LAN cables. |
![]() |
Locate your Banyan release software, any Banyan patches that you want to apply, and any third-party software you plan to reinstall. |
To Re-install the Release Software
1. If the server is in operation, shut down services. Refer to Chapter 1 for information on shutting down the server.
2. Begin a full installation of the software from the release media according to the instructions in the Server Installation Guide. Complete each step exactly as you would if you were installing the software on the server for the first time.
3. After the release media loads, the server reboots. You are asked if you would like to insert a complete system backup.
You are now ready to rename the server. Continue with "Renaming the Server."
Provide the server with a new name, and other first server information. Refer to the Server Installation Guide for more information.
1. After you reinstall system software, you are asked if you would like to reload a complete system backup. Enter N. The Add/Change Card screen appears.
2. Enter and save the configuration information for the LAN cards in your server. You are prompted to configure the time settings for the server.
3. Enter the appropriate time information. You are prompted to name the server.
4. Enter a unique name for the server. The following message appears:
Continue installing this server by selecting one of the following options:
1) This is the first server on this network.
2) This server is being integrated into an existing network of servers.
Select an option (1/2):5. Select This is the first server on this network.
6. Enter the organization name. Do not use international characters. You are prompted to enter the first group name.
Note: You must use first group and administrator names that were not previously on the server. When you later restore groups from tape, duplicate names can cause conflicts. You can delete the new first group and administrator names at the end of the process.
7. Enter the group name. Do not use international characters. You are prompted to enter the name of the system administrator.
8. Enter the name of the system administrator. Do not use international characters. You are prompted to confirm that the names you entered are correct.
9. Do one of the following:
- Enter N to reject the names. You are prompted to enter a new server name.
- Enter Y to accept the names. Remember that these names are later overwritten by backed up information.
The system displays some information about the items it is creating using the names you supplied. The server initializes and after a few minutes the Service Monitor appears. All services should have the status "Running" or "Initializing."
If the Service Monitor does not appear after one hour, refer to "Initialization Problems" in Chapter 8 of the Server Installation Guide.
10. Reattach the server's LAN cable.
You are now ready to begin restoring server information.
When restoring information after you rename the server, you must restore StreetTalk groups and services individually. You cannot rebuild the complete system, since doing so would result in the previous server name replacing the new server name.
To Restore Server Information After Renaming the Server
1. Re-install each third-party service that was running on the server (SMTP, VINES Assistant, FAX Gateways, and so on). Procedures for installing third-party services are included with the third-party software package.
2. Reapply any patches that are required on the server. Refer to Chapter 8 for information on applying patches.
3. From the Operator Menu, select Shut Down Server Software and then Shutdown services and return console to Operator Menu.
4. Enter the remainder of the server configuration information you recorded earlier, including the file cache and communication buffer allocations, and scheduled backup times. Depending on the configuration information you are re-entering, use the OPERATE command from a workstation, or use the Operator Menu at the server console.
You are now ready to move StreetTalk groups from backup media to the server.
Note: In the following section, newservername refers to the new name of your server.
Move all StreetTalk groups from backup media to the server.
To Move StreetTalk Groups from Tape
1. Move the StreetTalk groups back onto the server from the backups you made earlier. Refer to "Moving a StreetTalk Group" in Chapter 3 for information on moving StreetTalk groups.
2. Reboot the server. The server initializes.
3. After the server is fully initialized, log in as the first user.
4. Add the appropriate names to the list Adminlist@newservername@Servers. You are now ready to create and restore services.
Create and configure the server's services and restore the service data to the server.
To Create and Restore Services
1. Create the services that belong on the server.
2. Enter the configuration information for each service that you recorded in "Preparing to Rename a Server" earlier in this chapter.
Do not start services yet. The mail service starts up automatically; therefore, stop the mail service, if one exists.
3. Rebuild each service on the server from a complete system backup. Rebuild each service individually; do not rebuild the complete system.
Note: If the name of a service is dependent on location (for example, servicename@servername@servers), you need to rebuild the service to a service of another name.
4. Rebuild the mail service into a service of another name. The new mail service has the name MS@newservername@Servers. You cannot build the old mail service because it no longer exists. Be sure to rebuild the service from a complete system backup. Refer to "Rebuilding a Service" in Chapter 7 for information on rebuilding services.
You are now ready to administer the server.
Verify that the server is operating properly. Edit user profiles and verify administrative access to the server.
1. Start all services.
2. Check the Service Monitor to verify that all services are running.
3. Edit the user profile of any user who used the old mail service. You need to replace the name of the old mail service with the name of the new mail service. You may need to make similar changes for other services.
4. Verify that the appropriate names and access rights exist on the AdminList@newservername@Servers. Check administrative access by having users belonging to the AdminList log in.
5. Delete any temporary first group and first administrator names you created while entering first server information.