Migration to the new HFS on-site disk-based backup service

Introduction

Migration to the new HFS onsite disk-based backup service will require a possible upgrade of the IBM client software, a reconfiguration of that software and either a fresh backup of existing data stores to the new service or a transfer of data from the old service to the new service. The first two of these are usually managed by the HFS Hub app although for command-line only systems which cannot use the HFS Hub a slightly different procedure outlined below applies. 

Requirements

The new service uses newer features of Spectrum Protect than the old and also has tighter security requirements. For this reason there is a minimum client version on the new service. The new service is only open to systems that can run a recent version 8 client. In practice that incudes the vast majority of existing systems but excludes

  • 32-bit Windows
  • 32-bit Linux
  • Windows 7, 8, 2008, 2008 R2 (and earlier)
  • OS X 10.10 (Yosemite) and earlier
  • Netware
  • Irix
  • Solaris SPARC

It may also exclude other particularly old Linux distributions but it definitely includes Ubuntu 14.04, Debian 8, and RedHat 6 and later.

Systems must be able to contact the HFS Spectrum Protect servers on TCP port 1500. If you are configuring firewall rules the simplest thing to do is allow access to the whole HFS subnet at 163.1.219.0/24. For configuration purposes systems should also be able to contact portal.hfs.ox.ac.uk on TCP port 443.

Systems that do not meet the client requirements for the new service will be retained on the old service for the time being. However they will be consolidated onto a single server so there will be a migration process for them too.

The migration process

While the service will continue to use IBM Spectrum Protect migrating from the current tape based backups to the new system is not a simple matter and has to be done within our licenced capacity which restricts how much data can be on both systems at the same time. To achieve this there will be two methods of migration:

  1. Resend of data from the client to the new service. The client will be reconfigured to point to the new service and do a new full backup. Access to the old backups would still be possible if required. After an agreed interval after completing the new backup the data on the old service will be deleted. It will not be possible to keep the old data for anywhere near 90 days though. The initial phase of the migration will exclusively use this method with volunteers who are happy to have their old data deleted fairly quickly.
  2. Copy of data from the old servers to the new. This is a time consuming process as it requires data to first be moved off tape onto temporary disk before being replicated to the new service. However it does avoid having to resend the data and also copies previous versions. This method requires a reasonable amount of free licence capacity so won't start until enough capacity has been freed up by moving clients by resending data (the new service uses licenced capacity more efficiently die to deduplication). Because of resource restrictions it will however have to proceed on a server by server basis and you will be told when you are being moved. The second phase of the migration will predominantly use this method.

Please note that

  • Through the course of the migration process, the service will be limited to existing data stores already secured by the legacy tape-based backup service.
  • Backup is licensed on capacity i.e. the amount of primary storage consumed, so there will continue to be both a fair use presumption as well as upper limits on total backup storage; these are yet to be decided, and experience will shape this, but will exceed the current limits.

Current state of migration

As of the beginning of April a sufficient number of nodes have moved off the old service by resending data to the new system, and by the trial of data migration used for the virtual environment systems, to give us enough headroom to start phase 2 of the migration. We do need to move to phase 2 in order to move the remaining systems and data in a reasonable time span.

We are now in phase 2 of the migration in which your data is transferred to the new system. You will be given advance notice that your data is about to be transferred. When the transfer is complete you will no longer be able to access the copy on the old service. You will simply need to upgrade your client if required and reconfigure with the information we provide to connect to the new service. You will then be able to continue backing up as before and will have access to your historic backups on the new service.

Because of resource restrictions this will be done server by server so if you have multiple nodes they will not all be moved at the same time. The whole process is expected to take several months.

The provisional schedule is

Server Migration period
OX_HFS_DD1, OX_HFS_DD2, OX_HFS_DD3 March (completed)
OX_HFS_B12 April (completed)
OX_HFS_B4 18th - 27th May (completed)
OX_HFS_B14 30th May - 10th June (completed)
OX_HFS_B10 13th - 24th June (completed)
OX_HFS_B8 From 27th June (completed)
OX_HFS_B2 July
OX_HFS_B6, July/August
OX_HFS_B1, OX_HFS_B3, OX_HFS_B5, OX_HFS_B7 (Desktop service) Later

 

This timetable will be updated as we progress.

Alongside this it will still be possible to migrate by starting new backups to the new service if you wish but only if you are prepared to rapidly dispose of the old copy.

Procedure

As we work our way through the current servers we will inform contacts for the nodes on those servers that we are starting the migration process. In that email we will also tell you

  • the name of the server you will be moved to
  • the name your node will have on the new server (if it has changed)
  • whether your Spectrum Protect client needs upgrading
  • if your system cannot be moved to the new service we will be telling you that you will be moved to a new server on the current service
  • the estimated time of completion

We recommend that if your client needs upgrading you do it sooner rather than wait till you have to. In fact updating to the latest version is something you can do now. Follow the instructions below but only go as far as upgrading the client.

When your data has been migrated the procedure will be

  • the old node gets locked preventing further access and scheduled backups are removed
  • a final data replication takes place to ensure nothing gets missed
  • the node is configured correctly on the destination server, including setting up a schedule (usually at the same time you had before)
  • the node is assigned to you in the HFS Portal 
  • you get mailed to tell you migration is complete and you must now reconfigure your client

This will happen in the morning so you have the rest of the day to complete the reconfiguration.

 

Please note the following:

  • Naming: We would expect servers with a fixed public IP address to be registered with their DNS name. In many cases this will be identical with the current nodename, but in some cases may therefore generate a new account name that is subtly different from the existing one. We will confirm the account names (cf. nodenames) registered.
  • Passwords: The client installation and configuration process performed by the HFS Hub app does not need to know the password generated at registration time.
  • The upgrade process: Prior to the upgrade process do not be tempted to move your existing options file or indeed uninstall the existing IBM client software. The Hub will manage any required upgrade and will make the necessary edits to the options file in place, while also retaining a saved copy to allow you to check that any local edits to your previous configuration have been carried over correctly. 

Reconfiguring your system

Please chose from the following options to reconfigure your system:

Reconfiguring your system (GUI systems)

The process is functionally very similar on both Windows, Mac and Linux GUI systems and so is described generically below. It makes use of the HFS Hub. A lot of the configuration logic that was previously in the installer is now in the HFS Hub (this avoids having to have different implementations for different platforms) so you first need to install the HFS Hub

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)

and install. You can then run the HFS Hub app. The first screen will display similar to that below

hub first screen sp migration

Note that the HFS Hub app recognizes that the IBM Spectrum Protect client is already installed and configured. If the Upgrade button displays, then this signals that the current installed version of the IBM Spectrum Protect client is not at the latest level and the migration process cannot proceed until it is. In this case follow the upgrade process below.

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 collects diagnostics to include with any support call.

Reconfigure for the new service

Now you can reconfigure this machine to use the new service. Choose the Spectrum Protect menu and select the item 'Change node or server'.

HFS Hub move server 01

 At the next screen prompt check the details and confirm OK

HFS hub move server 02

At this point you will be asked to authenticate using your SSO before the screen below displays.

HFS hub move server 03

From the drop down list choose the nodename that is confirmed as the target account name on the new service (i.e. most likely the DNS name). There will probably be two similar or identical nodenames; ensure that you select the one listed as being on an HFS server beginning in OX_HFS_P, and not OX_HFS_B. 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 configuration file will have been modified to allow you to connect to the new server at the same time retaining any local configuration edits that had previously been made. The old configuration file will have been saved with a timestamp suffix for you to confirm this. Now is the time to start the client 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 setup and passwords cached. On Windows the 'TSM Client Scheduler' is setup to be controlled by the 'TSM Client Acceptor'; essentially a wrapper script that allows the scheduler to stop and start at the allotted times. Examining the service window, you should normally only see the 'TSM Client Acceptor' running and it is this service that should be stopped and started when 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. 

Reconfiguring your system (Linux non-GUI systems)

Before you start, you will need the name of the target node name on the new service (likely the DNS name of system), the Spectrum Protect server to which it will connect (one of OX_HFS_P11, OX_HFS_P22, OX_HFS_P31 or OX_HFS_P42). You should have received both of these from the HFS Team prior to this process. You will also need the node password, which you can get from the HFS Portal , click the tab for the node concerned to display the node details page. In the left hand menu, choose the 'Change Node Password' option and note the password generated. Note that you should consider the node password to be a temporary token used to set up your client. It is not needed in daily operation once your system is configured. It fact will later be changed by Spectrum Protect. You simple generate a new one if you need to reinstall the client for instance.

On the system, as the root user, use your package manager to install the package ox-hfs-spectrum-protect. Change directory to the Spectrum Protect install directory: /opt/tivoli/tsm/client/ba/bin. Run the HFSconfigure  script and answer the prompts with the information noted above.

As with the Linux GUI systems above, a successful reconfiguration will mean your configuration files dsm.sys and dsm.opt in the Spectrum Protect installation directory will have been modified to allow you to connect to the new server at the same time retaining any local configuration edits that had previously been made. The old configuration file will have been saved with a timestamp suffix for you to confirm this. Now is the time to start the client (dsmc) and confirm connection to new server (the Node Name: and the 'Session established: lines in the header information above the Protect> prompt).

Scheduled backup services will have been setup and passwords cached: you should see a dsmcad process in the process tree which performs the role of a wrapper script for running the dsmc command that actually performs the scheduled backup.

In cases where the installation and reconfiguration does not complete successfully, please gather the configuration files (dsm.sys and dsm.opt) together with the hfs-sp-install.log file to send with any support call. 

Reconfiguring your system (legacy systems)

Legacy systems (i.e. those that cannot be supported on the new service) will be consolidated onto server OX_HFS_PD1.

You will be informed of the nodename to be used on the new server. As it must fit the current naming scheme it may be different from the current name. This is particularly the case with desktops (if you don't like any revised name you are given it can be changed provided it meets the naming scheme rules). You will also need the node password, which you can get from the HFS Portal , click the tab for the node concerned to display the node details page. In the left hand menu, choose the 'Change Node Password' option and note the password generated.

On Windows legacy systems use the IBM Spectrum Protect GUI to do the reconfiguration:

  1. Start up the IBM Spectrum Protect GUI program
  2. If the "ANS1361E Session Rejected: The specified node name is currently locked" error message pops up, just click 'OK'.
  3. If the IBM Spectrum Protect login window will ask for a node name and node password, just click 'Cancel' and click 'OK' when the 'ANS5053W The operation was stopped by the user' message' warning message comes up.
  4. Click 'Yes' when you see the 'Do you wish to continue for purposes of local backupset restore?' message.
  5. Go to Utilities > Setup Wizard
  6. Select the 'Help me configure the Client Option File' option
  7. Select 'Update my options file'
  8. Update your nodename if needed. You may not need to if you kept your original nodename.
  9. Select 'TCP/IP' on the 'IBM Spectrum Protect Client/Server Communications' window
  10. Change the Server Address to: 'oxhfsd.hfs.ox.ac.uk' and the Port Number to: '1500'
  11. Accept the recommended include/exclude list and the file exclusion selections
  12. Accept the recommended domains for backup
  13. Apply the changes
  14. Enter the new node password when asked
  15. Restart your 'TSM Client Scheduler' service

On Linux/Unix command line only systems you will need to edit your dsm.sys and dsm.opt files which are located in /opt/tivoli/tsm/client/ba/bin on Linux or possibly /usr/tivoli/tsm/client/ba/bin on Solaris, Irix, and HP-UX.

Edit dsm.opt to modify the ServerName line

ServerName OX_HFS_PD1

Edit dsm.sys to modify the ServerName,TcpServerAddress, TcpPort and if necessary the NodeName lines

ServerName OX_HFS_PD1
TcpServerAddress oxhfsd.hfs.ox.ac.uk
TcpPort 1500
NodeName put your node name here

Now run dsmc and enter your node password when prompted. Once you have successfully reconnected restart your scheduler.

Reconfiguring your system (GUI systems) manually using the IBM Spectrum Protect GUI

You can manually reconfigure your GUI system using the IBM Spectrum Protect GUI if you are unable to use the HFS Hub app.

  1. Start up the IBM Spectrum Protect GUI program
  2. If the "ANS1361E Session Rejected: The specified node name is currently locked" error message pops up, just click 'OK'.
  3. If the IBM Spectrum Protect login window will ask for a node name and node password, just click 'Cancel' and click 'OK' when the 'ANS5053W The operation was stopped by the user' message' warning message comes up.
  4. Click 'Yes' when you see the 'Do you wish to continue for purposes of local backupset restore?' message.
  5. Go to Utilities > Setup Wizard
  6. Select both the 'Help me configure the Client Option File' and the 'Help me to configure the Client Scheduler' options
  7. Select 'Update my options file'
  8. Update your nodename if needed. You may not need to if you kept your original nodename.
  9. Select 'TCP/IP' on the 'IBM Spectrum Protect Client/Server Communications' window
  10. Change the Server Address to: 'oxhfs<1/2/3/4>.hfs.ox.ac.uk' and the Port Number to: '1500'
    1. oxhfs1.hfs.ox.ac.uk if the HFS server is OX_HFS_P11
    2. oxhfs2.hfs.ox.ac.uk if the HFS server is OX_HFS_P22
    3. oxhfs3.hfs.ox.ac.uk if the HFS server is OX_HFS_P31
    4. oxhfs4.hfs.ox.ac.uk if the HFS server is OX_HFS_P42
  11. Accept the recommended include/exclude list and the file exclusion selections
  12. Accept the recommended domains for backup
  13. Apply the changes
  14. Enter the new node password when asked
  15. Select 'Remove a previously installed scheduler'
  16. Accept the scheduler name (TSM Client Scheduler) and click 'Apply'
  17. Now we need to re-create the services
  18. Go to Utilities > Setup Wizard
  19. Select the 'Help me to configure the Client Scheduler' option
  20. Select 'Install a new or additional scheduler'
  21. Accept the scheduler name (TSM Client Scheduler) and tick the 'Use the client acceptor to manage the scheduler' option
  22. Accept the client acceptor name (TSM Client Acceptor)
  23. The option file location should point to your current dsm.opt file
  24. Accept the default client acceptor port number (1581)
  25. Enter the new node password when asked and click 'Next'
  26. On the 'Service login options' window, make sure that 'The System account' and the 'Automatically when Windows boots' options are selected
  27. The schedule and error log file location should point to your current log files
  28. Select 'Yes' when asked if you'd like the service to start now and click 'Apply'

Get support


Local IT support provides your first line of on-the-spot help

FIND MY LOCAL IT TEAM

 

Common requests and fault reports can be logged using self-service

   USE IT SELF SERVICE      

   LOG A SUPPORT CALL     

VIEW MY SUPPORT CALLS  

 

The Central IT Service Desk is available 24x7 on +44 1865 6 12345

If you do not have access to your Single Sign-On, you can use this form to contact the Service Desk