Changing the location of the file server
BMC Server Automation supports the use of only one file server at a time. This file server includes one host and one root directory location. In certain cases, you might need to change the location of the file server. For example, you might decide to move the file server from a single application server (with a typical //myfileserver/opt/bmc/bladelogic/storage path) to a centralized file server (with a path such as //blfs/opt/bmc/bladelogic/storage).
After copying the file server contents to their new location, you must ensure that all references to the file server point to the new location.
Typically, the only changes needed are two blasadmin commands and a SQL script to update extended object locations.
Typically, there will only be a single file server reference. Some BMC Server Automation environments that have been upgraded from versions before 8.1 may have multiple file server references present. Scripts are provided to check the file server references, and consolidate all such references, so that they all point to the new location of the file server. Before you run the scripts, you must ensure that the contents of the old file server are replicated to the same relative path under the new file server.
Ensure that you stop the Application Server prior to making any file server changes.
Overview of the scripts
The following table lists the available database scripts.
Tells you how many file servers exist in the BMC Server Automation system, which one is the default file server, and how many database references point to each file server. The system can use multiple file servers as long as it can read from the non-default file servers. All new files are written to the default file server.
Lets you change which file server is now considered the default file server. The file server you designate as the new default file server must be one of the file servers that appeared as output from the file_server_check script.
This script is used to consolidate multiple file server references to one and used with the file_server_change_<databaseType> (.sql or .bat for SQL server)
file_server_change_<databaseType> (.sql or .bat for SQL server)
This is typically only needed during the change procedure if multiple file servers were present and used with the file_server_change_<databaseType>
|update_extended_object_script_location.sql||Updates the extended object definitions which are stored on the file server.|
|update_depot_object_location_remote_path.sql||Updates the location of objects stored on remote paths (for example, NSH_COPY_AT_STAGING and AGENT_MOUNT url types). These files are not stored under the file server root (and are not affected by the blasadmin setting and scripts above) but might be on the same system as the file server.|
To change the location of the file server
- Run the file server check script to ensure there is only a single file server. See Checking file server references.
- Based on the results of the script, do one of the following:
- If the script determined that there are multiple file servers, complete the steps to get to a single file server. See Consolidating multiple file servers
- If the script confirms that there is a single file server, continue to the next step to change file server.
- Change location of the file server and move any applicable files to the new file server. See Changing the file server from one location to another.
- Execute the update_extended_object_script_location script to update the extended object definitions that reference the file server. See Updating extended object definitions with new file server location.
- If the file server being decommissioned was used to store remote path objects like patch-catalog patches, use the update_depot_object_location_remote_path.sql to change their location. See Updating remote path depot object locations.