Updates for IBM Tivoli Storage Manager V7.1 for Space Management (HSM) for UNIX and Linux User's Guide

Content

Tivoli® Storage Manager for Space Management for UNIX and Linux User's Guide V7.1 Documentation Updates

Updates and corrections for version 7.1.0 and version 7.1 PTFs

Corrections for Version 7.1.0 (applies to all modifications of version 7.1)

Installation and Planning

Per APAR IT13292:

Topic: "General installation prerequisites and considerations"

Add the following limitation:

The space management client is not compatible with DMAPI applications that use any of the following DMAPI events on the space managed file system:
• DM_EVENT_READ
• DM_EVENT_WRITE
• DM_EVENT_TRUNCATE
• DM_EVENT_PREUNMOUNT
• DM_EVENT_NOSPACE
• DM_EVENT_DESTROY
Any DMAPI application on the space managed file system must respond to the DM_EVENT_MOUNT event with DM_RESP_DONTCARE.

Managing Space: Adding and configuring space management

Per APAR IT12583, the following topics are added for changing the mount point of a space-managed file system. These procedures are valid for version 7.1.4 and earlier versions.

Changing the mount point of a space-managed file system

If you change the mount point of a space-managed file system, you must rename the file space on the Tivoli® Storage Manager server.



If you rename the file space before you mount the file system at the new mount point, you must rename the old file space to the new file space name.

If you changed the mount point and migrated some files before you rename the file space, you must merge the old file space and the new file space. If the new mount point is the same as an existing file space, you must also merge the old file space with the existing file space, even if you did not yet migrate any files at the new mount point.




Mounting a previously space-managed file system at a mount point for which a file space does not exist

If you mount a previouly space-managed file system at a new mount point, you must rename the file space on the Tivoli® Storage Manager server. If you rename the file space before you migrate any files at the new mount point, and if the new mount point does not match an existing file space, you do not have to merge file spaces.

Procedure


1. For GPFS file systems, disable HSM failover and stop HSM daemons on all cluster nodes by using the dsmmigfs stop command.
2. For JFS file systems, stop all HSM daemons by using the kill -15 <PID> command for all of the HSM daemon PIDs. For GPFS™ file systems, unmount the file system on all GPFS nodes.
3. On the Tivoli Storage Manager server, rename the file space to the new name by using the RENAME FILESPACE administrative command. The new file space name must match the mount point.
4. Remove the following space management client files:
/etc/adsm/SpaceMan/config/dmiFSGlobalState*
/hsm_new/.SpaceMan/dmiFSState
For GPFS file systems, remove the files on all cluster nodes.
5. Start the HSM daemons again. For GPFS file systems, use the dsmmigfs start command.
6. For GPFS file systems, rename the GPFS mount point by using the mmchfs command. If the new mount point is /hsmnew, enter the following command:
mmchfs -T /hsm_new
For more information about the GPFS mmchfs command, go to the IBM® Spectrum Scale product documentation.
7. Mount the file system at the new mount point. For GPFS file systems, mount the file system on the space-managed file-system owner node first. Then mount the file system on other GPFS nodes.



Mounting a previously space-managed file system at a new mount point for which a file space already exists

If a file space exists for the new mount point of a space-managed file system, you must merge the old file space and the new file space.

Before you begin


Merging file spaces requires a secondary Tivoli® Storage Manager server.
About this task
When you change the mount point of a space-managed file system, you must rename the file space on the Tivoli Storage Manager server. If you changed the mount point and migrated some files before you rename the file space, you must merge the old file space and the new file space. If the new mount point matches an existing file space, you must also merge the old file space with the existing file space, even if you did not yet migrate any files at the new mount point.
Procedure
1. For GPFS file systems, disable HSM failover and stop HSM daemons on all cluster nodes by using the dsmmigfs stop command.
2. For JFS file systems, stop all HSM daemons by using the kill -15 <PID> command for all of the HSM daemon PIDs. For GPFS™ file systems, unmount the file system on all GPFS nodes.
3. Merge the old file space with the new file space on the Tivoli Storage Manager server.
a. Export the HSM data in the old file space to a secondary Tivoli Storage Manager server by using the EXPORT NODE administrative command. Specify FILEData=SPacemanaged.
b. On the secondary Tivoli Storage Manager server, rename the file space to the new name by using the RENAME FILESPACE administrative command. The new file space name must match the mount point and the existing file space name on the Tivoli Storage Manager primary server.
c. Import the HSM data from the Tivoli Storage Manager secondary server to the file space on the primary server by using the IMPORT NODE administrative command. Specify FILEData=SPacemanaged and MERGEfilespaces=yes.
4. Remove the following space management client files:
/etc/adsm/SpaceMan/config/dmiFSGlobalState*
/hsm_new/.SpaceMan/dmiFSState
For GPFS file systems, remove the files on all cluster nodes.
5. Start the HSM daemons again. For GPFS file systems, use the dsmmigfs start command.
6. For GPFS file systems, you must rename the GPFS mount point. If the new mount point is /hsmnew, enter the following command:
mmchfs -T /hsm_new
For more information about the GPFS mmchfs command, go to the IBM® Spectrum Scale product documentation.
7. Mount the file system at the new mount point. For GPFS file systems, mount the file system on the space-managed file-system owner node first. Then mount the file system on other GPFS nodes.

Options

Per APAR IC94316:
Topic: "Restoremigstate"

Add the following information:

If you restore a file from the Tivoli Storage Manager target server, and the file system is managed by Tivoli Storage Manager for Space Management, you must not restore the file as a stub file. You must restore the complete file. Use the restoremigstate=no option to restore the complete file. If you restore the file as a stub from the target server, the following consequences can occur:
- You cannot recall the file from the Tivoli Storage Manager source server by using the Tivoli Storage Manager for Space Management client.
- A Tivoli Storage Manager for Space Management reconciliation process that runs against the Tivoli Storage Manager source server expires the file. If the file is expired by a reconciliation process, you can restore the complete file with the backup-archive client and the restoremigstate=no option.