Known Issues and Limitations: Version 8.1 IBM Spectrum Protect™ Snapshot - all Unix Components

Content

Tip: IBM Tivoli Storage FlashCopy® Manager is now IBM Spectrum Protect™ Snapshot. To learn more about the rebranding transition, see http://www.ibm.com/support/docview.wss?uid=swg21963634.


The following IBM Spectrum Protect™ Snapshot components share some known issues and limitations. Therefore, the known issues and limitations for all of the following components are grouped together in a single document. The components are:

• IBM Spectrum Protect Snapshot for DB2
• IBM Spectrum Protect Snapshot for Oracle
• IBM Spectrum Protect Snapshot for Oracle (in SAP® environments)
• IBM Spectrum Protect Snapshot for Custom Applications

• Applicable to All IBM Spectrum Protect Snapshot Unix Components
• Specific to the IBM Spectrum Protect Snapshot for DB2 Component
• Specific to the IBM Spectrum Protect Snapshot for Oracle (in SAP® environments) Component
• Specific to the IBM Spectrum Protect Snapshot for Oracle Component
• Specific to the IBM Spectrum Protect Snapshot for Custom Applications Component
• Specific to the AIX Platform
• Specific to the Linux Platform
• Specific to Spectrum Protect Snapshots v8.1.4 on the Linux Platform
• Specific to Virtualized Environments
• Specific to IBM XIV® Storage System hardware
• Specific to IBM System Storage SAN Volume Controller (SVC), IBM Storwize® family, IBM Flex System™ v7000, and IBM FlashSystem™ V840
• Specific to IBM System Storage DS8000 hardware
• Specific to IBM Spectrum Scale (formerly IBM General Parallel File System (GPFS™))

• Resolved with IBM Spectrum Protect Snapshot v8.1.4
• Resolved Issues and Limitations Applicable to All IBM Spectrum Protect Snapshot Unix Components
• Resolved Issues and Limitations Specific to the IBM Spectrum Protect Snapshot for DB2 Component
• Resolved Issues and Limitations Specific to the IBM Spectrum Protect Snapshot for Oracle Component

• Updates, clarifications, and corrections to the currently published version of the IBM Spectrum Protect Snapshot v8.1 publications are located in the Documentation Updates tech note at: http://www.ibm.com/support/docview.wss?uid=swg27048772.
  

• Insufficient space on root file system
  
  If the root file system is running out of space during IBM Spectrum Protect Snapshot installation and/or setup, the process might hang. Always ensure there are sufficient space reserves in the root file system.

• Installation in console mode requires X Window server
  
  In combination with some ssh clients, the console-based installation incorrectly checks for the presence of a X Window server. Therefore, if a X Window server is not available during IBM Spectrum Protect Snapshot installation you may see this error:
  
  Launching installer...
  
  X connection to localhost:10.0 broken (explicit kill or server shutdown).
  
  User response: Unset the DISPLAY environment variable (unset DISPLAY) and re-run the installer. (77219)

• When uninstalling in console mode , the uninstaller may report "Some items could not be removed" although the uninstallation completed successfully. (77924)

• "Previous" button of uninstallation agent
  
  Using the "Previous" and "Next" buttons in the uninstallation wizard after the package has already been uninstalled may lead to an exception. (78014)

• Concurrent fcmcli operations on the same backup server
  
  An operation "fcmcli -f tape_backup" (e.g. off-loaded backup to TSM) running on the IBM Spectrum Protect Snapshot Backup Server may terminate with the message:
  
  FMM6276E Another mount agent service is currently running
  
  when another fcmcli operation is running a second operation on the same IBM Spectrum Protect Snapshot Backup Server.
  
  Work-around: Use the profile parameter NUMBER_BACKUPS_IN_PARALLEL in the OFFLOAD section of the profile to specify the number of DB2 partitions to be backed up in parallel per IBM Spectrum Protect Snapshot backup server. If two or more DB2 partitions are backed up by the same IBM Spectrum Protect Snapshot backup server you can prevent parallel operations by choosing this number appropriately.

• Logging in the case of off-load operations
  
  When a customer starts multiple IBM Spectrum Protect Snapshot off-load operations (mount, unmount or tape_backup) in parallel, then the IBM Spectrum Protect Snapshot detailed log output gets written to the log file of the command that was started last. Also, some early log messages of a subsequent mount or unmount operation may be written to the detailed log of a previous off-load operation.
  No detailed log output is lost, but the log output may not be found in the detailed log file where it would be expected.
  
  Work-around: If detailed log output is missing for a specific off-load operation check the detailed log files of all IBM Spectrum Protect Snapshot operations that were executed in parallel. (84855)
  Early messages of mount or unmount operations may be found in the detailed log of a preceding off-load operation.

• Backup and delete operations running concurrently
  
  If a FlashCopy backup operation is started while a delete operation with the force option is still running the backup operation may fail with message FMM4008E logged to the summary log file:
  
  DB 00:25:50 (712) FMM4008E File '/db2/S43/sqllib/acs/acsrepos/ori.1313619101000' cannot be opened. Reason: errno(2) No such file or directory
  DB 00:25:50 FMM9223E The operation will be aborted.
  
  Work-around: Make sure the delete operation completed by monitoring the log file for FlashCopy withdraw messages, then re-start the backup operation.
  Please note: A delete operation may take several minutes to complete.
  (71973)

• Concurrent mount commands
  
  Running multiple mount commands concurrently on the same machine for the same database instance is not supported. Attempts to do so may cause all requests to fail.

• Inquire command and background reconciliation interference
  
  If an fcmcli -f inquire command interferes with a background reconcile operation (performed by default every 12 hours), the fcmcli -f inquire process might fail and print errors about snapshots that are not valid anymore. For example:
  
  ***********************************************************************
  db2acsutil load /db2/R95/sqllib/acs/libacsdb2.a options @/db2/R95/tc_tool/tc/Temp/db2acs.cfg query status show details
  **********************************************************************
  
  ERROR: Error initializing query statement. (rc = 18)
  db2ACS_ReturnCode:
  returnCode: 18
  reasonCode: 0
  description: FMM8323E IBM Tivoli Storage FlashCopy(R) Manager : Problem occurred while
  processing db2ACSBeginQuery().
  Please check log file:
  acsprod1:/db2/R95/sqllib/acs/logs/summary.20100422.log,
  /db2/R95/sqllib/acs/logs/details/inquire.20100422135640,
  /db2/R95/sqllib/acs/logs/summary.20100422.log for more information.
  
  Error information: 'FMM4008E File '/db2/R95/tc_tool/tc/Temp/acsrepos/ori.1271936982492'
  cannot be opened. Reason: errno(2) No such file or directory
  
  summary.log:
  ====================================================
  New query operation started for database instance *, database *.
  ====================================================
  DB 13:56:40 (66e) FMM1510I New connection received.
  DB 13:56:40 (66e) FMM1513I *****> Database client connected: instance *, database *, partition NODE0000
  DB 13:56:40 (66e) FMM1515I Client is logging to acsprod1:
  MON 13:56:40 (507) FMM0104I Deleting the data container '
  string=8,NODE0000
  string=9,R95log0vg
  string=10,A0G8BI7A29' from the backup 'db2r95,R95,20100422134304' in the repository.
  IBM Tivoli Storage FlashCopy(R) Manager found that the volumes of this data container do not contain a valid snapshot in the storage system.
  
  Those errors can be ignored. They will not be displayed any more when the "inquire" command is run again.

• Setup scripts cannot be aborted when overriding an existing clone instance as a new clone instance.
  
  After selecting to configure a new clone instance (option n) and then specifying the host name of an existing clone instance processing cannot be stopped by entering "c".
  
  Work-around: Stop the setup script by pressing ctrl+c before entering the root password of the clone system. Once the root password is specified the setup script starts to override the existing clone instance.
  
  
• In a remotely mirrored environment, the attempt to restore a backup on the secondary site after a failover may fail with the following messages:
  FMM0557W Removing the file system on the mount point <your mount point> failed with rc: 255.
  FMM0199W One or more errors were found disabling the production system resources.
  
  This happens when the given file system is recorded in the /etc/filesystems file even though it is actually not mounted. This occurs when the respective volume groups were deactivated, but were not completely removed from the system.
  
  Work-around: Ensure that the affected file system is removed from /etc/filesystems by exporting the corresponding volume groups with the exportvg command, then retry the restore.
  
  
• Using csh may cause cloning operations to fail
  
  IBM Spectrum Protect Snapshot Cloning operations can fail if a customer uses 'csh' as login shell for the database user on the cloning target system. Calls to pre- or post-processing scripts during a IBM Spectrum Protect Snapshot Cloning operation will fail with a return code RC=1, and the scripts will not be executed.
  
  Work-around: Switch the database user's login shell on the cloning target system to another shell, for example to ksh or bash. (63869_1)

• Duplicate informational messages
  
  During IBM Spectrum Protect Snapshot operations, a customer may see some duplicate informational messages in the IBM Spectrum Protect Snapshot log files.
  Examples for messages that can occur multiple times:
  FMM6555I Selected snapshot backup with ID '<BACKUP_ID>'.
  FMM6503I Terminating 'fs_chown_clone' request.
  FMM1014I Operation postproc_clone completed successful.
  
  There is no work-around. The duplicate messages can be ignored. Fixed in 8.1.4

• The sequence of a database clone creation without a new database name first, followed by a clone creation with a new database name, fails. The file system mount points / disk group names of the first clone prohibit the mount operation of the second clone that is required before the mount points / disk group names can be changed.
  
  Work-arounds:
• Delete the clone using the production database name before creating a clone with a new database name on the same clone system.
• Use separated clone systems. One for database clones with new database names and one for a database clone using the production database name.

• At least one file system is mounted on the clone target system which is part of a IBM Spectrum Protect Snapshot cloning operation. This means that IBM Spectrum Protect Snapshot will try to mount this file system a second time on the clone system. If running on Linux, this new clone operation will finish successful with the result, that the file system is mounted twice (its strange but its allowed on Unix systems). From an operational perspective the clone works.
  But the delete of the clone using the delete_clone operation does fail. IBM Spectrum Protect Snapshot first unmounts the file system (which was mounted twice). After that IBM Spectrum Protect Snapshot checks if the file system is unmounted but it still detects that it is mounted and fails then with error message
  FMM1241E Unable to unmount the following file systems:
      /oracle/CWS/oradata/HWS
  The file system in question then needs to be unmounted manually or the delete_clone operation needs to be performed again.
  Afterwards a new create clone would work fine and also the delete_clone will work fine.

• The help output of the installer (<installername>.bin --help) includes an option
  
  -r <path_to_generate_response_file> that generates a response file.
  
  The response file generated from the option "-r" cannot be used for silent installation.
  
  Work-around: Use the installer property option ("-DRECORDFILE") to generate an appropriate response file for silent installation. This installer property is explained in the documentation. (73087)

• For any IBM Spectrum Protect Snapshot action, the values of the DB2 registry variables as returned by the db2set command must have been activated and must reflect the actual state within the database.
  

• IBM Spectrum Protect Snapshot can fail when protecting data stored on DB2 automatic storage in case a data path was specified multiple times when configuring the database.
  A circumvention is documented with APAR IC83834.
  
  
• IBM Spectrum Protect Snapshot supports only the default DB2 storage group in combination with DB2 high availability disaster recovery servers (HADR).
  
  
• If there are multiple databases managed by a single instance, only one of these databases can be protected by IBM Spectrum Protect Snapshot.
  
  
• When backing up a DB2 database in online mode log files that are created during backup processing may be reported as "extra files" unless profile parameter NEGATIVE_LIST is set to NO_CHECK.
  If so, customers may see messages like to following in the log:
  FMM8387W The following extra files are found in the directories to be backed up: '/db2/D1S/log_dir/NODE0000/LOGSTREAM0000/S0000021.LOG'
  In case the profile parameter NEGATIVE_LIST is set to ERROR, backup processing ends in such a situation.
  
  
• The command "fcmcli -f delete" only deletes partition 0 of DB2 databases with multiple partitions.
  
  This command, with or without the force command line option '-F', only deletes partition 0 of DB2 databases with multiple partitions. A subsequent request "fcmcli -f inquire[_detail]" does not show the deleted backup any longer. However, the DB2 ACS command db2acsutil query status still shows the backups of the remaining DB2 partitions as valid backups.
  
  General recommendation: To delete DB2 backups with a single partition or with multiple partitions always use the db2acsutil delete command instead of using "fcmcli -f delete".
  
  
• An offloaded tape backup of a multi-partition DB2 database with Database Partitioning Feature (DPF) may be reported as unsuccessful by IBM Spectrum Protect Snapshot v8.1.0.0 although all partition backups were successfully sent to an IBM Spectrum Protect server.
  
  The corresponding log file in the details path may contain a sequence of messages similar to this:
  FMM6542I 20:33:26 db2dr1 DR1 1 20161114202354 20161114203305
  FMM6542I 20:33:26 db2dr1 DR1 2 20161114202354 20161114203313
  FMM6542I 20:33:26 db2dr1 DR1 3 20161114202354 20161114203321
  FMM6542I 20:33:26 db2dr1 DR1 ## 20161114202354 -
  FMM6544I Snapshot backup suspend time: 20161114202621
  FMM6283E offloaded tape backup unsuccessful.
  
  The error message can be ignored in case the states of the backups of all partitions show TAPE_BACKUP_COMPLETE when requesting the status via db2acsutil. Fixed in 8.1.4
  
  
• Cloning of a DB2 DPF database may end with an error if filesystems were added to DB2 storage groups using DB2 partition expressions, like:
  db2 create stogroup sg on '/db2/DUT/extendedStorage/fs_ $N'
  db2 alter stogroup sg add '/db2/DUT/extendedStorage/fs_ $N'
  
  When cloning such a database, an error similar to this may be logged:
  DBT1006N  The "<FILE-DEVICE-NAME>" file or device could not be opened.
  
  In order to determine whether a partition expression was used, you may use the db2pd utility with the -storagegroups or -storagepaths options, for example:
  db2pd -db DUT -storagepaths
  
  If a partition expression was used it shows up in braces under the heading "Storage Group Paths" in the respective command output, for example:
  Address            SGID  PathID    PathState    PathName
  0x00007FAC1625D080 1     1024      InUse        db2/DUT/extendedStorage/fs_0 (/db2/DUT/extendedStorage/fs_ $N)
  
  Fix:
  Install the fix for APAR IT15267 on DB2 LUW v10.1, the fix for APAR IT15320 on DB2 LUW v10.5, or the fix for APAR IT15321 on DB2 LUW v11.1.
  
  Work-around:
  Do not use DB2 partition expressions when adding filesystems to storage groups in DB2.
  
  
• After installation and configuration of IBM Spectrum Protect Snapshot for DB2 with an off-load configuration using IBM Spectrum Protect for Enterprise Resource Planning the off-loaded backup fails with the following error message:
  db2_all "<<+0<\" echo [ Backup database partition ## ]; db2 BACKUP DATABASE SD1 LOAD /opt/tivoli/tsm/tdp_r3/db2/libtdpdb2.so OPEN 1 SESSIONS OPTIONS @/db2/SD1/tdp_r3/vendor.env exclude logs 2>&1 "
  [ Backup database partition 0 ]
  SQL2071N  An error occurred while accessing the shared library
  "/opt/tivoli/tsm/tdp_r3/db2/libtdpdb2.so". Reason code: "1".
  The shared vendor library /opt/tivoli/tsm/tdp_r3/db2/libtdpdb2.so does not exist with the given name and directory. Instead it is located in /opt/tivoli/tsm/tdp_r3/db264/libtdpdb264.so.
  Work-around: Change the IBM Spectrum Protect Snapshot profile parameter VENDOR_LIB from TSM4ERP to /opt/tivoli/tsm/tdp_r3/db264/libtdpdb264.so or create the following symbolic links:
  cd /opt/tivoli/tsm/tdp_r3
  ln -s db2 db264
  cd db2
  ln -s libtdpdb2.so libtdpdb264.so
   

• When configuring an IBM Spectrum Protect Snapshot instance the script setup_db2.sh allows to specify the value "GPFS" for parameter COPYSERVICES_HARDWARE_TYPE. However, the value "GPFS" is not supported for DB2 environments. Specifying this value in a DB2 environment results in an inoperable configuration.
  
  
• When performing a series of DB2 snapshot backups and offload backups to Spectrum Protect server a second offload may fail with such an error message:

FMM9199E The following command returned with an error:
/bin/sh -c "mkdir -p /db2/SV1/log_dir/NODE0000/LOGSTREAM0000/"
The return code from this command is 2

This only happens when
1. a first db2 backup is done including logs and offload it to TSM.
2. a second db2 backup is done now with excluding logs and offload it to TSM

The root cause is that the first offload creates the mount point /db2/SV1/log_dir for the filesystem that contains the db2 log directory. This mount point is created as root user and does not have write permissions for others.
During the second offload operation Spectrum Protect Snapshot tries to create the directory /db2/SV1/log_dir/NODE0000/LOGSTREAM0000/ as subdirectory in /db2/SV1/log_dir but this fails because Spectrum Protect Snapshot is running as db2<sid> user at that time.

Work-around: Manually change the owner and permissions of the mount point /db2/<SID>/log_dir as root user on the backup system. This needs to be done only once.

• When configuring IBM Spectrum Protect Snapshot in a SAP Oracle environment the action may fail with the following error message:
  FMM8448E Another device class already exists under the given name 'STANDARD'. Please specify another name.
  The problem only occurs if IBM Spectrum Protect Snapshot is configured for cloning only and uses
  the cloning device class with the name STANDARD. When IBM Spectrum Protect Snapshot is reconfigured for backup with off-load and cloning then the configuration wizard tries to add a new device class for backup with the name STANDARD. This results in the above error message and the IBM Spectrum Protect Snapshot profile wizard fails to create the new configuration.
  
  Work-around: Manually duplicate the existing cloning device class in the profile and remove the CLONE_DATABASE YES parameter. If the storage system is SVC and uses the TARGET_NAMING parameter in the IBM Spectrum Protect Snapshot profile, then remove the USE_FOR_CLONING <dbname> clause on the TARGET_NAMING parameter as well. Afterwards the wizard starts without any errors.
  
  
• When configuring an IBM Spectrum Snapshot instance the script setup_ora.sh allows to specify the value "GPFS" for parameter COPYSERVICES_HARDWARE_TYPE. However, the value "GPFS" is not supported for Oracle (in SAP environments) environments, and specifying this value results in an inoperable configuration.
  
  
• Multitenant (pluggable) databases are not supported
  

• The RMAN catalog database must only contain a single DBID for the source database name that is selected for an offloaded backup.
  
  If multiple DBIDs exist for the same database name, then the following error occurs:
     RMAN-20005: target database name is ambiguous.
  Solution: Unregister the duplicate entries from the RMAN catalog.
  
  
• User actions necessary in Oracle Real Application Clusters (RAC)
  When using IBM Spectrum Protect Snapshot in Oracle Real Application Cluster (RAC) environments make sure that the following is observed:
• IBM Spectrum Protect Snapshot off-load and database cloning operations cannot share one server used as backup server and cloning server for Oracle ASM databases
  
  
• Database cloning with Oracle ASM: If the one of the log archive destinations refers an ASM disk group that is not part of the storage snapshot, then the create- or refresh-clone operation will fail. The alert log file will contain a statement like: 
  ARCH: Error 19504 Creating archive log file to '+<disk group name>'
  This limitation also applies if no log archive destination was specified and db_recovery_file_dest refers an ASM disk group that is not part of the storage snapshot. db_recovery_file_dest is used as default log archive destination if not otherwise specified. All disk groups that contain data files, control files or online log files are part of the storage snapshot.
  
  Work-arounds:
• Set the log archive destination to a disk group that is part of the storage snapshot or set it to a directory within a regular file system.
• In case no log archive destination was specified, set the db_recovery_file_dest to a disk group that is part of the storage snapshot or set it to a directory within a regular file system.
• Create the disk group that is claimed to be missing within the alert log file on the clone system manually
  
  
• When configuring an IBM Spectrum Snapshot instance the script setup_ora.sh allows to specify the value "GPFS" for parameter COPYSERVICES_HARDWARE_TYPE. However, the value "GPFS" is not supported for Oracle environments, and specifying this value results in an inoperable configuration. Fixed in 8.1.4
  
• Off-loaded backups will always be performed automatically
  
  When starting the Spectrum Protect Snapshot daemons by the Spectrum Protect Snapshot configuration wizard, all off-loaded backups to Spectrum Protect Server will be performed automatically by the fcmcli daemon. If the backups should be off-loaded manually by the user, the fcmcli daemon needs to be stopped after each configuration.
  
  Work-around:
  Stop the fcmcli daemon each time after running Spectrum Protect Snapshot configuration wizard.
  
  When using /etc/inittab:
  remove the fcmcli -D entry of the Spectrum Protect Snapshot instance from the /etc/inittab
  
  When using upstart/initctl:
  initctl stop <sps_instance_owner>-fcmclid
  
  When using systemd:
  systemctl stop <sps_instance_owner>-fcmclid
  
• Multitenant (pluggable) databases are not supported

• Off-loading snapshot backups in IBM Snapshot Scale (a.k.a GPFS) file systems to an IBM Spectrum Protect server may terminate with message FMM6572E if paths to filesets have a length of about 30 or more characters. In this case, the command output logged with message FMM6572E contains multiple lines
  "awk: String mmbackupIn cannot be longer than 399 bytes.".
  This is a limitation in IBM Spectrum Scale v4.1.1 and v4.2.0 which will be lifted in later deliverables of IBM Spectrum Scale.
  (IBM Spectrum Scale defect 75060)
  
  
• For Custom Applications on IBM Spectrum Scale or GPFS, all limitations specific to IBM Spectrum Scale apply.
  
  
• Spectrum Protect Snapshot backup fails if the infile contains files or directories for which the Spectrum Protect Snapshot application backup user does not have read permissions. (126143)
  
  Work-arounds: Make sure that all files or directories listed in the infile have read permission for the Spectrum Protect Snapshot application backup user. Subdirectories or files within those directories are allowed not to be accessible by the Spectrum Protect Snapshot application backup user.

• VIO/vSCSI configuration
  
  For AIX environments that use VIO / vSCSI storage adapter virtualization, the BACKUP_HOST_NAME must be set to the value of PREASSIGNED_VOLUMES when using DS or SVC storage devices.
  Note: The "backup_server_hostname" setting is not allowed.
  

• Installation on AIX 7.1 may fail with message 'Error: Port Library failed to initialize' and 'Error: Could not create the Java Virtual Machine.'. See sample below.
  
  ----------------------------------------------------------------------
  # ./4.1.4.0-TIV-TSFCM-AIX.bin -i console
  Preparing to install...
  Extracting the JRE from the installer archive...
  Unpacking the JRE...
  Extracting the installation resources from the installer archive...
  Configuring the installer for this system's environment...
  Launching installer...
  Error: Port Library failed to initialize: -125
  Error: Could not create the Java Virtual Machine.
  Error: A fatal exception has occurred. Program will exit.
  ----------------------------------------------------------------------
  
  Solution: See AIX APAR IV09585. The fix is available in AIX 7.1 TL 1 SP 2. It is recommended to obtain the fix as part of SP2.
  If you cannot upgrade to SP2, you can download the APAR fix available from
  https://www-304.ibm.com/support/docview.wss?uid=isg1IV09585
  
  
• IBM Spectrum Protect Snapshot may terminate with exit code 11 and without a speaking error message on AIX if an invalid profile parameter was specified in the device class section of the profile (130439)

• Installation when GSKit v8.0.13 is present.
  
  Installing IBM Spectrum Protect Snapshot v8.1 on a Linux machine with GSKit packages of version "8.0.13" already installed will fail with the following error: "Fatal error: No appropriate GSKit installation found."
  The command 'rpm -qa | grep gsk' will show:
  gskcrypt64-8.0-50.67
  gskssl64-8.0-50.57
  This indicates that the GSKit packages were successfully upgraded to the version delivered with IBM Spectrum Protect Snapshot. However, due to a flaw in the post-install scripts of GSKit 8.0.13, PATH variables are not set correctly so that the GSKit command line tools are not found. The issue was fixed with GSKit version 8.0.13.1.
  
  Work-around: Before installing IBM Spectrum Protect Snapshot, uninstall GSKit version 8.0.13. When IBM Spectrum Protect Snapshot is installed it will also install a more recent GSkit version. (81744)

• SELinux must be disabled
  
  SELinux is activated by default on Red Hat Enterprise Linux. However, SELinux must be disabled for the following environments / operations:
  
1. SAP/Oracle installations. SELinux should be permanently disabled in this environment. Please also refer to SAP Note 1048303 - „Red Hat Enterprise Linux 5.x: Installation and upgrade“.
   
2. When installing or uninstalling the IBM Spectrum Protect Snapshot applications, SELinux should be temporarily disabled.
   
To temporarily disable SELinux before uninstall, enter the following:
setenforce 0
To re-enable SELinux after completing the uninstall process, enter the following:
setenforce 1

• HA features of the supported logical volume managers must not be activated in combination with IBM Spectrum Protect Snapshot V8.1.x.

• Restore may fail when a logical volume is open on Red Hat Enterprise Linux .
  
  In rare cases, the Linux LVM does not remove / reset the "Open" state of a logical volume (LV) after the file system for that LV has been unmounted. When this occurs, IBM Spectrum Protect Snapshot restore operations to the affected LV will fail with the following message:
  
  FMM1040E … Remove failed for logical volume <logical_volume_name> ... Can't remove open logical volume <logical_volume_name>
  
  Rebooting the system will reset the state of the LV and you can attempt your IBM Spectrum Protect Snapshot restore operation.

• File systems imported and mounted with IBM Spectrum Protect Snapshot mount operations on Linux are not added to the (v)fstab. Therefore, you would need to remount the file systems manually after a system reboot. This should be considered especially in case of cloned environments that are used over a longer period (and may need to persist beyond machine reboot).
  Work-around: Add the required file systems to your (v)fstab.
  
  
• Starting with RHEL 7 and SLES 12 LVM2 has enabled the Metadata Daemon (lvmetad) by default. The LVM Metadata Daemon causes Spectrum Protect Snapshot operations to fail.
  Work-around: Disable the LVM Metadata Daemon as described in the Red Hat documentation https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Logical_Volume_Manager_Administration/metadatadaemon.html
  
  
• Certain Linux LVM2 versions are not supported by IBM Spectrum Protect Snapshot. See the Pre-installation Checklist for supported versions. If an unsupported LVM2 versions is used the mount operation may fail with an error message from the operating system adapter component.
  FMM1040E An exception occured in the operating system adapter component, exception text: Type: '<class 'xsf.host.storage.volume_manager.errors.VolumeManagerPhysicalVolumeError'>', Value: 'Cannot resignature physical volume /dev/mapper/mpathaeowith error:   Replacing dev /dev/mapper/mpathaeo pvid 4hPxGPwk3tUK1EfvcYwKBJ0Gf5Q3SakK with dev /dev/mapper/mpathaeo pvid Cy8HPEVveTGqpQYmNYEvvByWNBkSgmVg', Traceback: '<traceback object at 0x7f4ccc96bcf8>'.
  If tracing is enabled the xsflog.<backup_host_name>.mount.<timestampe for e.g. 20161206124634>.trace file contains:
  
  2016-12-06 12:47:08 INFO     Running command '['pvchange', '/dev/mapper/mpathaeo', '-u']...'
  2016-12-06 12:47:08 DEBUG    Command line 'pvchange /dev/mapper/mpathaeo -u' has ended with exit code 0.
  stdout:
    Physical volume "/dev/mapper/mpathaeo" changed
    1 physical volume changed / 0 physical volumes not changed
  
  stderr:
  File descriptor 3 (/CAA/TGC/tc_tool/tc/Temp/logs/acsgend.texasback5.20161206.32623.trace) leaked on pvchange invocation. Parent PID 1134: /CAA/TGC/acs/acsgen
  File descriptor 4 (/dev/null) leaked on pvchange invocation. Parent PID 1134: /CAA/TGC/acs/acsgen
  File descriptor 5 (/CAA/TGC/tc_tool/tc/Temp/logs/acsgen.texasback5.mount.20161206124634.trace) leaked on pvchange invocation. Parent PID 1134: /CAA/TGC/acs/acsgen
  File descriptor 6 (/dev/null) leaked on pvchange invocation. Parent PID 1134: /CAA/TGC/acs/acsgen
  File descriptor 7 (/dev/pts/0) leaked on pvchange invocation. Parent PID 1134: /CAA/TGC/acs/acsgen
  File descriptor 8 (/dev/pts/0) leaked on pvchange invocation. Parent PID 1134: /CAA/TGC/acs/acsgen
  File descriptor 9 (/dev/pts/0) leaked on pvchange invocation. Parent PID 1134: /CAA/TGC/acs/acsgen
  File descriptor 10 (/dev/pts/0) leaked on pvchange invocation. Parent PID 1134: /CAA/TGC/acs/acsgen
  File descriptor 12 (/CAA/TGC/acs/pipes/readpipe1134_0) leaked on pvchange invocation. Parent PID 1134: /CAA/TGC/acs/acsgen
  File descriptor 13 (/CAA/TGC/acs/pipes/writepipe1134_0) leaked on pvchange invocation. Parent PID 1134: /CAA/TGC/acs/acsgen
  File descriptor 14 (/CAA/TGC/tc_tool/tc/Temp/logs/acsgen.texasback5.mount.20161206124634.trace) leaked on pvchange invocation. Parent PID 1134: /CAA/TGC/acs/acsgen
  File descriptor 15 (/CAA/TGC/tc_tool/tc/Temp/logs/xsflog.texasback5.mount.20161206124634.trace) leaked on pvchange invocation. Parent PID 1134: /CAA/TGC/acs/acsgen
  File descriptor 16 (pipe:[328367]) leaked on pvchange invocation. Parent PID 1134: /CAA/TGC/acs/acsgen
    Replacing dev /dev/mapper/mpathaeo pvid 4hPxGPwk3tUK1EfvcYwKBJ0Gf5Q3SakK with dev /dev/mapper/mpathaeo pvid Cy8HPEVveTGqpQYmNYEvvByWNBkSgmVg
  
  2016-12-06 12:47:08 ERROR    An exception of type <class 'xsf.host.storage.volume_manager.errors.VolumeManagerPhysicalVolumeError'> was raised with the following message: Cannot resignature physical volume /dev/mapper/mpathaeowith error:   Replacing dev /dev/mapper/mpathaeo pvid 4hPxGPwk3tUK1EfvcYwKBJ0Gf5Q3SakK with dev /dev/mapper/mpathaeo pvid Cy8HPEVveTGqpQYmNYEvvByWNBkSgmVg
  2016-12-06 12:47:08 ERROR    Current stack:
    File "build/bdist.linux-x86_64/egg/xsf/host/storage/volume_manager/__init__.py", line 607, in import_volume_group
      physical_volumes)
    File "build/bdist.linux-x86_64/egg/xsf/host/storage/volume_manager/linux.py", line 270, in import_volume_group
      self._resignature_vg_lvs_and_pvs(volume_group)
    File "build/bdist.linux-x86_64/egg/xsf/host/storage/volume_manager/linux.py", line 236, in _resignature_vg_lvs_and_pvs
      self.resignature_physical_volume(pv)
    File "build/bdist.linux-x86_64/egg/xsf/host/storage/volume_manager/linux.py", line 678, in resignature_physical_volume
      VolumeManagerMessages.WITH_ERROR(stderr)))
  
  Solution:
  Check the Pre-installation Checklist for the supported LVM2 versions. Some LVM2 versions have an issue with the pvchange command that command output ist written to the stderr output.
  This causes a problem in the operating system adapter during mount and the mount fails with the above error message.
  With a supported LVM2 version this problem is solved.

• acsutil can fail on SLES Linux with this error:
  error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
  Work-around: Create a link within /lib64 to the ncurses library like this:
  ln -s libncurses.so.5 libtinfo.so.5

• IBM Spectrum Protect Snapshot operations in VMware® Virtual Machines
  IBM Spectrum Protect Snapshot can back up, restore, and perform clone operations on VMware virtual machines that run Linux guest operating systems.
  
  All source LUNs that participate in backup or clone operations must be attached to the virtual machine by using one of the following attachment methods:
  • VMware physical mode raw device mapping (pRDM)
  • iSCSI
  • Network File System (NFS)
  
  IBM Spectrum Protect Snapshot can perform a FlashCopy restore operation from a snapshot to an existing pRDM disk but does not create a virtual machine or pRDM definition as part of the restore process.
  
  If the backup or clone system is a virtual machine then all target LUNs that participate in backup or clone operations must be attached to the virtual machine by using one of the following attachment methods:
  • iSCSI
  • Network file system (NFS)
  
• IBM Spectrum Protect Snapshot operations in Linux KVM Virtual Machines
  IBM Spectrum Protect Snapshot can back up, restore, and perform clone operations on Linux KVM virtual machines that run Linux guest operating systems.
  
  All source LUNs that participate in backup or clone operations must be attached to the virtual machine by using one of the following attachment methods:
  • Block device mapping (BDM)
  • iSCSI
  • Network File System (NFS)
  • PCI Passthrough
  
  For the Tivoli® Storage FlashCopy® Manager KVM setup using Block Device Mapping (BDM), the LUNs must be mapped to the KVM guest as multipath devices. The LUNs must be visible inside the KVM guest as multipath devices.
  
  From within the KVM guest, run the multipath command. The output from running this command looks similar to the following example:
  
  kvm-guest:~ # multipath -ll
  mpathat (360050768018205de4000000000001949) dm-7 IBM    ,2145
  size=2.0G features='1 queue_if_no_path' hwhandler='0' wp=rw
  `-+- policy='service-time 0' prio=50 status=active
  `- 3:0:0:3 sdf 8:80 active ready running
  
  The LUN identifier is a unique number like this 360050768018205de4000000000001949, and must not be overwritten by the KVM stack. The product storage identifier like this IBM ,2145 must be visible inside the KVM guest.
  
  If the backup or clone system is a virtual machine then all target LUNs that participate in backup or clone operations must be attached to the virtual machine by using one of the following attachment methods:
  • iSCSI
  • Network file system (NFS)

• Clean-up of the takeover host after remote restore on IBM XIV® Storage System
  
  When using IBM Spectrum Protect Snapshot v8.1 in combination with the remote mirror functionality of an IBM XIV® Storage System or with the metro mirror or global mirror functionality of the IBM System Storage SAN Volume Controller or IBM Storwize V7000, take care to clean up the take-over host after a remote restore before making the original production site the master of the remote relation again.
  The following scenario may leave the instance on the take-over host in an unpredictable state:
1. A remote FlashCopy or snapshot backup is restored to and mounted on the take-over host, for example due to disaster or maintenance.
2. In order to switch back to the original production system, the remote copy relationship is reverted to the original production site as the master.

Work-around: Prior to switching back to the original production site, deactivate the remote backup on the take-over host by performing the following procedure:
1. Unmount all file systems of the backup restored.
2. Vary off-line the volume groups involved.
3. Export the volume groups involved.
4. Remove the devices involved from the take-over host.
(84992)


• Limitation concerning remote relations on IBM XIV® Storage System after restore
  
  When using IBM Spectrum Protect Snapshot v8.1 in combination with the remote mirror functionality of an IBM XIV® Storage System, XIV demands that IBM Spectrum Protect Snapshot deactivates and deletes the remote relationship before restoring a snapshot to either the master or the slave volume of a remote mirror relation. After restoring, IBM Spectrum Protect Snapshot does not recreate the mirror relations.
  
  Work-around: After IBM Spectrum Protect Snapshot restore, use the XIV XCLI or GUI to create the remote relationships and start the synchronization. (87292)
  
  
• Backups might fail if a volume migration of OLVM volumes is ongoing. IBM Spectrum Protect Snapshot is able to protect OLVM volumes before and after their migration. Before the migration it is configured to use the source XIV system as storage device. Once the disks were migrated, IBM Spectrum Protect Snapshot needs to be reconfigured to use the target XIV system as storage device for the backup.
  
  
• Limitations related to XIV Multi-Site Mirroring environments:
  
• FlashCopy Manager fails to restore snapshots if the volumes containing the application data are mirrored into two or more destinations with XIV Multi-Site Mirroring.
• FlashCopy Manager fails to create snapshots of mirrored volumes if the application data is mirrored into two or more destinations with XIV Multi-Site Mirroring. Snapshots of local source volumes can be created.
  
In both scenarios FlashCopy Manager fails with an error message containing this text: "VOLUME_HAS_MULTIPLE_MIRRORS volume has multiple mirrors, operation not allowed or target must be specified"

Work-around: Remove all mirror relations manually, before triggering a restore operation with IBM Spectrum Protect Snapshot. To create a snapshot of a remote mirror, ensure that only one mirror of the volumes containing the application data exists.

• Limitation for environments where source volumes of a FlashCopy are mirrored by using the ability of the SVC to create volumes with two copies, and where the copies are in two different SVC storage pools: When using dynamic allocation of FlashCopy target volumes in such environments the storage pool for the target volumes of the FlashCopy is not automatically determined.
  Work-around: Specify the SVC storage pool for the target volumes explicitly via parameter SVC_POOLNAME in the DEVICE_CLASS section of the IBM Spectrum Protect Snapshot profile.
  
  
• For IBM Spectrum Protect™ Snapshot to work in combination with dynamic target allocation (SVCDTA) device classes, the name of the SAN Volume Controller production source volumes must not exceed the length of 27 characters.
  
  An IBM Spectrum Protect Snapshot backup involving a volume with a longer name fails with the following SVC error message:
  CMMVC5738E The argument contains too many characters.
  
  There is no work-around to allow source volume names of length larger than 27 characters.
  The sample below shows however that a volume name smaller than 27 characters can be practicable.
   
  Example:
  Given the sample input source volume name „esxcet1_vol1“, IBM Spectrum Protect Snapshot SVC DTA adapter would generate the following object names in SAN Volume Controller:
  
  Name of the dynamic allocated target volume for the snapshot backup operation:
  esxcet1_vol1_A0ITWN5DGH_ITWN6A1F_1
  Name of the duplicate target volume used for the mount operation:
  esxcet1_vol1_A0ITWN5DGH_ITWN6A1F_1_dup
  Name of the FlashCopy mapping:
  TSM_A0IO1BN9X6_A0IW39B9GG_IW39J8A6_esxcet1_vol1
  Name of the cosistency group
  TSM_A0IO1BN9X6_A0IW39B9GG_IW39J8A6  

• Misleading error message when requesting additional incremental backups on DS8000
  
  On an IBM System Storage DS8000 series, only a single incremental relation can be created. When a second incremental relation is requested for a DS8000, the following error message is issued:
  
  FMM0777E An unexpected error was encountered processing a function.
  function name : DsHWInterface::hwStartCopy
  function : CIM Error. Failed to execute IBMTSDS_StorageConfigurationService::AttachReplicas , Return: Failed
  CIM Error Code : ReturnCodes: <0xb040 0xb040>
  0xb040: FlashCopy operation failure: action prohibited by current FlashCopy state. Contact IBM
  technical support for assistance.
  return code : 4
  
  Though the error may be misleading, the issue at hand is that it is not supported to create multiple incremental FlashCopy relations on the DS8000 from the same source volume.

• IBM Spectrum Scale snapshots are located in the productive file systems. Due to their copy-on-write technology, their sizes grow over time as the database is modified. When configuring IBM Spectrum Protect Snapshot, administrators are asked to assess how many file system snapshots can be kept in the file system without risking a file-system-full condition.
  The number of IBM Spectrum Scale snapshots kept in the file systems is controlled with IBM Spectrum Protect Snapshot profile parameter MAX_VERSIONS. This parameter cannot be set to the value ADAPTIVE in IBM Spectrum Scale environments, but must be set to the number of snapshots to be kept.
  During production, administrators must continuously monitor free space in the IBM Spectrum Scale file systems where the database and log files reside in order to avoid a file-system-full condition of the productive file systems. Monitoring can be done with commands df and mmdf.
  
  
• Nested IBM Spectrum Scale filesets are not supported.
  Specifically, if the root fileset of a file system participates in the backup other filesets are not allowed in this file system. If the root fileset does not participate in the backup various independent filesets linked in the root fileset can be defined.
  
  
• Nested file systems (i.e. file systems mounted on paths in other file systems) are not supported.
  
  
• Symbolic links are supported only when the links point to files in the same file system and fileset.

• Duplicate informational messages
  
  During IBM Spectrum Protect Snapshot operations, a customer may see some duplicate informational messages in the IBM Spectrum Protect Snapshot log files.
  Examples for messages that can occur multiple times:
  FMM6555I Selected snapshot backup with ID '<BACKUP_ID>'.
  FMM6503I Terminating 'fs_chown_clone' request.
  FMM1014I Operation postproc_clone completed successful.
  

• An offloaded tape backup of a multi-partition DB2 database with Database Partitioning Feature (DPF) may be reported as unsuccessful by IBM Spectrum Protect Snapshot v8.1.0.0 although all partition backups were successfully sent to an IBM Spectrum Protect server.
  
  The corresponding log file in the details path may contain a sequence of messages similar to this:
  FMM6542I 20:33:26 db2dr1 DR1 1 20161114202354 20161114203305
  FMM6542I 20:33:26 db2dr1 DR1 2 20161114202354 20161114203313
  FMM6542I 20:33:26 db2dr1 DR1 3 20161114202354 20161114203321
  FMM6542I 20:33:26 db2dr1 DR1 ## 20161114202354 -
  FMM6544I Snapshot backup suspend time: 20161114202621
  FMM6283E offloaded tape backup unsuccessful.
  
  The error message can be ignored in case the states of the backups of all partitions show TAPE_BACKUP_COMPLETE when requesting the status via db2acsutil.

• When configuring an IBM Spectrum Snapshot instance the script setup_ora.sh allows to specify the value "GPFS" for parameter COPYSERVICES_HARDWARE_TYPE. However, the value "GPFS" is not supported for Oracle environments, and specifying this value results in an inoperable configuration.