Changing the file server from one location to another

This topic describes how to copy the file server contents to a new location and change location of the file server in the TrueSight Server Automation configuration. This topic contains the following sections:

To change the location of the file server

  1. If you have upgraded from an earlier version and have any doubt about how many file servers you have, run the file_server_check script to make sure you are using only one file server. (For information about how to run this script, see Checking-file-server-references.)
    • If file_server_check returns just one file server, note the location and continue with this procedure.
    • If file_server_check returns more than one file server, go to Consolidating-multiple-file-servers.
  2. Prepare the new file server, as described in File-server-requirements.
  3. Copy all the files from the old file server to the new file server. (See To copy files from one location to another.)

  4. Update the database with new file server details by running the following blasadmin commands.

    Note

    Before running these blasadmin commands, ensure that the database connection information stored in blasadmin is correct and up-to-date. If database connection details have changed since they were defined in blasadmin, update them as described in Configuring-a-database-server.

    If you are using multiple Application Servers, you need to run these blasadmin commands on only one Application Server. The reason for this is that the file server name and path are stored in the database, and all Application Servers use the same database.

    set fileserver name <hostname>
     where hostname is the name of the new file server to which you just moved the files.
    set fileserver location <directory>
     where directory is the directory on the new file server where data is stored. Use a Network Shell path to a directory, such as /c/FileServer, as opposed to a Windows path, such as C:\FileServer.

  5. After confirming that the new file server is being used, decommission the old file server system.
    This can be done by watching the rscd log on the old file server for some amount of time and ensuring there are no incoming connections.

To copy files from one location to another

Before making the blasadmin changes noted above, the contents of the file server need to be copied to the new system.  During an outage of the TrueSight Server Automation services, copy the files from the old path (for example, //blfileserver1.example.com/opt/bmc/bladelogic/storage) to the new path (for example, //blfilserver2.domain.com/storage). There are multiple ways to accomplish this using various tools. The entire contents should be present on the new system before continuing with the blasadmin changes.

Note

For large file servers where the copy time will take a significant amount of time, a utility like dsync can be used to perform a series of synchronizations between the old and new up until the outage. An example series of steps looks like this:

  1. Run an initial dsync command to copy the contents over. This might take hours
  2. Run successive dsync commands up until the outage window to keep the locations synchronized.  These copies should take minutes, as only a small volume of data will need to be changed.
  3. After the TrueSight Server Automation services are stopped, run a final dsync.

Where to go from here

Updating-extended-object-definitions-with-new-file-server-location

Updating remote path depot object locations

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*