IC89847: EXAMPLES OF HOW TO SCHEDULE A BACKUP OF A GPFS FILE SYSTEM NEED CLARIFICATION

APAR status

• Closed as documentation error.

Error description

• The examples given to show how to schedule a backup of a GPFS
  file system need clarification in Tivoli Storage Manager
  manuals.
  Examples of how to schedule a backup of a GPFS file system
  The following example shows the steps necessary to back up a
  GPFS file system, using three nodes in the GPFS cluster to share
  the workload.
  This example assusmes node_1, node_2, and node_3 will be used
  for authentication.  The file spaces backed up will be stored
  under node_gpfs.
  Define four nodes on the Tivoliﾩ Storage Manager server, using
  the following commands:
  (1) REGISTER NODE node_1 mysecretpa5s
  (2) REGISTER NODE node_2 mysecretpa5s
  (3) REGISTER NODE node_3 mysecretpa5s
  (4) REGISTER NODE node_gpfs mysecretpa5s
  Define a proxynode relationship between the nodes, using the
  following command:
   GRANT PROXYNODE TARGET=node_gpfs AGENT=node_1, node_2, node_3
  Define a schedule for using the following commands:
  (1) DEFINE SCHEDULE STANDARD GPFS_SCHEDULE ACTION=incremental
  OBJECTS="/gpfs"
  (2) DEFINE ASSOCIATION STANDARD GPFS_SCHEDULE node_gpfs
  Choose one of the GPFS systems to run the schedule.  Specify the
  following options in the dsm.sys file on the system chosen to
  run the schedule :
  (1) nodename node_1
  (2) asnodename node_gpfs
  Start the scheduler on the system chosen to run the schedule:
  DSMC SCHED
  Tivoli Storage Manager Versions Affected: 5.5,6.1,6.2,6.3,6.4
  Initial Impact: medium
  Additional Keywords: gpfs cluster sched backup proxy tsm
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM Tivoli Storage Manager for UNIX and      *
  *                 Linux Backup-Archive Clients Installation    *
  *                 and User's Guide                             *
  ****************************************************************
  * PROBLEM DESCRIPTION: The documentation does not provide      *
  *                      clear and accurate steps for            *
  *                      scheduling a backup on a GPFS cluster.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  *
  

Problem conclusion

• Section:
  Backing up your data
   > Backing up data with client-node proxy support
     (UNIX and Linux)
     > Scheduling backups with client-node proxy support
       > Examples of how to schedule a backup of a GPFS file
         system
  
  The example of scheduling a GPFS backup is  updated as follows:
  
  Scheduling a backup of a GPFS file system
  Use the scheduler and proxy relationships to back up a GPFS
  file system.
  
  About this task
  Assume that three nodes in a GPFS cluster participate in the
  backup operation. Nodes node_1, node_2, and node_3 are used
  for authentication only. The objects are backed up to file
  spaces that belong to node node_gpfs.
  
  Procedure
  1. Define four nodes on the Tivoli Storage Manager server.
  REGISTER NODE node_1 mysecretpa5s
  REGISTER NODE node_2 mysecretpa5s
  REGISTER NODE node_3 mysecretpa5s
  REGISTER NODE node_4 mysecretpa5s
  2. Define a proxy relationship between the nodes.
  GRANT PROXYNODE TARGET=node_gpfs AGENT=node_1, node_2, node_3
  3. Define a schedule.
  DEFINE SCHEDULE STANDARD GPFS_SCHEDULE ACTION=incremental
  OBJECTS="/gpfs"
  DEFINE ASSOCIATION STANDARD GPFS_SCHEDULE node_gpfs
  4. Choose one of the GPFS systems to run the schedule.
  Specify the nodename and asnodename options in the dsm.sys
  options file on all systems in the GPFS cluster.
  The value for the asnodename option must be the same on all
  systems.
  
  Definitions in dsm.sys on node 1:
  nodename node_1
  asnodename node_gpfs
  
  Definitions in dsm.sys on node 2:
  nodename node_2
  asnodename node_gpfs
  
  Definitions in dsm.sys on node 3:
  nodename node_3
  asnodename node_gpfs
  
  5. Start the scheduler on the system that is chosen to
  run the schedule.
  DSMC SCHED
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels