The process is very similar on Windows, Mac and Linux GUI systems. Firstly, one installs and runs the HFS Hub app. Secondly, in most cases, one needs to upgrade Spectrum Protect. Then, thirdly, Spectrum Protect is reconfigured so that one can then back up to the new HFS service.
1. Install the HFS Hub
Download the HFS Hub installer/package from the appropriate link below.
HFS Hub for Windows
HFS Hub for Debian based Linux (Ubuntu, Debian etc.)
HFS Hub for RPM based Linux (Fedora, OpenSUSE, Centos 8 etc.)
HFS Hub for older RPM based Linux (Centos 7, and possibly others with an older version of rpm)
HFS Hub for Mac (Intel)
HFS Hub for Mac (Apple Silicon)
You can then run the HFS Hub app. The first screen will display similar to that below.
Note that the HFS Hub app recognises that the IBM Spectrum Protect client software is already installed and configured. If the Upgrade button is displayed, then you need first to upgrade the IBM Spectrum Protect software before the migration process can proceed. In this case follow the upgrade process below.
2. Upgrade the Spectrum Protect client
Note: on Linux the Spectrum Protect client will be updated from the HFS repository just like your other software updates, so you typically will have updated the client with your usual updates. You can still use the HFS Hub to upgrade but it is just telling your system to update from the repository.
Click the Upgrade button or (or select the Upgrade item from the Spectrum Protect menu). Follow the prompts to download and install the new Spectrum Protect client. The process may take a little time, during which you will be prompted to allow the hfshub-agent process to make changes that require elevated privileges on your machine. This process will on Windows also open a temporary window which tracks the progress of the various elements being installed. You should see a window message confirming the upgrade was successful. If not, please use the 'Save Logs' item from the Logs menu to collect diagnostics to include with any support call.
3. Reconfigure for the new HFS service
Now you can reconfigure this machine to use the new HFS service. Choose the Spectrum Protect menu and select the item 'Change node or server'.
At the next screen prompt check the details and confirm with the OK button:
At this point you will be asked to authenticate using your SSO before the screen below displays.
From the drop-down list choose the nodename that has been confirmed as the target account name on the new service. If you have more than one node, make sure you select the correct one. Ensure that the option 'Modify existing configuration' is selected and choose OK. A background process will run and prompt you to confirm/authorise changes requiring elevated privileges on your machine. All being well, the process will complete successfully.
If any error has occurred during the above process, select the Logs menu from the Hub and choose the 'Save Logs' item. Please then include the zip file with any support query.
A successful move will mean your Spectrum Protect settings will have been modified to allow you to connect to the new HFS server, at the same time retaining any local setting changes that had previously been made. The old configuration settings will have been saved in a file with a timestamp suffix for you to confirm this. Now is the time to start up Spectrum Protect and confirm connection to new server (choose Connection Information from the File menu in the GUI or note the information when connecting using the command line).
Scheduled backup services will have been set up and passwords cached. The scheduler now works as follows. On Windows, the 'TSM Client Scheduler' is set up to be controlled by the 'TSM Client Acceptor'; essentially a wrapper script that allows the scheduler to stop and start at the allotted times. If you wish to check in Services, you should normally only see the 'TSM Client Acceptor' running and it is this service that should be stopped and started if that is ever required. On Linux you should see a dsmcad process in the process tree and this performs an identical role as a wrapper script for running the dsmsched process.