IBM Support

Known Issues and Limitations: IBM Spectrum Protect Plus V10.1.3.x

Preventive Service Planning


Abstract

This document details the Known Issues & Limitations for IBM® Spectrum Protect™ Plus V10.1.3 and later patches.

Content

This document is divided into linked sections for ease of navigation. Use the following links to jump to the section of the document that you require:


IBM Spectrum Protect Plus common

Automatic VADP proxy update fails when upgrading IBM Spectrum Protect Plus version 10.1.2 to version 10.1.3 or version 10.1.3 to version 10.1.4. (internal reference #SPPSUP-1129)
Problem: When upgrading IBM Spectrum Protect Plus, the VADP proxy will be automatically upgraded. If upgrading from V10.1.2 to V10.1.3 or V10.1.3 to V10.1.4, this upgrade will fail with an error message in the Virgo log stating:
"Cannot automatically update VADP with the name <server name>. Manual update required. [Error => No identity stored for VADP instance with ID <ID number>".
Workaround:  Manually update the VADP proxy to resolve the issue. For more information on manually updating VADP proxies, see Updating VADP proxies.
Limitation: Since 10.1.2.
 

The EULA can not be displayed when upgrading vSnap (internal reference #SPPSUP-707)
Problem: When upgrading vSnap, the EULA is reported as being a binary file which results in the agreement not being displayed
Workaround: Install the upgrade to vSnap by executing the following commands:
chmod +x<filename> .run             
where <filename> is the name of the vSnap upgrade file.
sudo bash
In the new terminal that opens, execute the following command:
./.run
where is the name of the vSnap upgrade file that was made executable in the step above.
Limitation: Since V10.1.2.
 

Recurring VM restore fails at second restore time (internal reference #SPP-10076)
Problem: Configure a re-occurring restore in clone mode can't be combined with specifying a dedicated VM name. The second and all following restore operations will fail due to naming and UUID conflicts in the vCenter.
Workaround: Do not specify a dedicated VM name when configuring a re-occurring restore in clone mode. If a name is specified, delete or rename the previously created VM, and re-run the job.
Limitation: Since V10.1.2. Permanent restriction.
 

IBM Spectrum Protect Plus does not support Unicode normalization (internal reference #SPP-6852 & SPP-8705)
Problem: When using the search fields in the IBM Spectrum Protect Plus product, glyphs that are visually equivalent but created with different code point representation might not be returned in the search results.
For example, a user from France might create a backup: sauvegarde_incrémentielle_220419. Depending on the “é” used in the string, the results might not be returned when searching because IBM Spectrum Protect Plus does not support Unicode normalization.
That is, é (U+0065 U+0301) versus é (U+00E9) are two different representations of the same character in the string. Depending on the one being used in search, results might not be returned because the target of the search contained a character that was created using an alternate code point representation.
Workaround: When using any search box in IBM Spectrum Protect Plus, if it is suspected that characters such as the one above was used, always remember to include different variations of the code point representation in the search.
Limitation: Since V10.1.3. Permanent restriction, see APAR IT34542.
 

IBM Spectrum Protect Plus sorting order is not in ICU collation order (internal reference #SPP-6851 & SPP-8634)
Problem: The IBM Spectrum Protect Plus product does not follow ICU collation sorting for menus, therefore, the ordering of menus will appear in code point order.  For example, some languages sort letters differently from code point order. As such, the sorted order of characters and words as they appear in menus when using these languages will appear out of expected order.
Workaround: None.
Limitation: Since V10.1.3. Permanent restriction, see APAR IT34456.
 

SLA filter drop-down only appears after searching on backup selection screen.(internal reference #SPP-6571 & #SPP-5913)
This issue is resolved in IBM Spectrum Protect Plus 10.1.4
Problem: The SLA filter drop-down under the VMware backup screen does not appear until you perform a search in the backup selection.
Workaround: Search * in the search bar and the SLA filter drop-down will appear.
Limitation: Since V10.1.3.
 

Backups of a failover cluster with SQL DBs residing on Cluster Shared Volume always runs as base backup (internal reference #SPP-6580)
Problem: SQL Database backups residing on Cluster Shared Volume(CSV) always runs as base backup since change block tracking is not supported on CSV File system.
Workaround: Failover clusters with DBs running on CSV File system is not supported.
Limitation: Since V10.1.3.
 

Failure to access vSnap server for catalog restore after upgrading from 10.1.2.(internal reference #SPP-6690)
Problem: On Physical vSnap servers, after upgrading from 10.1.2, IBM Spectrum Protect Plus fails when trying to access the vSnap server for catalog restore.
Workaround: User must manually create the /opt/vsnap-data cache area expected in 10.1.3. Refer to procedure documented in Cloud object storage offload configuration
Limitation: Since V10.1.3.
 

Web user interface stuck with the message “Server is being brought up”. (internal reference #SPP-6698)
Problem: Under rare circumstances, when trying to connect to the Web user interface to deploy an IBM Spectrum Protect Plus server, the Web user interface doesn’t progress past the “Server is being brought up. Please wait…” message.
Workaround: Reboot the IBM Spectrum Protect Plus Server Appliance.
Limitation: Since V10.1.3.
 

Granular resource counts for Replication and offload do not display correct counts when new VMs are added to SLA and results in partial failure.(internal reference #SPP-6718)
Problem: When VMs or DBs are added to an SLA after backup has completed but before replication and offload, the counts displayed for successful and failed VMs and DBs are inaccurate.
Workaround: none
Limitation: Since V10.1.3.
 

Application Server can be deleted even during an active restore job. (internal reference #SPP-6796)
Problem: Application servers defined within IBM Spectrum Protect Plus can be deleted by a user even during an active restore job. This could result in subsequent clean up failures.
Workaround: Check for active restore jobs pointing to the Application Server before deletion
Limitation: Since V10.1.3.
 

When upgrading from IBM Spectrum Protect Plus version 10.1.3 to version 10.1.4, manually running a previously created policy (10.1.3) that has an associated sub-policy added will result in a null-pointer exception (internal reference #SPPSUP-1115)
Problem: In IBM Spectrum Protect Plus, after upgrading from version 10.1.3 to version 10.1.4, manually running a previously created SLA policy that also has an associated sub-policy will result in a null-pointer exception. The automatic running of the SLA policy will work correctly.
Workaround: Edit the original SLA policy, but do not change anything with the policy and then click Save. Next, manually start the policy. The user will then be prompted to select the sub-policy.
Limitation: Since V10.1.3.
 

Admin Console user interface still displays trial license after updating to perpetual license. (internal reference #SPP-7043)
Problem: The Admin Console user interface displays the trial license information after updating to the perpetual license.
Workaround: Clear your browser cache and reload the Admin console to show the correct information.
Limitation: Since V10.1.3.
 

Unused objects are not all being deleted after cloud offload (internal reference #SPP-5849)
Problem: When an SLA policy is deleted and all the recovery points are purged out from vSnap, some of the objects that are not being used may still exist in cloud buckets.
Workaround: This issue is targeted to be resolved in next IBM Spectrum Protect Plus fix pack.
Limitation: Since V10.1.3.
 

Test Restore Jobs disappear after a vSnap upgrade (internal reference #SPP-6052)
Problem: Restore Jobs in test mode disappear when upgrading the vSnap server to the latest version. Test Restore jobs are not persisted when vSnap server is restarted.
Workaround: To avoid the issue, Defer Upgrade until all test restore jobs can be canceled. Rerun Test Restore jobs if the issue is encountered.
Limitation: Since V10.1.3.
 

vSnap hangs due to connectivity failure
Problem:  Offload to the Cloud or a Repository server may fail due to network connectivity issues. This may prevent success in further offloading for the same volume.
Workaround: Reboot the vSnap to discard the suspended pool and resume routine operations.
Limitation: Since V10.1.3.
 

If the latest restore point of a resource is manually expired, older versions of the restore point will not display on Restore screens (internal reference #SPP-4220)
Problem: If the latest restore point of a resource is manually expired through the Restore Point Retention screen, older versions of the restore point will not display on associated Restore screens.
Workaround: Run the backup job again to capture the latest restore point. Once complete, older versions of the restore point will display on associated Restore screens.
Limitation: Since V10.1.2.
 

SLA policy and backup option selections for a folder are not retained if the folder is moved (internal reference #SPP-4388)
Problem: If a folder is moved through the vCenter interface after SLA policies or backup options are assigned to the folder and an Inventory job is run, the selections are not retained in IBM Spectrum Protect Plus. Any virtual machines within this folder that were previously backed up will no longer be backed up.
Workaround: After a folder is moved and its new location is logged by the Inventory job, re-associate the folder with the SLA policy and reassign the backup options.
Limitation: Since V10.1.2.
 

After a Catalog restore completes on a target appliance, the associated Catalog backup job returns an ABORT state on the destination appliance (internal reference #SPP-994)
Problem: After a Catalog restore completes on a target IBM Spectrum Protect Plus appliance, the Catalog Backup job that is carried over to the new appliance initially shows that the job last ran in an ABORT state.
Workaround: This is expected due to the snapshot transition. When the Catalog Backup is run on the source, the snapshot is taken while the Catalog Backup is running.
Limitation: Since V10.1.1. Permanent restriction, see APAR IT34548.
 

When creating a custom Resource Group, there is no option to add resources through the Tags & Categories view type (internal reference #SPPL3-626, #SPP-1874)
Problem: When creating a custom Resource Group and adding VMware resources, there is no option to filter selections based on the Tags & Categories view type.
Workaround: None.
Limitation: Since V10.1.1.
 

Backups fail when a vSnap certificate is changed (internal reference #ECC-12208, # SPP-9356)
Problem: When a vSnap certificate is changed, such as when a user imports a certificate, backups will fail with the following error:
"Failed to get Live Storage reason : server certificate change is restricted during renegotiation."
Workaround: The IBM Spectrum Protect Plus service must be restarted from the Administrative Console to allow backups to complete again.
Limitation: Since V10.1.0.
 

Jobs cannot be saved when scheduling a report with a frequency less than 5 minutes when using Microsoft Edge (internal reference #ECC-12221),
Problem: By default, a warning message displays in IBM Spectrum Protect Plus when attempting to schedule a report with a frequency that is less than 5 minutes. However, when defining a report schedule with a frequency that is less than 5 minutes with Microsoft Edge, the warning message does not display, and the job cannot be saved.
Workaround: Select frequencies that are 5 minutes or higher, or use a different supported browser when creating schedules.
Limitation: Since V10.1.0.
 

First entries in lists automatically display in menus when using Microsoft Edge (internal reference #ECC-12203)
Problem: When selecting options from drop-down menus in IBM Spectrum Protect Plus, the first entry in a list automatically displays in the menu when using the Microsoft Edge browser; however, the item is not selected. In addition, if there is one entry in a drop-down menu, the item cannot be selected when using the Microsoft Edge browser.
Workaround: None.
Limitation: Since V10.1.0.
 

Certificates in the .p12 format cannot be imported through the Administrative Console (internal reference #ECC-12119)
Problem: The Administrative Console supports importing external public key certificates, which allows the appliance to make outbound connections to resources, such as secured LDAP and secured HTTPS servers. The certificate import feature supports .cer and .crt certificate types. Note that .p12 certificates can only be imported into the IBM Spectrum Protect Plus keystore.
Workaround: To import the .p12 certificates into the keystore, perform the following procedure:
Login as root user on the IBM Spectrum Protect Plus appliance and at the command line execute the following command:
“/usr/java/latest/bin/keytool -importkeystore -deststorepass ecx-beta -destkeystore /opt/virgo/configuration/keystore -srckeystore cs.p12 -srcstoretype PKCS12"
Then reboot the appliance.
Limitation: Since V10.1.0.
 

Offloading to IBM Spectrum Protect fails if FlashCopy Manager is installed on the data mover machine (internal reference #SPPL3-297, #SPP-1812)
Problem: When performing an offload job from IBM Spectrum Protect Plus to IBM Spectrum Protect, the job fails if Flash Copy Manager is installed on the associated data mover machine.
Workaround: Uninstall the Flash Copy Manager component from the data mover machine.
Limitation: Since V10.1.0.
 

IBM Spectrum Protect Plus system log sizes grows in some situations. (internal reference #SPPSUP-374)
Problem:  ** IBM Spectrum Protect Plus does not offer a mechanism to limit log sizes to a specific size. If the system log file is too large the file system could be filled and the download of this log file is difficult. Logs that contribute to large deviations are however regularly reviewed for its usefulness to troubleshooting.
Workaround: Make sure that logs are reviewed and removed regularly.
Limitation: Since V10.1.0. Permanent restriction, see APAR IT26590.
 

In IBM Spectrum Protect Plus, permission groups specify the ability to edit a certificate, but no edit button is displayed on the Keys and Certificates screen. (internal reference #SPP-8611)
Problem:  Certain pre-defined roles have assigned permission groups that allow for creating, viewing, editing, or removing certain features of IBM Spectrum Protect Plus.  In particular, the Application Admin, Backup Only, Restore Only and SYSADMIN groups have the Edit ability for Certificates.  However, if a user that is assigned to one of these groups views certifications on the Keys and Certificates screen, there is no Edit button.  Currently, there is no way to edit a certificate from the Keys and Certificates screen.
Workaround: None.
Limitation: Since V10.1.0. Permanent restriction, see APAR IT34549.
 

In IBM Spectrum Protect Plus, when a datacenter is associated with an SLA, the number of backed up VMs may be more than the number of VMs in the datacenter. (internal reference #SPP-8509)
Problem: An NFS volume can be mounted to any number of datacenters in the same vCenter. When a NFS volume is mounted on more than one datacenter on a vCenter, even though vCenter treats the same volume as two different datastores, SPP treats this a single datastore and combines all the VMs and VMDKs residing on this datastore from all the datacenters this datastore is mounted on. Therefore, any SLA selection/resolution against this datastore will cause all the VMs from the different datacenters to be backed up.
Workaround: None.
Limitation: Since V10.1.0.


 


Hypervisor VMware related

Independent disks are not contained in VM snapshots (internal reference SPPSUP-1980)
Problem: IBM Spectrum Protect Plus does not back up independent disks in VM snapshots for backup jobs. Independent mode virtual disks do not support snapshot operations. See also Change Disk Mode to Exclude Virtual Disks from Snapshots
Workaround: None.
Limitation: Since v10.1.1. Permanent restriction.
 

Full base backups occur after storage vMotion operation (internal reference #SPPSUP-237)
Problem: Incremental backups are not performed after a storage vMotion operation occurs to a new datastore. Backups that occur after the storage vMotion operation will run as full base backups.
Workaround: None.
Limitation: Since v10.1.1.
 

IBM Spectrum Protect Plus backup of Windows Server 2019 fails with error: “Error: com.vmware.vim25.ApplicationQuiesceFault” (internal reference #SPP-9873)
Problem: Performing a backup job of Windows Server 2019 without enabling the option “Fall back to unquiesced snapshot if quiesced snapshot fails” can fail with the error message: “Error: com.vmware.vim25.ApplicationQuiesceFault An error occurred while quiescing the virtual machine.”
Workaround: Disable the VMware Snapshot Provider service in the guest operating system (OS) and allow the Microsoft Volume Shadow Service to run automatically.  Once this has been done, re-attempt the backup job that failed with the error.
Disable the VMware Snapshot Provider service in the guest OS:

  1. Login to the guest operating system using administrator credentials.
  2. On the keyboard, click the Windows key + R to open the Run dialog box.
  3. Type services.msc and press the Enter key.
  4. Locate and right-click on the VMware Snapshot Provider entry and left-click on Properties.
  5. Set Startup type to Disabled and click Apply and then OK.

Ensure that the Microsoft Volume Shadow Service is set to automatic in the guest OS:

  1. Login to the guest operating system using administrator credentials.
  2. On the keyboard, click the Windows key + R to open the Run dialog box.
  3. Type services.msc and press the Enter key.
  4. Locate and right-click on the Volume Shadow Service entry and left-click on Properties.
  5. Set Startup type to Automatic and click Apply and then OK.

Re-attempt any backup jobs that failed as a result of the error.
Limitation: Since v10.1.3.


 


Hypervisor Hyper-V related

Backup and restore operations for Hyper-V shared virtual hard disks fails (internal reference #SPP-1108)
Problem: When attempting to run a backup of a Hyper-V shared virtual hard disk (shared VHDX), the backup fails with the following error:
“Failed to create Snapshot .ava.lang.NullPointerException.”
Shared virtual hard disks in a Hyper-V environment are not supported in IBM Spectrum Protect Plus.
Workaround: None.
Limitation: Since V10.1.1. Permanent restriction, see APAR IT34557.
 

Backup target LUNs on vSnap storage do not automatically expand for Hyper-V backups (internal reference #ECC-11356, #SPP-2719)
Problem: For Hyper-V backups, if the source datastore is expanded, the backup target LUN on vSnap storage does not automatically expand.
Workaround: None.
Limitation: Since V10.1.0.


 


SQL application server related

vSnap password fails when attempting to access CIFS share with the associated account credentials (internal reference #SPPSUP-561)
Problem: The vSnap credentials registered with IBM Spectrum Protect Plus do not work when trying to access the CIFS share when using the same account credentials. The credentials will need to be re-synchronized to ensure continued access.
Workaround: The vSnap password should be changed to the same value to manually force synchronization. In this example, the username is “vsnapuser” Credentials can be manually synchronized by entering the following commands on the vSnap Server:

  • Update the operating system credentials which are used for management communication through the vSnap API:
    sudo passwd vsnapuser
  • Update the CIFS credentials which are used for communication between the application server and vSnap:
    sudo smbpasswd vsnapuser

Finally, update the vSnap registration in IBM Spectrum Protect Plus to ensure that the updated password is entered into the system. At this time, you may re-run the job that failed as a result of the problem.
Limitation: Since V10.1.2.
 

IBM Spectrum Protect Plus limits the log backup of a database from only one SLA (internal reference #SPPSUP-703)
Problem: The log backup of a database is limited to only one SLA. If there are two SLAs, one to protect a SQL Server Always-On availability groups (AG) and another to protect databases on a standalone instance, if a database is moved from AG to standalone, or standalone to AG, log backup for that database could fail from the SLA that protect the target of the move.
Workaround: After moving the database from the standalone to AG or AG or standalone, run the SLA that was protecting the database prior to the move once more. Doing this will remove the log backup for that database. Once that is completed, run the second SLA that will protect the database at the new location. That will create the log backup for that database.
Limitation: Since V10.1.1. Permanent restriction, see APAR IT28420.
 

SQL server databases with non-ASCII characters are not available for Backup Selection. (internal reference # SPP-6059)
Problem: If a SQL server have databases with non ASCII character names, the inventory job for that SQL server will complete but the job log will have the following error "Failed to merge SQL application discovery output c:\ProgramData\SPP\<uuid>\output_sql.json". The Database is not available for Backup Selection.
Workaround: Rename the Database with ASCII characters.
Limitation: Since V10.1.3.


 


ORACLE application server related

An entry in ‘srvctl’ is not created after a successful Oracle database restore to a RAC destination (internal reference # SPP-843)
Problem: After successfully restoring an Oracle database to a RAC destination, IBM Spectrum Protect Plus does not automatically create an entry in 'srvctl' for the restored database.
Workaround: An entry in ‘srvctl’ must be manually created if desired.
Limitation: Since V10.1.1.
 

Error messages returned from Oracle servers running non-English languages may not be displayed correctly. (internal reference #SPP-6193)
Problem: When Spectrum Protect Plus experiences errors while attempting to backup or restore an Oracle database, it attempts to capture the error messages returned by Oracle and display them in the backup/restore job log. If the Oracle database runs with the NLS_LANGUAGE set to a non-English language by default, then the error messages may contain characters that cannot be formatted or displayed correctly in the job log. As a result, those specific error messages may not be readable when the job log is viewed or downloaded.
Workaround: While the message itself may not be readable, the message prefix will contain a standard error code starting with "ORA" or "RMAN". Use Oracle support/documentation resources to look up the message associated with the error code.
Limitation: Since V10.1.3.


 


Db2 application server related

Database is subtly excluded from scheduled backup when volume group is running out of free space (internal reference #SPP-db2-179999 & #SPP-9108)
Problem: During inventory, volume groups holding data of databases are checked for free space to ensure that temporary snapshots can be successfully created during the backup operation. In case of there is not sufficient free space available, the database is declared to be ineligible for backup with the according reason message. However, the free space can be sufficient initially and the database has been added to a SLA policy. When the free space declines successively it might fall below the minimum limit. A warning message will indicate the situation, however, it is not rated as a failed backup - the database will just be silently skipped. The summary of the scheduled backup run will just show a decreased number of protected databases.
Workaround: Create backup reports frequently and verify that all important databases have recent backups. Monitor the free space of volume groups and ensure to expand it timely when necessary.
Limitation: Since V10.1.2.
 

Archive log backups are limited to a single SLA policy per database.(internal reference #db2-175439)
Problem: When archive log backups are enabled on the Db2 Backup options panel, it applies to all SLA policies the database is associated with.
For each SLA policy, an extra archive log backup target is created on the vSnap repository. However, Db2 can only handle a maximum of two log archive paths in parallel, provided there are no other archive log destinations in use (e.g. TSM). While there could be two SLA policies associated where applicable, it is highly recommended to stay limited to a single SLA policy per database when log backup is enabled.Otherwise, disabling log backup or disassociating SLA policies can lead to situations requiring manual intervention. See below for details.   
Workaround: When the log backup option is enabled for a distinct database, ensure that this database is only associated with a single SLA policy.
If two SLA policies have been associated nonetheless, you will encounter issues when either the log backup is disabled or when one of the SLA policies is disassociated. The result is the Db2 configuration parameters logarchmeth1/2 cannot be reset to its original values leading to the following error message:
"Log backup for database <DB name> is not disabled because otherwise the database will no more be configured for rollforward recovery.
 As a consequence, a restart of the Db2 database would be required."
If you encounter this situation, reset the logarchmeth1/2 parameters manually to its original settings or to LOGRETAIN.
Example: db2 UPDATE DB CFG USING logarchmeth1 LOGRETAIN logarchmeth2 OFF
Limitation: Since V10.1.2.
 

Restoring IBM Spectrum Protect Plus Db2 data to an alternative instance on the original host (internal reference #SPP-6709)
This issue is resolved in IBM Spectrum Protect Plus 10.1.4
Problem: When you are restoring a Db2 resource to an alternate location, the user interface allows you to select another instance on the original host that has a different name. When you select this instance as the target for the restore operation, the Db2 data on the original instance is compromised because all restore operations restore to the original instance name first.
Workaround: Avoid selecting target instances on the original host when using the restore to alternate instance option.
Limitation: Since V10.1.3.
 

Inventory fails for Db2 databases using non-ASCII characters in path or filenames (internal reference #SPP-5965)
Problem: Databases with non-ASCII characters in path or filenames (database paths, container paths, storage paths, log and mirror log paths) cannot be inventoried due to the following error:
Error: Command line '/usr/bin/python /tmp/tmpWzEDYB' has ended with exit code 1. stdout: ===SPPAgent-output===
stderr: File "/tmp/tmpWzEDYB", line 2 SyntaxError: Non-ASCII character '\xc7' in file /tmp/tmpWzEDYB on line 2, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details
Workaround: Ensure that all path and filenames of the database are built from ASCII characters only.
Limitation: Since V10.1.3.
 

Redirected restore operations to alternative locations, require path names to include the instance and database names  (internal reference #db2-175655)
Problem: When a database is restored to an alternate instance name and/or database name, the disk paths must include the instance name and the database name.
This detail is required so that the path names can be altered during the relocation procedure. The condition applies to all types of paths: database paths, container paths, storage paths, log and mirror log paths.
It is best to include both the instance name and the database name in all path names to enable the full set of restore capabilities, including restoring the same database to the same machine multiple times with different names and instances. If the path names do not include the instance name and database name, the following restrictions apply:

  1. If one or more of the path names includes the database name but not the database instance name.
    Restriction: In order to restore multiple copies of the database to a single target machine at the same time, each copy needs an individual database name assigned even when each restore operation targets another database instance.

  2. If one or more of the relevant path names includes the database instance name but not the database name.
    Restriction: In order to restore multiple copies of the database to a single target machine at the same time, each copy needs to be restored to a separate database instance even when an individual database name has been assigned to each copy.

  3. If one or more of the path names does not include either the database name or the database instance name.
    Restriction: Only a single copy of the database can be restored to a single target machine at the same time. Both database and instance name need to match the original names.

Workaround: Use a dedicated target machine for each restore.
Limitation: Since V10.1.3.
 

Redirected restore operations to alternative locations will change ownership and permissions for all database paths up to the root filesystem  (internal reference #db2, 179927)
Problem: When a database is restored to an alternate instance name and / or database name, all disk paths of the database will be altered to the new names during the relocation procedure that is performed on the target machine following the actual restore and recovery.
To ensure the database management system has access to the relocated paths, the ownership and permissions of the paths are also updated. This applies to the complete path chain up to but not including the root filesystem ("/"). Once the operation is completed, only the database instance user and other members of its group still have write access to the full chain of these paths. These conditions can lead to issues given that the top level directories of the altered paths are representing directories that other users need to have write access to, too.
The condition applies to all types of paths: database paths, container paths, storage paths, log and mirror log paths.
Workaround: Ensure that all database paths of the database are dedicated to the database the full chain up to the root filesystem so that exclusive write permissions is acceptable.
Limitation: Since V10.1.3.


 


MongoDB application server related

The backup job option Force full backup is not implemented in the MongoDB application agent. (internal reference #Mongo-179504)
Problem: The Spectrum Protect Plus GUI provides an option to force a full backup of a specified database. This option is available in the backup job definition options panel. The MongoDB application agent does not support this option in current implementation. You can select this option in the GUI and specify a database name but it will not be respect it. Only the initial backup for a database is a full backup and the subsequent backups are always incremental.
Problem Verification: There is an incremental backup created even though you have specified the correct database name in the Force full backup resources field. 
Workaround: There is no workaround for this limitation. Currently only incremental backups for MongoDB databases are possible.
Limitation: Since V10.1.3.


 


Exchange application server related

The granular restore remote package readme contains syntax error in a command (internal reference #SPP-exchange-1205)
Problem: In granular restore remote package README, the following command example misses the quotation, and fails with exception.

Set-Item WSMan:\localhost\Client\TrustedHosts -Value $remote_server_host_name,$app_server_host_name -Force

Problem Verification: Run the command provided from readme file, most of time, by copy and paste. The "Cannot convert 'System.Object[]' to the type 'System.String'" error is reported as following.

Set-Item : Cannot convert 'System.Object[]' to the type 'System.String' required by the parameter. Specified method is not supported.
At line:1 char:1
+ Set-Item WSMan:\localhost\Client\TrustedHosts -Value $remote_server_h ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Set-Item], InvalidOperationException
    + FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.PowerShell.Commands.SetItemCommand

Workaround: Enclose the -Value parameter with quotation mark as the following:

Set-Item WSMan:\localhost\Client\TrustedHosts -Value "$remote_server_host_name,$app_server_host_name" -Force

Limitation:  Since V10.1.3.
 


 

No error message to indicate that restore failed due to "out of space" (internal reference #Exchange-798)
Problem: During restore operations (Production Restore or Test Restore), if a out of space condition occurs IBM Spectrum Protect Plus with report a message like below:
Failed to restore databases (aaaa bbbbb) on server (someserver.cccc.ddddd.com).
The job logs will not report that a out of space condition occured.
Workaround:  Ensure you have adequate space, prior to a restore operation
Limitation:  Since V10.1.3.
 

Unsupported characters are displayed as '?' in MMC GUI mailbox restore browser (internal reference #SPP-6054)
Problem: If mailbox is created without specifying mailbox alias, Exchange server uses the value of 'DisplayName' parameter for the 'Alias' property value. If 'DisplayName' contains characters outside of unicode range from U+00A1 to U+00FF, then Alias will contain unsupported characters.
Exchange removes unsupported characters from 'Alias' by converting them to question marks. As a result, MMC GUI mailbox restore browser shows mailboxes with some characters displayed as '?' question marks.
Refer to Microsoft documentation: https://docs.microsoft.com/en-us/powershell/module/exchange/mailboxes/new-mailbox?view=exchange-ps for further details.
Workaround: When creating public folder mailbox or user mailbox, explicitly set mailbox alias value and use supported characters in mailbox alias.
Limitation:  Since V10.1.3. Permanent restriction, see APAR IT34558.
 

Exchange application server configured in a DAG environment failed to resolve cluster host (internal reference #SPP-6455)
Problem: When registering an exchange application server configured in a DAG environment with the IBM Spectrum Protect Plus Appliance it is recommended to register all Microsoft Exchange servers in the DAG. During the registration process (or if not all servers are registered) the discovery process will log warning messages as below:
"Failed to resolve cluster host xxxxxx to an application server"
The warnings will occur for each appplication server in the DAG that are not registered at the time that the discovery process is ran.
Workaround: Register all Microsoft Exchange servers in the DAG or you may ignore the warnings if you do not plan to use SPP to protect the the not registered Microsoft Exchange servers.
Limitation:  Since V10.1.3.
 

Exchange application server configured in a DAG environment job log contain warnings (internal reference #SPP-6539)
Problem: In a Microsoft Exchange DAG environment, during the application discovery process the job log will contain warning messages as seen below:
"Warning: No valid primary instance key for db group xxxxxx"
Workaround: Ignore the warning messages. No feature\function is affected
Limitation:  Since V10.1.3.
 

Readme file for installation procedure on remote server should be updated (internal reference #Exchange-806)
Problem: Granular Restore MMC GUI package must be manually installed on remote to Exchange 2016/2019 machine that has Microsoft Outlook installed. This is done per Microsoft recommendation to have Outlook installed on a different machine than Exchange 2016/2019 server. There is no Help information available on how to install Granular Restore package and how to configure it to connect to Exchange 2016/2019 server.
Problem Verification:
 -For Exchange 2019: Mailbox restore from MMC GUI Mailbox restore browser fails if Granular restore MMC GUI is not installed on the same machine as Microsoft Outlook and Outlook is not installed
on remote to Exchange server machine.
 - For Exchange 2016: Mailbox restore from MMC GUI Mailbox restore browser might fail if Granular restore MMC GUI is not installed on the same machine as Microsoft Outlook and Outlook is not installed
on remote to Exchange server machine.
Workaround: until the correct readme is packaged with the product, we provide here the correct readme:

  1. before you begin:
    To use the remote management features, you must install and enable Windows PowerShell 3.0, or later, on all IBM Spectrum Protect Plus protected Exchange servers and the server you will run the MMC GUI from. To download, install, and enable the software, follow the instructions in Microsoft Windows Management Framework 3.0 Downloads. The remote machine and Application Server must be in the same domain.

  2. Deploy the granular restore package to a remote server that has Microsoft Outlook installed
    These steps are only performed once. Once the granular restore package is installed you may continue to use it to perform later granular restore operations.

    1. Copy granular restore package from the Application Server to the remote server where you will manage the granular restore operation from.
      C:\Program Files\IBM\IBM Spectrum Protect Plus\tools\exchange\imr*TIV-TSMEXC-Win.exe
      * See HW/SW requirements for prerequisites for the remote server.

    2. On the remote server, run the following to install the package.
      a. Execute the self-extracting binary: C:\temp*TIV-TSMEXC-Win.exe, assuming you copied to the c:\temp directory.
      b. Run C:\temp*TIV-TSMEXC-Win\SetupFCM.exe to install MMC GUI
      c. Run C:*-TIV-TSMEXC-Win\fcm\x64\exc*\enu\spinstall.exe to install SP Exchange components

  3. Running the MMC GUI on the remote server to perform granular restore operations
    1. Run the MMC GUI application by executing C:\Program Files\Tivoli\FlashCopyManager\FlashCopyManager.exe
    2. Add the Application Server in MMC GUI:
    Click Actions > Manage Computers to open Manage Computers window. Click the plus-sign icon in Computers pane and enter Application Server name. Click Set Account icon and enter user credentials for the Application Server. Use the same credentials as used by Spectrum Protect Plus GUI -> Manage Protection > Applications > Exchange > Backup > Manage Application Servers > Add Application Server.
    3. Test connection to the Application Server: select Application Server node > Click Test Connection. Verify connection status "Connected successfully" is shown in Message column. Click OK to close Manage Computers window.

  4. Configure remote connection between the remote server and Application server

    1. Enable remote management for the MMC GUI deployed with IBM Spectrum Protect Plus entering the following Windows PowerShell command. Enable-PSRemoting -force.
      Depending on your environment you may need to add trusted hosts to the Exchange Server and server where the MMC GUI will be deployed.
      a. Add the Application Server and remote server to the trusted hosts list by entering the following command on each system: Set-Item WSMan:\locahost\Client\TrustedHosts -Value remote_server_host_name,app_server_host_name -Force where remote_server_host_name specifies the remote server.
      b. Restart the winrm service by entering the following command: Restart-Service winrm

    2. Enable the Windows PowerShell Remoting feature with Credential Security Support Provider (CredSSP) authentication. Complete the following steps:
      a. On the remote server, enter the following command to enable the Windows PowerShell Remoting feature with CredSSP: enable-wsmancredssp -role client -delegatecomputer app_server_host_name where app_server_host_name specifies the Application Server
      b. On the Application Server that will run the granular restore operation, enter the following command to enable the Windows PowerShell Remoting feature with CredSSP: enable-wsmancredssp -role server

    3. Verify that the Windows PowerShell Remoting feature is configured by using one of the following methods: - Use the "Test-WSMan" cmdlet to test whether the WinRM service is running on the remote computer.
      a. On the remote server, enter the following cmdlet to verify that the Windows PowerShell Remoting feature is configured correctly: Test-WSMan app_server_host_name where app_server_host_name specifies the Application Server.
      b. On the Application Server, enter the following cmdlet to verify that the Windows PowerShell Remoting feature is configured correctly: Test-WSMan remote_server_host_name where remote_server_host_name specifies the remote server.

[Optional] For additional remote configuration verification.

  • On the Application Server and remote server, to verify basic remote connection, enter the following cmdlet: invoke-command -computername remote_server_host_name -scriptblock {pwd} -Credential $creds where remote_server_host_name specifies the remote server.
    invoke-command -computername app_server_host_name -scriptblock {pwd} -Credential $creds where app_server_host_name specifies the Application Server.

  • On the Application Server and remote server, to verify (CredSSP) authentication is enabled, enter the following cmdlet: invoke-command -computername remote_server_host_name -scriptblock {pwd} -Credential $creds -Authentication Credssp where remote_server_host_name specifies the remote server.
    invoke-command -computername app_server_host_name -scriptblock {pwd} -Credential $creds -Authentication Credssp where app_server_host_name specifies the Application Server.

Continue with Step 11 from the granular restore topic under the Exchange Server section in the user guide to complete the granular restore operation.
Limitation: Since V10.1.3.


 


Limitations solved with V10.1.3 and V10.1.3_patch1

Upgrading to IBM Spectrum Protect Plus version 10.1.2 fails when upgrading from version 10.1.1 (internal reference #SPP-4699)
Problem: Upgrading to IBM Spectrum Protect Plus version 10.1.2 fails when upgrading from IBM Spectrum Protect Plus version 10.1.1 if the appliance is not manually rebooted.
Workaround: To upgrade to IBM Spectrum Protect Plus version 10.1.2 from version 10.1.1, you must apply the necessary ISO update files as described in the user documentation, then manually reboot the IBM Spectrum Protect Plus appliance.
Limitation: Since V10.1.2. Solved with V10.1.3.
 

Upgrading to IBM Spectrum Protect Plus version 10.1.2 fails if an emergency fix (efix) was applied to version 10.1.1 (internal reference #SPP-4750)
Problem: If an emergency fix (efix) was applied to IBM Spectrum Protect Plus version 10.1.1, the following error displays in the Administrative Console when upgrading to version 10.1.2: "Subscription Errors Encountered: Errors encountered while updating IBM Spectrum Protect Plus 500 - Internal Server Error".
This issue only applies if fixes in the .rpm format were installed directly on the IBM Spectrum Protect Plus virtual appliance using the yum or rpm command, and contain "efix" in the file name. Fixes that were applied through the Administrative Console are not impacted by this issue.
Workaround: To verify that an IBM Spectrum Protect Plus efix was installed in your 10.1.1 environment, enter the following command from the command-line interface of the IBM Spectrum Protect Plus version 10.1.1 virtual appliance:  rpm -qa | grep spp
If an efix is installed on the system, it will be displayed in the following format: spp-efix-10.1.1-xx.noarch. To uninstall the efix, enter the following command from the command-line interface of the IBM Spectrum Protect Plus version 10.1.1 virtual appliance:  rpm -e spp-efix
Once complete, perform the IBM Spectrum Protect Plus version 10.1.2 upgrade procedure.
Limitation: Since V10.1.2. Solved with V10.1.3.
 

Large vSnap replication operations taking longer than 24 hours time out and abort (internal reference #SPPSUP-367)
Problem: By default, a vSnap replication operation aborts if the session does not complete within 24 hours. In cases where a large amount of backup data is being replicated between vSnap servers, a replication operation could be aborted before the operation is completed. Data that is transferred before the timeout threshold is met is saved.
Workaround: Increase the replication timeout threshold to a value larger than 24 hours. The parameter is measured in seconds; by default, the value is set to 86,400 seconds, or 24 hours. Increase the value to 48 hours (172,800 seconds) by entering the following command in the command-line interface of the primary vSnap server that is the source of the replication:
vsnap system pref set --name replTransferTimeout --value 172800
The parameter takes effect when the next replication operation starts.
Limitation: Since V10.1.2. Solved with V10.1.3, see APAR IT26536

 

After a Catalog restore, jobs that were utilizing local vSnap fail (internal reference #SPP-1000)
Problem: When a Catalog is restored from a backup, jobs that were utilizing local vSnap storage will fail on the recovered IBM Spectrum Protect Plus appliance with the following error:
“vSnap Storage Volume not found”.
Workaround: A Catalog backup does not include local vSnap pools or volumes. Only the Catalog itself is backed up and will be restored to the same or new IBM Spectrum Protect Plus appliance. External vSnap servers can be re-registered to the new IBM Spectrum Protect Plus appliance, so it is recommended to use external vSnap servers for backup operations.
Limitation: Since V10.1.1. Solved with V10.1.3.
 

During a VMware File Restore of a large file in a Linux environment, the restore may fail with a timeout error (internal reference #SPP-1274)
Problem: In a Linux environment, performing a VMware-based file restore on files larger than 2 GB may fail with the following error:
"Timed out (300 seconds) waiting for command to complete."
In some cases, larger file restores complete successfully, however the chances of failure increase for files larger than 2 GB.
Workaround: A hot fix will be provided to increase the timeout threshold to accommodate larger files.
Limitation: Since V10.1.1. Solved with V10.1.3.
 

Expired jobs remain on the Catalog Retention pane after removal(internal reference #SPPL3-775, #SPP-1734)
Problem: A job session can remain on the Catalog Retention pane after the recovery point has been expired and removed through the Maintenance job.
Workaround: None.
Limitation: Since V10.1.1. Solved with V10.1.3.
 

Virtual machines deleted from a Hyper-V or VMware server continue to be displayed as backup sources (internal reference #ECC-11836)
Problem: If a virtual machine is deleted from a Hyper-V or VMware server after an Inventory job completes, the VM continues to be displayed as a backup source in IBM Spectrum Protect Plus after the Inventory job runs again. This scenario occurs if the Inventory job of one or multiple servers that are part of the job does not complete successfully, which in turn does not trigger a cleanup job.
Workaround: None.
Limitation: Since V10.1.0. Solved with V10.1.3.

Backup jobs can save only virtual machines selected within a single page(internal reference #ECC-10924)
Problem: Backup jobs can save only virtual machines selected on a single page. The virtual machines selected on further pages are not saved.
Workaround: None.
Limitation: Since V10.1.0. Solved with V10.1.3.
 

The Maintenance job cannot be rescheduled (internal reference #ECC-11937)
Problem: The Maintenance job, which removes resources and associated objects created by IBM Spectrum Protect Plus when a job in a pending state is deleted, cannot be rescheduled.
Workaround: Ensure that scheduled jobs do not run at the same time as the Maintenance job.
Limitation: Since V10.1.0. Solved with V10.1.3.
 

Ability to edit Backup Storage is disabled if IBM Spectrum Protect Plus fails to authenticate with vSnap server (internal reference #ECC-12118)
Problem: If IBM Spectrum Protect Plus fails to authenticate with a vSnap server (that is, if the vSnap user's password is changed, access is revoked, or if the associated user with access to the vSnap server is deleted) the server will appear in the Backup Storage list with its status listed as "Not Connected". However, the ability to edit the Backup Storage registration will be disabled.
Workaround: In the case of a user being deleted or having their access revoked, edit the Backup Storage registration in IBM Spectrum Protect Plus and specify the new credentials before deleting the original user or revoking access.
Limitation: Since V10.1.0. Solved with V10.1.3.

Backup and offload of a virtual machine template fails(internal reference #ECC-12337)
Problem: A backup of a virtual machine template fails with the following error:
“Full VM backup of VMware Virtual Machine ‘<template_name>’ failed with RC=4379”
Workaround: To enable backup and offloading of virtual machine templates, you must specify VMENABLETEMPLATEBACKUPS in the data mover option file. Note that a backup of a template can only be performed as a Full backup. For more information about configuring your environment for backing up virtual machine templates, see https://www.ibm.com/support/knowledgecenter/en/SSEQVQ_8.1.2/client/r_opt_vmenabletemplatebkup.html.
Limitation: Since V10.1.0. Solved with V10.1.3.

A file restore in a Linux environment might use the wrong source if guest network settings were not configured correctly (internal reference #SPPL3-285)
Problem: When backing up a Linux virtual machine with the file indexing option enabled, if the guest operating system has a fully qualified domain name, it must be resolvable from the guest. If the resolution fails, the file index might be associated with the wrong source virtual machine. Subsequent file restores may lead to files being restored (or attempted to be restored) from the wrong backup.
Workaround: If the Linux virtual machine being backed up has a fully qualified domain name, run the commands "hostname" and "hostname --fqdn" inside the guest OS and verify that both commands return valid output. If there are resolution errors, update the Linux network settings either by specifying the correct DNS information or by adding appropriate entries in the /etc/hosts file. Note that each virtual machine must have a unique host name.
Limitation: Since V10.1.0. Solved with V10.1.3.

A Hyper-V Linux VM fails file indexing (internal reference #ECC-11708)
Problem: A Hyper-V Linux VM fails file indexing with the following error:
"Could not establish an SSH session with server on host(null) at port(22). Error (host must not be null)"
Workaround: A guest should use a specific kernel for Ubuntu Linux. For more information, see https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/Supported-Ubuntu-virtual-machines-on-Hyper-V?f=255&MSPPError=-2147217396.
Limitation: Since V10.1.0. Solved with V10.1.3.
 

SQL Restore jobs cannot be canceled (internal reference #SPP-2471)
Problem: When a SQL Restore job is in progress and the user clicks Cancel, data and log files will continue to be restored. Canceling a SQL Restore job through the IBM Spectrum Protect plus interface is not supported.
Workaround: None.
Limitation: Since V10.1.1_patch1. Solved with V10.1.3.

If an Exchange server is running on a SQL server, Inventory jobs associated with the SQL server fail (internal reference #SPPL3-804)
Problem: Running an Inventory job on a SQL resource in IBM Spectrum Protect Plus fails if an Exchange server is running on the same machine.
Workaround: None.
Limitation: Since V10.1.1. Solved with V10.1.3.

A SQL database backup with log backup enabled fails when performed against a restored SQL database with an underscore in its name (internal reference #SPPL3-806)
Problem: When an SLA policy with log backup enabled is created for a database that was restored through IBM Spectrum Protect Plus, and the database has an underscore in its name, the backup fails.
Workaround: If the restored database must have log backup enabled in future backup jobs, ensure the name of the database does not include an underscore.
Limitation: Since V10.1.1. Solved with V10.1.3.

Oracle 12c multi-threaded configurations
Problem: Oracle 12c multi-threaded configurations are not supported in IBM Spectrum Protect Plus.
Limitation: Since V10.1.1. Solved with V10.1.3.
 

Restores to an alternate instance are restricted to a single copy per source machine and database instance combination (internal reference #SPP-db2-168387)
Problem: When a database is restored to an alternate instance, a database instance with the same name as the original database instance must exist on the target machine. Even if you are changing the database or instance name where the target database is located, the data is first restored with its original name and its original instance name before it is relocated to the final destination with its new name. The actual data is not moved so when the restore operation completes successfully, the alternative instance is always linked to the original instance. When you run another restore operation of the same database or instance to the same target machine, the process overwrites the previously restored data.
Workaround: To avoid issues when you are restoring to an alternate instance, use multiple target machines for each copy you want to create from the original database.
Limitation: Since V10.1.2. Solved with V10.1.3.
 

Restores to an alternate instance are restricted to a single copy per source machine and database instance combination (internal reference #SPP-db2-168387)
Problem: When a database is restored to an alternate instance, a database instance with the same name as the original database instance must exist on the target machine. Even if you are changing the database or instance name where the target database is located, the data is first restored with its original name and its original instance name before it is relocated to the final destination with its new name. The actual data is not moved so when the restore operation completes successfully, the alternative instance is always linked to the original instance. When you run another restore operation of the same database or instance to the same target machine, the process overwrites the previously restored data.
Workaround: To avoid issues when you are restoring to an alternate instance, use multiple target machines for each copy you want to create from the original database.
Limitation: Since V10.1.2. Solved with V10.1.3.

Backup Speed value reported in VM Backup History report does not match the one reported in job log. (internal reference #SPP-6156)
Problem: Customer runs VM Backup History report and looks at “Backup Speed” value which is found different than what’s reported in job log for that backup job instance. Backup calculation of throughput assumes 1KB = 1024 Bytes differs from reports’ assumption that 1KB = 1000 bytes.
Workaround: None.
Limitation: Since V10.1.3. Solved with V10.1.3_patch1, see APAR IT28093.
 

Cloud catalog restore points are not displayed if they are from an IBM Spectrum Protect server. (internal reference #SPP-6893)
Problem: The IBM Spectrum Protect Plus server cannot enumerate the recovery points of the catalog that are offloaded to an IBM Spectrum Protect server.
Workaround: None.
Limitation: Since V10.1.3. Solved with V10.1.3_patch1, see APAR IT28124.
 

Protected and unprotected VMs report failing to report unprotected VMs.   (internal reference #SPP-6913)
Problem: On setups with several hundreds of unprotected VMs, Protected and Unprotected VMs report shows errors at the very bottom of the report fails to report any VMs under the Unprotected VMs table.
Workaround: None.
Limitation: Since V10.1.3. Solved with V10.1.3_patch1, see APAR IT28094
 

vSnap is not cleaned up after object expiration  (internal reference #SPP-6855)
Problem: Some vSnap volume/snapshots are not purged after expiration or SLA deletion.
Workaround: None.
Limitation: Since V10.1.3. Solved with V10.1.3_patch1
 

Hyper-V Restore Advanced Options not getting replayed. (internal reference #SPP-7166)
Problem: After setting up a Hyper-V Restore Job and saving it with the desired Advanced Options selected, the option selections are not preserved when editing the Restore Jobs.
Workaround: Make your option selections again before rerunning the restore jobs for Hyper-V.
Limitation: Since V10.1.3. Solved with V10.1.3_patch1, see APAR IT28009.
 


Limitations solved with V10.1.2

VMware backups through a VADP Proxy utilizing NBDSSL and LIBZ compression fails (internal reference #SPP-2634)
Problem: When performing a VMware Backup through a VADP Proxy, selecting the NBDSSL transport mode with LIBZ compression enabled might cause the backup to fail.
Workaround: This issue only affects LIBZ compression under certain conditions. Select a different compression type, or disable compression for the NBDSSL transport mode.
Limitation: Since V10.1.1_patch1. Solved with V10.1.2.

The Provide Feedback pop-up window displays in environments without an internet connection (internal reference #SPP-1156)
Problem: The Provide Feedback pop-up window displays after a period of time when using IBM Spectrum Protect Plus. The feedback form requires an internet connection to capture feedback, but the pop-up window will display if no internet connection is available.
Workaround: To provide feedback, use the feedback form on a machine with internet access.
Limitation: Since V10.1.1. Solved with V10.1.2.
 

File restores might fail if another operation is occurring on the same virtual machine during the time of the attempted file restore (internal reference #SPPL3-113)
Problem: File restores might fail if another operation, such as a scheduled backup, is occurring on the same virtual machine during the time of the attempted file restore. A similar issue might occur if you are attempting to run multiple file restore jobs simultaneously.
Workaround: Ensure that no other operations are occurring on a virtual machine while restoring a file from the same virtual machine.
Limitation: Since V10.1.0. Solved with V10.1.2.
 

Transaction logs are not purged from SQL Server in SQL Always On environments (internal reference #SPP-3190)
Problem: When SQL backup jobs successfully complete with log backups enabled, all transaction logs up to the point of the job completing are automatically purged from the SQL server. In SQL Always On environments, the logs are not automatically purged.
Workaround: Transaction logs older than 1 day should be manually deleted from the log target volume in SQL Always On environments.
Limitation: Since V10.1.1_patch1. Solved with V10.1.2.
 

SQL Always On Availability Group backup jobs display error messages about disabling log backups of associated Availability Groups (internal reference #SPP-3191)
Problem: If a standalone SQL database and a database that is part of a SQL Always On Availability Group are protected through the same SLA policy, and  the databases are located on the same server, the following error message displays during incremental backup jobs:
"Disabling log backup failed on instance:<SQL INSTANCE> e=...xsb.commons.XSBException".
Workaround: Create separate SLA policies for standalone SQL databases and databases that are part of SQL Always On Availability Groups.
Limitation: Since V10.1.1_patch1. Solved with V10.1.2.
 

SQL servers display on the Oracle Manage Application pane (internal reference #SPP-1088)
Problem: If a pair of nodes that are part of a failover cluster are registered in IBM Spectrum Protect Plus, the inactive node will display on all application screens, including differing application database types.
Workaround: None.
Limitation: Since V10.1.1. Solved with V10.1.2.
 

When an SLA Policy is deleted, some artifacts are not removed from the SQL server internal reference #SPPL3-721)
Problem: In some conditions, when an SLA Policy is deleted and the Maintenance job is run, some artifacts such as log backups associated with the deleted SLA Policy are not removed from the SQL server. If a new SLA Policy is created and assigned to the same database, future log backups fail because they are still associated with the deleted SLA Policy.
Workaround: If artifacts are not removed through a Maintenance job after an SLA Policy is deleted, manually delete the artifacts, then re-assign the database to a new SLA Policy.
Limitation: Since V10.1.1. Solved with V10.1.2.
 

An entry in /etc/oratab is not created after a successful Oracle database restore (internal reference # SPP-836)
Problem: After successfully restoring an Oracle database, IBM Spectrum Protect Plus does not automatically create an entry in /etc/oratab for the restored database.
Workaround: An entry in /etc/oratab must be manually created if desired.
Limitation: Since V10.1.1. Solved with V10.1.2.
 

Backup of Hyper-V virtual machines that are on NTFS and CSVFS file systems fail with a target volume error (internal reference #SPP-1165)
Problem: If a job definition is created that includes Hyper-V virtual machines that utilize both NTFS and CSVFS formatted drives, the job will fail with an error indicating that the mountpoint is inaccessible.
Workaround: Ensure Hyper-V backup jobs do not include drives that utilize both NTFS and CSVFS formats.
Limitation: Since V10.1.1. Solved with V10.1.2.
 


 


Limitations solved with V10.1.1 and V10.1.1_patch1

Virtual machine backup jobs fail after performing a Catalog Restore (internal reference #SPPL3-724)
Problem: After restoring the catalog through a Catalog Restore job, certain virtual machine backup jobs fail.
Workaround: For releases prior to the patch1, the workaround is to create new SLA policies for each backup job that fails following a Catalog Restore. This procedure is only required for failed jobs; backup jobs that complete successfully following a Catalog Restore do not need to be associated with new SLA policies.
Limitation: Since V10.1.1. Solved with V10.1.1_patch1.
 

When updating IBM Spectrum Protect Plus using Firefox, the Clean Process appears to fail (internal reference #SPPL3-833)
Problem: When updating IBM Spectrum Protect Plus through the Administrative Console using Firefox, a Clean Process Failure message displays during the update process. The message indicates that the update has been applied successfully, but the update cleanup process failed.
Workaround: This message appears consistently when performing an update to IBM Spectrum Protect Plus with Firefox, regardless of whether the Clean Process failed or was successful. This behavior is specific to Firefox only.
Limitation: Since V10.1.1. Solved with V10.1.1_patch1.
 

The predefined Self Service role can create and run jobs (internal reference #SPP-1160)
Problem: The Self Service role allows a user to monitor existing backup and restore operations delegated by an Administrator. Though only the View permission is assigned to the appropriate resources, a Self Service user can also create and run jobs.
Workaround: For releases prior to the patch1, the workaround is to create a custom role that assigns the View permission to SLA Policy, Backup Storage, Job, Report, and necessary hypervisor or application resources.
Limitation: Since V10.1.1. Solved with V10.1.1_patch1.
 

Backup and restore operations for SQL Server system databases are not supported (internal reference #SPP-1332)
Problem: Backup and restore operations for SQL Server system databases such as the primary database are not supported in IBM Spectrum Protect Plus 10.1.1. 
Workaround: For releases prior to the patch1, SQL Server system databases can be backed up to vSnap and restored by using the Instant Access restore type.
Limitation: Since V10.1.1. Solved with V10.1.1_patch1
 

SQL incremental backup jobs perform a base backup despite the first incremental backup job reporting that write range tracking is enabled (internal reference #SPP-1246)
Problem: On systems where the source volume is less than 1 GB, the Update Sequence Number (USN) size may cause the backup to continually run as a base backup. The USN change journal provides write range tracking for a volume when the file size is increased to a specific threshold.
Workaround: For releases prior to the patch1, resize the source volume to be larger than 1 GB to enable incremental backups.
Limitation: Since V10.1.1. Solved with V10.1.1_patch1.
 

A SQL restore of data/log files that are in the same path to an alternate location restores to the data file location (internal reference #SPP-970)
Problem: If the source database’s data and log files are located in the same directory, a SQL restore of data and log files to an alternate location restores the files to the data file location.
Workaround: For releases prior to the patch1, if the source data and logs are stored in a single location, then the source data and logs must be restored to the same single location.
Limitation: Since V10.1.1. Solved with V10.1.1_patch1.

A database or point-in-time restore of a SQL Failover Cluster Instance fails with a writer error (internal reference #SPP-1270)
Problem: A database or point-in-time restore of a SQL Failover Cluster fails with the following error:
"Writer [SQLServerWriter] report error status ([VSS_WSS_FAILED_AT_PRE_RESTORE])"
Workaround: For releases prior to the patch1, when the automount option is disabled on a SQL Failover Cluster Instance restore target destination, the "Available Storage" group must be on the same owner node as the target SQL cluster instance during restore.
Limitation: Since V10.1.1. Solved with V10.1.1_patch1

Backups fail when selecting sources at the datastore cluster level (internal reference #ECC-12266)
Problem: When creating a backup job definition, the IBM Spectrum Protect Plus interface supports selecting sources to back up at the datastore cluster level; however, the backups will fail when selected at this level. The following error displays:
"Failed to find virtual machine under path: <path>. There are no virtual machines to backup."
Workaround: The workaround is to select datastores under the cluster level.
Limitation:  Since V10.1.0. Solved with V10.1.1.
 

vSnap servers remain on the Backup Storage page after deletion (internal reference #ECC-12307)
Problem: After deleting a primary or secondary vSnap server through the Backup Storage page, the server remains in the list of available servers.
Workaround: Navigate to a different page in the user interface, then return to the Backup Storage page. The deleted vSnap server is removed from the list.
Limitation:  Since V10.1.0. Solved with V10.1.1.
 

The IBM Spectrum Protect Plus appliance time zone must be set through a command line interface (internal reference #ECC-12434),
Problem: The IBM Spectrum Protect Plus appliance time zone cannot be set through the user interface or Administrative Console. An incorrect time zone might impact job scheduling. Set the time zone through the appliance’s command line interface.
Workaround: To set the time zone, log in to the appliance as root and enter the following command: "ls -l /etc/localtime".
Make a backup of the existing localtime file by entering the following command: "sudo mv /etc/localtime /etc/localtime.bak".
Create a link (here, America/Chicago is used as an example) through the following command: "sudo ln -s /usr/share/zoneinfo/America/Chicago /etc/localtime".
Execute "ls -l /etc/localtime" to see the time zone change.
Restart Virgo through the following command: "service virgo restart".
Limitation: Since V10.1.0_patch1. Solved with V10.1.1.
 

For VMware backups, HotAdd Transport mode is not supported (internal reference #ECC-11021)
Problem: The VMware HotAdd Transport feature is not supported in IBM Spectrum Protect Plus operations.
Workaround: None.
Limitation: Since V10.1.0. Solved with V10.1.1.
 

A Hyper-V restore using the Production restore type does not preserve the path of the original volume (internal reference #SPPL3-190)
Problem: When restoring a Hyper-V virtual machine to the original host using the Production restore type, the directory path is not preserved on the original volume.
Workaround: None.
Limitation: Since V10.1.0_patch1. Solved with V10.1.1.


 


Limitations solved with V10.1.0_patch1

If the automount parameter is not enabled on Hyper-V hosts, backups might fail (internal reference #SPPL3-207)
Problem: If the automount parameter is not enabled on a Hyper-V host, backups might fail with the following errors:
Unprotected vm: XXXXX [Destination volume creation failed for soure volume C]
Unprotected vm: YYYYY [Failed to format volume. Disk: 39, partition: 2]
Workaround: For releases prior to the IBM Spectrum Protect Plus 10.1.0_patch1, you must enable the DiskPart automount parameter on Hyper-V hosts. For more information about enabling the automount parameter, see https://technet.microsoft.com/en-us/library/cc753703(v=ws.11).aspx.
Limitation: Since V10.1.0. Solved with V10.1.0_patch1.
 

SQL log truncation might fail for Windows virtual machines running on a Hyper-V server (internal reference #SPPL3-238)
Problem: Log truncation might fail for a backup job which has the SQL log truncation option selected. This impacts Windows Virtual Machines on Hyper-V. The backup task completes successfully, but when SQL log truncation is attempted, the log returns the following message:
"Truncating application logs of vm <vm_name>”.
The job then ends abruptly with a "failed" status. The message "Successfully truncated logs for <vm_name>” does not appear.
Workaround: For releases prior to the IBM Spectrum Protect Plus 10.1.0_patch1, this issue does not affect the recoverability of the VM, only the truncation of SQL logs. As a result, the logs keep growing, and out-of-space issues might ensue. Therefore, if you encounter this issue, the workaround is to perform a SQL log truncation independently. For more information see https://technet.microsoft.com/en-us/library/ms189085(v=sql.105).aspx.
Limitation: Since V10.1.0. Solved with V10.1.0_patch1.
 

A VM protection job with file-level indexing completes with the following message: “Cataloging task for search in 0 seconds. Files Indexed : 0 , Files Skipped : 0” (internal reference #SPPL3-224)
Problem: A Windows VM protection job with file-level indexing completes with the following message:
“Cataloging task for search in 0 seconds. Files Indexed : 0 , Files Skipped : 0”.
But the job log indicates that files were found via file discovery. Consequently, the files for this virtual machine are not available for search and recovery. This issue does not impact Linux virtual machines.
Workaround: None.
Limitation: Since V10.1.0. Solved with V10.1.0_patch1.
 

A file restore in a Linux environment fails if the file name or path to the file contains spaces (internal reference #SPPL3-264)
Problem: When performing a file restore in a Linux environment, the file restore fails if the file name or path to the file contain spaces.
Workaround: For releases prior to the IBM Spectrum Protect Plus 10.1.0_patch1, a file can be restored from a higher-level directory that does not contain spaces. For example, restoring a file from the “path” directory in the following example would be successful: /path/a path/file name.txt. Note that the file must be restored to an alternate location in this instance, then copied to the desired location. Alternatively, remove spaces from the file name or path to the file, back up the associated virtual machine, then run the file restore again.
Limitation: Since V10.1.0. Solved with V10.1.0_patch1.
 

Attempts to access the Administrative Console on port 8090 fail (internal reference #SPPL3-263/252)
Problem: A user is unable to access the IBM Spectrum Protect Plus Administrative Console through port 8090 after installation.
Workaround: For releases prior to the IBM Spectrum Protect Plus 10.1.0_patch1, the workaround is to first log in to the IBM Spectrum Protect appliance as a root user and execute the following command: systemctl start adminconsole.
Once complete, reboot the appliance.
Limitation: Since V10.1.0. Solved with V10.1.0_patch1.
 

Virtual machines support only one offload job type at a time (internal reference #ECC-12346)
Problem: A virtual machine can support only one type of offload job (that is, vSnap offload or direct offload). If a virtual machine is a part of two different offload types, the job that runs last will remove the previous recovery points from IBM Spectrum Protect Plus.
Workaround: For releases prior to the IBM Spectrum Protect Plus 10.1.0_patch1, ensure virtual machines are assigned to one offload job type, either vSnap offload or direct offload.
Limitation: Since V10.1.0. Solved with V10.1.0_patch1.
 

UUIDs remain the same after a Test/Clone mode restore (internal reference #SPPL3-270)
Problem: When restoring a virtual machine through a Test/Clone mode restore, the UUID of the cloned virtual machine remains the same as the UUID of the source virtual machine. The lack of a unique UUID introduces issues when attempting to perform file cataloging.
Workaround:
For releases prior to the IBM Spectrum Protect Plus 10.1.0_patch1, there are several workarounds for this issue as described in the following VMware article:https://kb.vmware.com/s/article/2006865.

  • Migrate the cloned virtual machine to a different vCenter ESX host.
  • Change the UUID of the cloned virtual machine by logging in to the ESX host where the cloned virtual machine resides and entering the following command: vmkfstools -J setuuid <vmname>.vmdk
  • Create a vSphere clone of the virtual machine clone created through IBM Spectrum Protect Plus. Once complete, the VM Guest OS will boot up with a unique UUID, and the virtual machine clone created through IBM Spectrum Protect Plus can be deleted.

Limitation: Since V10.1.0. Solved with V10.1.0_patch1.

 

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSNQFQ","label":"IBM Spectrum Protect Plus"},"Component":"Not Applicable","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"10.1.3","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
01 July 2021

UID

ibm10843068

Page Feedback