IBM Support

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

Preventive Service Planning


Abstract

This document details the known Issues & limitations for IBM Spectrum Protect Plus V10.1.8 and later patches.

Content

This document is divided in to 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

IBM Spectrum Protect Plus navigation pane overlaps the main pane. (internal reference #SPP-16099)
Problem: IBM Spectrum Protect Plus navigation pane has different behaviors depending on the size of the browser window. For smaller browser sizes, the behavior of the navigation pane is to overlap the main pane. For larger browser sizes, the behavior of the navigation pane is to expand pushing the main pane.
Workaround: IBM Spectrum Protect Plus user interface provides a collapse and expand button for the navigation pane.
Limitation: Since 10.1.6.
 

Unassigned SLA Policy is not deleted when last resource is unassociated. (internal reference #SPP-15719)
Problem: If IBM Spectrum Protect Plus detects that there are no resources associated with an SLA, then attempts to delete the corresponding job. There are certain conditions that might prevent the deletion of the job resulting in a job with no resources associated. This case job run and completed in Partial status.
Problem Verification: Job completes in Partial status due to no resources associated.
Workaround: Using the IBM Spectrum Protect Plus schedule tab of the Jobs and Operations screen, place the job into Held state to prevent job execution.
Limitation: Since 10.1.6.
 

VMs hidden in the GUI due to permission settings aren't properly hidden in API responses (internal reference #SPP-14334)
Problem: Hidden VMs, based on assigned permissions, are returned by API calls, and by extension of that show up in IBM Spectrum Protect Plus reports.
Workaround: None.
Limitation: Since V10.1.5.
 

Available Software updates button remains active after the user selects and starts the update process. (internal reference #SPP-10088)
Problem: When the user logs in to the administrative console, the update remains active and clickable even when the update is already in process. If clicked can interfere with the ongoing update process.
Workaround: Do not click the button again until the update process fully completes.
Limitation: Since 10.1.5.
 

"Offload" terminology appears after you upgrade from IBM Spectrum Protect Plus V10.1.4 to V10.1.5 (internal reference #SPP-10526)
Problem: IBM Spectrum Protect Plus underwent a terminology change in V10.1.5 where the word "offload" was changed to "copy." When you upgrade from an IBM Spectrum Protect Plus V10.1.4 appliance to version 10.1.5, the incorrect term "offload" appears in the Start Job Options drop down menu.
Since this issue is related to the old data in catalog, this problem can happen if customer had data before V10.1.5. Any new installation from V10.1.5 and later does not encounter this problem.
Workaround: None.
Limitation:  Since V10.1.5. Permanent restriction, see APAR IT35104.
 

Restore type cannot be selected in the restore wizard in IBM Spectrum Protect Plus when you use Firefox 60.9.0esr (64 Bit) on Windows (internal reference #SPP-10211)
Problem: When you use Mozilla Firefox 60.9.0esr (64 Bit) on Microsoft Windows, the restore type cannot be selected in the restore wizard for IBM Spectrum Protect Plus.  Previous and more recent versions of Mozilla Firefox do not exhibit this behavior.
Workaround: Use a more recent version of Mozilla Firefox or another supported web-browser.
Limitation:  Since V10.1.5. Permanent restriction for Mozilla Firefox 60.9.0esr (64 Bit) browsers on Microsoft Windows. Solved with browsers later than Mozilla Firefox 60.9.0esr (64 Bit) on Microsoft Windows.
 

Older product upgrades might prevent online options for recent versions (internal reference #SPP-16277)
Problem: Online update does not display options to select for 10.1.6 and newer releases
Problem Verification: The IBM Spectrum Protect Plus appliance file /etc/yum/vars/spp_version contains V10.1.4. Or you offline upgrade IBM Spectrum Protect Plus from version older than 10.1.6 and now attempt online upgrade and do not see any buttons for newer GA releases.
Workaround: Upgrade offline to IBM Spectrum Protect Plus V10.1.8
Limitation: since V10.1.4.
 

SQL and Exchange log backups fail due to vSnap with multiple network interface cards (NICs) (internal reference #SPPSUP-1253)
Problem: IBM Spectrum Protect Plus mail fail during Exchange and SQL log backups if the backup destination is a vSnap server that has multiple network interface cards (NICs) configured.
Workaround: To resolve this issue, the server message block (SMB) service needs to be disabled on the NICs on which Exchange or SQL server has no connection by issuing the following command on the vSnap server:

$ sudo vSnap network update –id --services “mgmt,repl,nfs,iscsi”

Reattempt the failed backup job.
Limitation:  Since V10.1.4.
 

Jobs cannot be saved when you schedule a report with a frequency less than 5 minutes when you use Microsoft Edge (internal reference #SPP-9353)
Problem: By default, a warning message displays in IBM Spectrum Protect Plus when you attempt to schedule a report with a frequency that is less than 5 minutes. However, when you define 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 you create schedules.
Limitation: Since V10.1.4. Solved with Microsoft Edge 41 or Microsoft EdgeHTML 16.16299 and later. Permanent restriction for earlier Microsoft Edge and Microsoft EdgeHTML browsers.
 

In IBM Spectrum Protect Plus, after you upgrade to V10.1.4 and attempting to log in, the user might receive the message: Username has expired and must be changed (internal reference #SPP-9339 & SPP-6327)
Problem:  When you upgrade to IBM Spectrum Protect Plus V10.1.4, the browser might attempt to reuse previously cached credentials.  Upon the first login for V10.1.4, the user might receive the message

Username has expired and must be changed.

Workaround:  After upgrade to IBM Spectrum Protect Plus V10.1.4 and before you log in for the first time, clear the browser cache.  For Chrome, Edge, or Firefox, press SHIFT+CTRL+DELETE to open the appropriate screen for clearing the browser cache.
Limitation:  Since V10.1.4. Permanent restriction, see IT35014.
 

Pointing an IBM Spectrum Protect Plus to another IBM Spectrum Protect object client node without unregistering and reregeristing the IBM Spectrum Protect endpoint can produce errors when you run backup jobs (internal reference #SPP-8747)
Problem: In IBM Spectrum Protect Plus, when a IBM Spectrum Protect (SP) server is registered, it is recognized based on hostname and port as a unique endpoint, and the credentials are associated with that endpoint. If a new object client node is created on the same IBM Spectrum Protect server, and the credentials previously registered in IBM Spectrum Protect Plus are updated to point to the new node, then IBM Spectrum Protect Plus does not recognize that the object client node changes. IBM Spectrum Protect Plus continues to treat it as the same endpoint as before. As a result, IBM Spectrum Protect Plus might try to refer to data that existed in the older node that is no longer present in the new node.
Workaround:  When a IBM Spectrum Protect repository server is registered in IBM Spectrum Protect Plus by using a particular object client node, the registration cannot be updated to point to another node. If the access key or secret key registered into IBM Spectrum Protect Plus are updated, the new keys must continue to be associated with the same node as before. To stop by using the existing node and start by using another node on the same IBM Spectrum Protect Plus server, remove any SLAs that point to the repository server and then unregister the repository server from IBM Spectrum Protect Plus.  Next, reregister the repository server by using the keys associated with the new node and re-create the necessary SLAs to point to the new server.
Limitation:  Since V10.1.4. Permanent restriction, see IT36650.
 

vSnap server shows high CPU usage even when no jobs are active (internal reference #SPP-16253)
Problem: vSnap servers can experience a spike in CPU usage at certain times of the day even though no jobs are actively running in IBM Spectrum Protect Plus. The problem occurs if one or more SLAs are configured to copy data to an IBM Cloud Object Storage (COS) vault that has WORM retention enabled and if the vSnap server has a large backlog of cloud objects that are pending for expiration.
Problem Verification: The queue can be seen by using command:

vsnap cloud maint show

If there are hundreds of pending sessions in the list, the vSnap server can show heavy CPU usage at certain times of the day as it gradually works through the expiration queue in the background.
Workaround: None.
Limitation:  Since V10.1.3
 

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 is no longer backed up.
Workaround: After a folder is moved and its new location is logged by the Inventory job, reassociate the folder with the SLA policy and reassign the backup options.
Limitation:  Since V10.1.2. Permanent restriction, see IT34947.
 

The IBM Spectrum Protect Plus Administrator Console list of time zones is not translated to reflect local language selection (internal reference #SPP-7982 & SPP-8631)
Problem: If a user (administrator) of the IBM Spectrum Protect Plus enters the Admin Console and attempts to set the time zone, the list of time zones presented in the menu is not translated and not reflect that user's local language choice.  The time zone is not translated because it uses the timedatectl utility on the appliance to obtain this information.
Workaround: None.
Limitation:  Since V10.1.4. Permanent restriction, see APAR IT35013.
 

IBM Spectrum Protect Plus uses third-party libraries that might not reflect language selection (internal reference #SPP-8301 & SPP-8633 & SPP-8517)
Problem: The IBM Spectrum Protect Plus product uses third-party libraries that might not reflect the user’s local language selection.  Therefore, errors or exceptions from these libraries might not adhere to the language selection.
Workaround: None.
Limitation: Since V10.1.4. Permanent restriction, see APAR IT34544.
 

The IBM Spectrum Protect Plus Administrator Console doesn’t display the time and date in cultural format (internal reference #SPP-7984 & SPP-8632)
Problem: If a user (administrator) of the IBM Spectrum Protect Plus enters the Admin Console and that user has the web-browser configured to use a region setting other than the United States region setting, the time and date might not be displayed in the proper cultural format. The time and date uses the timedatectl utility on the appliance to obtain this information.
Workaround: None.
Limitation: Since V10.1.4. Permanent restriction, see APAR IT34545.

When a report is downloaded to PDF format, some non-English-language characters might not be displayed properly (internal reference #SPP-1634)
Problem: IBM Spectrum Protect Plus provides a mechanism whereby job history can be downloaded in PDF format.  If elements in the report contain non-English-language characters, it might be the case that these strings are not displayed in the PDF correctly.  This behavior occurs due to the version of a third-party framework that is used by IBM Spectrum Protect Plus for PDF rendering.
Workaround: None.
Limitation: Since V10.1.4. Permanent Restriction, see APAR IT34526.

IBM Spectrum Protect Plus does not support Unicode normalization (internal reference #SPP-6852 & SPP-8705)
Problem: When you use 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 you search 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 by using an alternative code point representation.
Workaround: When you use any search box in IBM Spectrum Protect Plus, if it is suspected that characters such as the preceding 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: Therefore, the IBM Spectrum Protect Plus product does not follow ICU collation sorting for menus the ordering of menus 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 you use these languages appear out of expected order.
Workaround: None.
Limitation: Since V10.1.3. Permanent restriction, see APAR IT34456.
 

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

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

Back ups 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. Permanent restriction, see APAR IT35005.
 

If the latest restore point of a resource is manually expired, older versions of the restore point do 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 do not display on associated Restore screens.
Workaround: Run the backup job again to capture the latest restore point. When complete, older versions of the restore point do display on associated Restore screens.
Limitation:  Since V10.1.2.
 

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

Insufficient error messages for low disk space situation (internal reference #SPP-10668)
Problem: If the LINUX or AIX servers do not have enough free space, the error messages do not mention it is a free space issue.
Workaround: Make sure the LINUX or AIX servers have enough free space according to the requirements documentation.
Limitation: Since V10.1.1. Solved with V10.1.8 patch1.
 

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 issue 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.
 

vSnap installation on physical RHEL system fails due to dependency conflicts (internal reference #SPP-14901)
Problem: vSnap installer consists of the core vSnap software and third-party dependency packages. When installed on physical RHEL systems where the operating system was preinstalled by the user, the existing set of third-party packages present in the operating system might have minor version differences that cause dependency conflicts with the packages provided by vSnap. As a result the vSnap installation can fail due to the failure to install or update third-party packages.
Problem Verification: Refer to the on-screen messages reported by the failed installation, or refer to the installation log file at /opt/vSnap/log/install.log. The failure messages indicate yum dependency conflicts. The exact packages listed can differ, but some common packages that cause failure are samba or crypt setup.
Workaround: Manually install or update some packages by using yum commands to resolve the conflicts. The exact command that needs to be run differs depending on which packages caused the failure. Contact IBM Support for assistance.
Limitation: Since V10.1.0.
 

Assigning SLAs to multiple resources does not maintain originally assigned SLAs (internal reference #SPP-13436)
Problem: When you assign SLAs to multiple resources that have existing SLAs assigned, the presented pane of SLAs has no SLAs checked. Saving apply the checked SLAs to all selected resources overriding the original SLA assignments.
Workaround: Assign SLAs to a single resource at a time. When a single resource is selected, the presented pane of SLAs has the existing assigned SLAs checked.
Limitation: Since V10.1.0.
 

Restored VMware VM does not have local permissions set (internal reference #SPPSUP-1772)
Problem: After a production restore operation of a VMware VM, the local user permissions are not set.
Workaround: Do a production disk restore or manually set the permissions through vCenter.
Limitation: Since V10.1.0. Permanent restriction, see APAR IT35105.
 

Certificates in the .p12 format cannot be imported through the administrative console (internal reference #SPP-9355)
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. The .p12 certificates can be imported only into the IBM Spectrum Protect Plus keystore.
Workaround: To import the .p12 certificates into the keystore, follow the procedure:
Log in 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, restart the appliance.
Limitation: Since V10.1.0. Permanent restriction, see APAR IT35015.
 

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 assign 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.
 

IBM Spectrum Protect Plus system log sizes grow 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 might be filled and the download of this log file is difficult. Logs that contribute to large deviations are however regularly reviewed, usefulness to troubleshooting.
Workaround: Make sure that logs are reviewed and removed regularly.
Limitation: Since V10.1.0. Permanent restriction, see APAR IT26590.


 


Hypervisor VMware related

An RBAC user assigned a VMWare Tag and Categories along with either Hosts and Clusters or VMs and Templates results in data not being displayed (internal reference #SPP-8913)
Problem: Users that are assigned to the Tag and Categories resource group and either Hosts and Clusters or virtual machines and Templates result in data not being displayed for the Hosts and Clusters view or virtual machines and Templates view.  Only information for Tags and Categories displayed when that is selected as a view when you run backup operations.
Workaround: Do not assign a user to more than one VMware resource group.
Limitation:  Since V10.1.4. Permanent restriction, see APAR IT30103.
 

IBM Spectrum Protect Plus backup of Windows Server 2019 fails with error: “Error: com.vmware.vim25.ApplicationQuiesceFault” (internal reference #SPP-9873)
Problem: Running 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 and allow the Microsoft Volume Shadow Service to run automatically.  When this disable is done, reattempt the backup job that failed with the error.
Disable the VMware Snapshot Provider service in the guest operating system:

  1. Log in to the guest operating system by 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 operating system:

  1. Log in to the guest operating system by 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.

Reattempt any backup jobs that failed as a result of the error. For more information, see https://kb.vmware.com/s/article/60395
Limitation: Since V10.1.3. This issue is resolved in Windows Server version 1809 and all versions of Windows Server 2019 OS Build 17763.1012. For more information, see 23 January 2020—KB4534321 (OS Build 17763.1012) Permanent restriction, see APAR IT34555.
 

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, see APAR IT34980.
 

VMware backup will occasionally fail for some VMs with the error "Cannot complete login due to an incorrect user name or password." (internal reference #SPPUP-2862)
Problem Verification: The login credentials for the vCenter are correct and other VMs using the same vCenter in the same backup succeed. Retrying the failed VMs usually completes successfully.
Workaround: Reduce the number of VMs in the SLA. Check the vCenter for any performance issues.
Limitation:  Since V10.1.0.
 


 


Hypervisor Hyper-V related

Back up and restore operations for Hyper-V shared virtual hard disks fails (internal reference #SPP-1108)
Problem: When you attempt 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.
 


 


SQL Server application protection related

IBM Spectrum Protect Plus does not differentiate between identically named databases in different instances (internal reference #SPP-6222)
Problem: SQL instance names are not referenced in the IBM Spectrum Protect Plus API when the database name is entered in the Force full backup for resource field. If the option is used, base backups are done, for databases that have the same name, but reside on different instances of an SQL server. There is no way to differentiate between identically named databases in different instances that use that option, as instance and database names are not supported.
Workaround: None.
Limitation: Since V10.1.3. Permanent restriction.
 

Incorrect Alert and job log messages when an SQL Database is in SIMPLE recovery mode (internal reference #SPP-12989)
Problem: Alerts are generated in IBM Spectrum Protect Plus when an SQL database has logged back up enabled, the SQL database recovery model is SIMPLE, and the vSnap with the log volumes is either off or has a different IP address.
Workaround: Don't put database into SIMPLE recovery mode and then change the vSnap for the SLA policy
Limitation: Since V10.1.2.
 

Log storage volume is removed when last backup snapshot is removed (internal reference #SPP-14160)
Problem: During maintenance, if there are no backup snapshots for a database, the log volume is removed. Normally this log volume removal also disables the log backups on that server, but if log backups cannot be disabled then the log backup task creates alerts on IBM Spectrum Protect Plus.
Workaround: Increase retention or back up frequency to have at least one retained backup snapshot for each database with log backup enabled.
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 an SQL Server Always-On availability groups (AG) and another to protect databases on a stand-alone instance, and if a database is moved from AG to stand-alone instance, or from stand-alone instance to AG, log backup for that database might fail from the SLA that protects the target of the move.
Workaround: After you move the database from the stand-alone instance to AG or from AG to stand-alone instance, run the SLA that was protecting the database before the move once more. Doing this action removes the log backup for that database. When that is completed, run the second SLA that protects the database at the new location. That creates the log backup for that database.
Limitation: Since V10.1.1. Permanent restriction, see APAR IT28420.
 


 


ORACLE application protection 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 wanted.
Limitation:  Since V10.1.1. Permanent restriction, see APAR IT34946.
 


 


Db2 application protection related

Two progress update rows are displayed for non-partitioned Db2 databases. (internal reference #SPP-13066)
Problem: For non-partitioned Db2 databases, two progress rows are displayed.
Problem Verification: Progress update displays two rows for the same Db2 database.
Workaround: None.
Limitation:  Since V10.1.6.
 

In IBM Spectrum Protect Plus, the log backup volume is not unmounted when log backup enablement fails (internal reference #SPP-8833)
Problem:  When log backup is not enabled in IBM Spectrum Protect Plus and then it gets enabled, the log backup enablement command run so that IBM Spectrum Protect Plus mounts a log backup volume.  In case the agent fail in enabling the log backup, even though it gets reported, the host agent does not unmount the log backup volume and it remains in a mounted state. The mounted volume continues to be used for future log backup attempts.
Workaround: None
Limitation:  Since V10.1.4. Permanent restriction, see APAR IT37628.
 

Application cataloging fails that uses fully qualified hostnames in Db2nodes.cfg (internal reference #SPP-7173, #SPP-4509)
Problem:  When hosts in db2nodes.cfg are specified by its fully qualified names (including dots), cataloging of the database instance fails on inventory with the following error message:
Cataloging failed for server <servername>:org.springframework.data.mapping.model.MappingException: Map key <hostname> contains dots but no replacement was configured! Make sure map keys don't contain dots in the first place or configure an appropriate replacement!
Workaround: Ensure to have only short hostnames in db2nodes.cfg
Limitation:  Since V10.1.4.
 

Archive log backups are limited to a single SLA policy per database (internal reference #SPP-Db2-175439 & SPP-6058)
Problem: When archive log backups are enabled on the Db2 backup options pane, 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 handle only a maximum of two log archive paths in parallel, provided there are no other archive log destinations in use (for example Tivoli Storage Manager). While there might be two SLA policies associated were 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 the following 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 are associated nonetheless, you 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.
 

Redirected restore operations to alternative locations, require path names to include the instance and database names (internal reference #SPP-db2-175655)
Problem: When a database is restored to an alternative instance name 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: 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: 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 is 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.
 

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 is checked for free space to ensure that temporary snapshots can be successfully created during the backup operation. If 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 is added to a SLA policy. When the free space declines successively it might fall under the minimum limit. However, a warning message indicates the situation it is not rated as a failed backup - the database is silently skipped. The summary of the scheduled backup run shows 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.
 


 


MongoDB application protection related

---
 


Exchange Server application protection related

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 contains 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.
For more information, see Microsoft documentation: https://docs.microsoft.com/en-us/powershell/module/exchange/mailboxes/new-mailbox?view=exchange-ps
Workaround: When you create 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.
 


 


Microsoft 365 application protection related

IBM tested Microsoft 365 support in IBM Spectrum Protect Plus with 4000 Exchange Online & OneDrive users.
 

Upgrade IBM Spectrum Protect Plus V10.1.5 or V10.1.6 to V10.1.7 keeps the old UI structure when you restore Microsoft365 (internal reference #SPP365-229)
Problem: IBM Spectrum Protect Plus V10.1.7 provides new UI structure for Microsoft365 protection. The old structure is still shown when restore operation is done with previous versions.
Workaround: None.
Limitation: Since V10.1.7. Permanent restriction, see APAR IT37670.
 

The SLA policy assigned to OneDrive feature needs to reassigned (internal reference #SPP365-186)
Problem: Due to the restructuring of the inventory process of the Microsoft 365 application, reassigning the SLA to the OneDrive feature is necessary
Workaround: none
Limitation: Since V10.1.7. Permanent restriction, see APAR IT36184.
 

The M365 agent process can hang if the system prerequisites are not met (internal reference #SPP365-253)
Problem: When the operating system prerequisites are not met for the Microsoft365 agent, the job for Microsoft365 hangs. Inventory process is started but no further progress is displayed. The job is running until it canceled.
Workaround: Install all required packages according to the documentation.
Limitation:  Since V10.1.5. Solved with V10.1.8 patch1, see APAR IT34303.
 

The pie chart in the running jobs view is not updated dynamically (internal reference #SPP365-149)
Problem: The pie chart, in the running jobs view is not updated dynamically for the Microsoft365 jobs. The chart is updated after the whole job is completed.
Workaround: None.
Limitation:  Since V10.1.5.
 

Restoring the calendar event fails if the event doesn't have correct time zone (internal reference #SPP365-100)
Problem: When you create a calendar event by using for example PowerShell, it is possible to create an event without a correct time zone. Such an event can be protected but cannot be restored.
Workaround: None.
Limitation:  Since V10.1.5. Permanent restriction.
 

The backup job hangs until all data to be protected are processed if there is no free space left at the backup destination (internal reference #SPP365-68)
Problem: When there is no free space left on the backup destination, the agent anyway tries to process all objects that expected to be protected.
Workaround: Add more space to the backup destination.
Limitation:  Since V10.1.5.
 

Microsoft 365 protection with IBM Spectrum Protect Plus does not support HTTP/S proxy configuration (internal reference #SPPSUP365-27)
Problem: Microsoft 365 protection with IBM Spectrum Protect Plus requires to set up a Linux machine that acts as a cloud proxy system. This machine hosts the backup and restore agent. It is required that this machine has a direct route to the Microsoft REST API endpoints. Because the backup agent does not recognize HTTP/S proxy settings, routing the traffic by using a HTTP/S proxy system is not supported.
Problem Verification: When an HTTP/S proxy is configured to route the traffic between the agent machine and Microsoft 365 REST API endpoints, the protection fails.
Workaround: Ensure that the agent machine has a direct route to Microsoft 365 REST API endpoints.
Limitation:  Since V10.1.5.
 

Office 365 data size is not included in a license report (SPP365-20)
Problem: When you protect Office 365 data, the amount of protected data is not included in a license report.
Workaround: None.
Limitation:  Since V10.1.5.
 


 


Container protection related

Warnings during Helm installation (internal reference #SPP-Container-2822)
Problem: During installation, the following warnings are displayed:

Warning: resource customresourcedefinitions/kafkas.kafka.strimzi.io is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by kubectl apply. kubectl apply should only be used on resources created declaratively by either kubectl create --save-config or kubectl apply. The missing annotation will be patched automatically.
customresourcedefinition.apiextensions.k8s.io/kafkas.kafka.strimzi.io configured

These warnings are not significant, and the installation is still successful.
Workaround: None required.
Limitation: Since V10.1.8.1.
 

The baas-minio pod for Container Backup Support does not start when SecurityContextConstraint anyuid is set as the default instead of restricted (internal reference #SPP-Container-2833)
Problem: When IBM Block CSI, IBM Scale CSI, or IBM Spectrum Protect Plus containerized server on OpenShift is installed, or when one of their operations is running, the default SecurityContextConstraint (SCC) that is applied to non-default ServiceAccounts is modified from 'restricted' to 'anyuid'. This modification causes the baas-minio container to fail to start because the expected the SCC is 'restricted'.
Problem Verification: Steps to reproduce the behavior:

  1. Install IBM Block CSI, IBM Scale CSI, or IBM Spectrum Protect Plus server and run related actions such as creating PVCs, snapshot PVCs, restore from snapshot PVC. The specific software or action that triggers this error is unknown now. It is unlikely to be caused by the Container Backup Support software.
  2. Install Container Backup Support.
  3. The baas-minio containers ends up in the 'Error' state and crash-loops with permission errors issued in the logs of the baas-minio pod.
  4. Run the command:
    oc describe pods -n baas | grep scc

If the anyuid SCC was applied, the output looks similar to the following example:

openshift.io/scc: anyuid
openshift.io/scc: anyuid
openshift.io/scc: anyuid
openshift.io/scc: anyuid
openshift.io/scc: anyuid
openshift.io/scc: anyuid
openshift.io/scc: baas-scc
openshift.io/scc: anyuid
openshift.io/scc: anyuid
openshift.io/scc: anyuid
openshift.io/scc: anyuid
openshift.io/scc: anyuid
openshift.io/scc: anyuid

Workaround: The modification of the SCC to anyuid of the Container Backup Support pods (except the baas-spp-agent pod, which is set to baas-scc) is caused by the following field in the 'ClusterRoleBinding' object 'system:openshift:scc:anyuid'.
Run the following command:

oc describe clusterrolebinding system:openshift:scc:anyuid

The output is similar to the following example:

...
subjects:
    apiGroup: rbac.authorization.k8s.io
    kind: Group
    name: system:authenticated

Extra 'subject' and 'roleRef' fields might exist.
The issue can be fixed by deleting this subject from the ClusterRoleBinding object and then running the following command to restart the Container Backup Support pods:

oc delete pods --namespace baas --all

The SCC that is attached to a pod changes only on the deletion and restart of a pod.
Limitation: Since V10.1.8.
 

Duplicate identities of the container agent in IBM Spectrum Protect Plus Server (internal reference #SPP-Container-2718)
Problem: Upon initial installation, the Container agent might get the identity added twice in the IBM Spectrum Protect Plus GUI. This behavior results in two 'identities' with the same name, which causes the cluster registration to fail. The cluster is not automatically register and is not available for SLA policy selection.
Problem Verification: The IBM Spectrum Protect Plus GUI shows two clusters with the same identity.
Workaround: Remove one identity and register the cluster manually
Limitation: Since V10.1.8.
 

IBM block storage and IBM Spectrum Scale storage are not supported as a MinIO Object Store in Velero (internal reference #SPP-Container-2655)
Problem: IBM block storage and IBM Spectrum Scale storage are not supported as a MinIO Object Store in Velero to protect cluster-scoped and namespace-scoped resources. Do not use IBM block or IBM Spectrum Scale storage class in baas-values.yaml minioStorageClass parameter. IBM Spectrum Scale storage class is supported as a MinIO Object Store in Velero only in Spectrum Scale Container Native Storage Access (CNSA) Cluster.
Problem Verification: MinIO pod fails to start with the following errors:

$ oc logs baas-minio-0 -n baas
mkdir: cannot create directory '/storage/velero': Permission denied
Certdir exist exiting loop
cp: cannot create regular file '/config/certs/public.crt': Permission denied
cp: cannot create regular file '/config/certs/private.key': Permission denied
ERROR Unable to initialize backend: mkdir /storage/.minio.sys: permission denied

Workaround:

  1. Use Ceph file system storage or Ceph RBD (RADOS Block Device) block storage type for Velero MinIO storage.
  2. IBM Spectrum Scale storage class is supported as a MinIO Object Store in Velero only in IBM Spectrum Scale Container Native Storage Access (CNSA) Cluster.
Limitation: Since V10.1.8.

 

IBM Spectrum Protect Plus container persistent volume backup history report shows incorrect backup size for IBM Spectrum Scale PVC (internal reference #SPP-Container-2617)
Problem: If IBM Spectrum Scale PVC is smaller than IBM Spectrum Scale file system block size, the snapshot size of PVC is larger than the size of PVC. As a result, IBM Spectrum Protect Plus job log shows incorrect transfer size of backup and IBM Spectrum Protect Plus container persistent volume backup history report shows incorrect backup size. For more information, see https://github.com/IBM/ibm-spectrum-scale-csi/issues/422
Problem Verification: Run Report 'Container Persistent Volume backup history' IBM Spectrum Protect Plus job log message CTGGA2402 shows incorrect transfer size of backup.
Workaround: Increase the size of PVC.
Limitation: Since V10.1.8.
 

Copy backup of CephFS Persistent Volume Claims (PVC) with many files can run in to a timeout (internal reference #SPP-Container-2203)
Problem: During a copy backup operation of a CephFS PVC, the volume is cloned from a snapshot. Due to a known issue in the cephfs-csi driver (https://github.com/ceph/ceph-csi/issues/411) this operation can take long and run in to a timeout when the PVC contains many files (30000+). The ceph-csi driver copies all files after the snapshot restore, which causes the long operation. Until this issue is fixed potentially, there is a need to raise the timeout to allow the copy backup operation to finish.
Problem Verification: If the copy backup fails, check the job log for the following message:

CTGGA2632 Backup failed for PVC timed out after seconds. Backup failed for this PVC due to encountering an error.


Workaround: You can configure the PVC snapshot restore timeout in the configmap baas-configmap.

  1. Run
    oc edit configmap baas-configmap -n baas
  2. Look for attribute: pvcSnapshotRestoreTimeout, and set it to the new timeout in minutes
    pvcSnapshotRestoreTimeout: ""
  3. Save the configmap
  4. Rerun the copy backup operation in IBM Spectrum Protect Plus

Limitation: Since V10.1.8.
 

Scale PVC restored from copy backup has less available disk space than source PVC and restored data might be incomplete. (internal reference #SPP-Container-2415)
Problem: A known problem in IBM Spectrum Scale "shrink-to-fit" functionality causes unexpected disk space usage in file system. As a result:

  • Scale volume restored from copy backup has less available disk space than source volume.
  • If restored volume has insufficient disk space, some files are not restored.
Problem Verification: 
  1. To verify disk space on the restored volume: Mount source volume and restored volume into pod and use 'df -h' command to view disk space on each mounted file system:
    $ oc -n test exec myPod -- df -h /source-pvc Filesystem Size Used Avail Use% Mounted on TSMstg 5.0G 1.1G 4.0G 21% /source-pvc
    $ oc -n test exec myPod -- df -h /restored-pvc Filesystem Size Used Avail Use% Mounted on TSMstg 5.0G 2.1G 3.0G 41% /restored-pvc
  2. To verify incomplete data restore: check if restored PVC is 100% full with no available disk space and some of the restored files have zero byte size.
Workaround:
  1. Users running IBM Spectrum Scale V5.0.0.0 (ESS 5.3.0.0 or ESS 6.0.0.0) through V5.0.5.7 (ESS 5.3.7.1 or ESS 6.0.2.1), should apply IBM Spectrum Scale V5.0.5.8 or later
  2. Users running IBM Spectrum Scale V5.1.0.0 (ESS 6.1.0.0) through V5.1.1.0 (ESS 6.1.1.0), should apply IBM Spectrum Scale V5.1.1.1 or later
  3. If you cannot apply one of the above PTF levels, contact IBM Service to obtain and apply an efix for your level of code
    -  For IBM Spectrum Scale V5.0.0.0 thru V5.0.5.7, reference APAR  IJ32581
    -  For IBM Spectrum Scale V5.1.0.0 thru V5.1.1.0, reference APAR  IJ32627
For more information, see IBM Spectrum Scale: The intended shrinkage ("shrink-to-fit") of the pre-allocated last data block of a file might be skipped, causing increased space usage.
Limitation: Since V10.1.8.
 

Cluster-scope resource restore with ValidatingWebhookConfiguration objects (internal reference #SPP-Container-2339)
Problem: When you try to restore cluster-scoped resources, Velero reports PartiallyFailed if there are ValidatingWebhookConfiguration objects to be restored. This report is the default case for OCP environments.
Problem Verification: In the downloadable joblog.zip for the restore-job, in the included diag.tar.gz the included Velero log includes an error like this:

time="2021-03-17T08:25:27Z" level=info msg="error restoring multus.openshift.io: ValidatingWebhookConfiguration.admissionregistration.k8s.io "multus.openshift.io" is invalid: webhooks[0].sideEffects: Unsupported value: "Unknown": supported values: "None", "NoneOnDryRun"" logSource="pkg/restore/restore.go:1170" restore=spp-velero/spprestore-k8s-bba0d48e-f1f2-47c7-82d8-31b96e79abe2

Workaround: None. All other objects are restored correctly, only the WebhookConfiguration objects are not, which leads to a status of PartiallyFailed for the whole restore operation.
Limitation: Since V10.1.8.
 

Velero crashes during process of a massive number of events (internal reference #SPP-Container-2300)
Problem: On some OpenShift® environments, Velero crashes during backup operations of cluster-scoped resources even though you followed instructions in Installing and configuring Velero by using the OADP Operator to increase memory for the Velero deployment.
Problem Verification: To troubleshoot this issue:

  1. Run the following oc logs command to show whether Velero crashes when it tries to process Event resources:
    oc logs deployment/velero –n spp-velero
  2. Look for output that is similar to the following example:
    logSource="pkg/backup/item_collector.go:297" namespace= resource=secrets
    time="2021-03-08T10:01:50Z" level=info msg="Getting items for resource" backup=spp-velero/test-debug group=v1 logSource="pkg/backup/item_collector.go:165" resource=events
    time="2021-03-08T10:01:50Z" level=info msg="Listing items" backup=spp-velero/test-debug group=v1 logSource="pkg/backup/item_collector.go:291" namespace= resource=events
  3. On the OpenShift cluster that is exhibiting the symptoms, run the following command to show the exact number of events that are logged:
    oc get events --A | wc -l
If the amount exceeds 100,000 events, the cluster is affected.
Workaround:  To resolve this issue, delete old events by running the following command:
oc delete events --A –-all
Alternatively, if you do not want to delete all events, select the events that are no longer needed. You can use the oc delete events command to delete events that are restricted to a namespace. For example, run the following command to delete all the events in the baas namespace:
oc delete events -n baas --all
After the old events are removed, Velero cluster-scoped resource backup operations can resume.

Limitation: Since V10.1.8.
 

Warning indicates deprecated resource to be removed in Kubernetes 1.22 (internal reference #SPP-Container-2302)
Problem: The packaged dependency Red Hat AMQ Streams 1.62 uses deprecated versions of the CustomResourceDefinition API. This limitation has no effect on installation unless you install on Kubernetes 1.22 and later. Kubernetes 1.22 has yet to be released. In Kubernetes 1.22 and later, installation fails.
Problem Verification: Install the Strimzi 0.21 helm chart. The same warning appears.
Workaround: None
Limitation: Since V10.1.8.
 

Cannot register external Container Backup Support to a containerized IBM Spectrum Protect Plus server (internal reference #SPP-container-2486
)
Problem: When you install Container Backup Support, the cluster is not automatically registered to a containerized IBM Spectrum Protect Plus server.

Problem Verification: The cluster is not registered on the containerized IBM Spectrum Protect Plus server. Additionally, on the cluster, the transaction manager pods might not be running due to a failed liveness probe.

Workaround: In order for Container Backup Support to find the containerized IBM Spectrum Protect Plus server, the name resolution must be working correctly. There are several ways to accomplish this, including adding the IBM Spectrum Protect Plus external IP address to the domain name server. Alternatively, add a host alias to the baas-transaction-manager deployment on the cluster. You might need to scale the deployment down and back up for the host alias to take effect. The host alias appears similar to the following text:

  • hostAliases:  ip: “10.10.96.49"
  • hostnames: “sppserver1.apps.cos.cloud.local"


Additional information is available in the Kubernetes documentation:
https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/
Limitation: Since V10.1.7. Solved with V10.1.8 patch1.
 

Configmap objects are not removed after backup and restore operations on OpenShift clusters (internal reference #SPP-Container-2445)
Problem: During a backup or restore job of PVCs to the vSnap server on OpenShift clusters, temporary configmap resources are created for the operation. These configmap objects are not removed after the operation is completed as expected.
Problem Verification: Run a backup or restore job on an OpenShift cluster. Then, run the following command:

oc get ConfigMap --namespace

Check for configmap objects starting with the name 'backup-' or 'restore-'. The existence of these objects confirms the issue.
Workaround: Delete the configmap objects after backup or restore operations with the following commands.

Backups: oc get configmap --namespace | grep 'backup*' | xargs oc delete configmap -n
Restore: oc get configmap --namespace | grep 'restore*' | xargs oc delete configmap -n

Limitation: Since V10.1.7. Solved with V10.1.8 patch1.
 

Warning about CustomResourceDefinition API version v1beta1 is issued during installation and uninstallation of Container Backup Support (internal reference #SPP-container-1964)
Problem: When you install or uninstall Container Backup Support on a Kubernetes or OpenShift cluster, a warning message is issued by Helm 3. The warning message is similar to the following example:

WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: <path for kubeconfig file>

W1119 141254.210782 10425 warnings.go:67] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition

This warning is issued because the Custom Resource Definition API version v1beta1 is deprecated in Kubernetes 1.16 and is scheduled to remove in Kubernetes 1.22 and a future release of Red Hat OpenShift Container Platform.
The deprecation does not affect the functionality of Container Backup Support 10.1.7 because the product is supported on Kubernetes 1.17, 1.18, and 1.19, and OpenShift Container Platform 4.5 and 4.6. However, applications such as the Helm 3 package manager issues the warning.
Workaround: None. This warning is expected.
Limitation: Since V10.1.7.
 

Error pops up during VADP registration in Docker deployment environment (internal reference #SPP-14659)
Problem: During VADP registration, user can notice error in UI:

Syntax error Unexpected token S in JSON at position 0

Workaround: However, the VADP gets registered the issue is in UI module. So workaround is just to click OK and the VADP is registered.
Limitation:  Since V10.1.7.
 

Node failure causes agent to not respond (internal reference #SPP-container-2781)
Problem: When a node fails that is hosting the Spectrum Protect Plus container agent pod, the agent might stop responding. The following message appears in the Spectrum Protect Plus job log:

CTGGA3106 Failed to find the application servers for this job Failed to find the application servers where the selected items are located.

Workaround: Log in to the cluster and do the following:

  1. Run the command:
    kubectl(or oc) get pods -n baas
  2. Identify the Agent pod.
  3. Run the command:
    kubectl delete pod SPP-Agentpodname -n baas

    Once the agent pod is restarted, all operations should work again.
Limitation:  Since V10.1.6.
 

A namespace might appear more than once in the restore wizard after an upgrade from 10.1.6 or 10.1.7 (internal reference #SPP-16188)
Problem: After IBM Spectrum Protect Plus is upgraded from 10.1.6 or 10.1.7, a namespace might appear more than once in the restore wizard if a namespace was deleted and created again between backups. The duplicate entries stay until the backups from older version are expired.
Workaround: The old entry is removed when the backups are expired.
Limitation:  Since V10.1.6.
 


 


File system protection related

After deployment of the file system Restore Service, a local installed Python version cannot be used anymore (internal reference #SPP-13033)
Problem: The file system restore service changes the global settings for all users. After that, an installed Python version cannot be found anymore. That change is happening for all user on the system. All Python by using programs on the System fails to run properly.
Workaround: To solve this behavior:

  • Uninstall the global Python version and install for all user that needs Python a personal version, or
  • Change for every user that needs Python the local path settings.
    Make sure that you do not change the global path settings. If the global path settings are changed, a restore is not possible anymore.
    Also, make sure not to change the settings of the administrative user that is used for the file system agent.

Limitation:  Since V10.1.6.
 

Protection of stub files is not supported (internal reference #SPP-13082)
Problem: Stub files (for example IBM Spectrum Protect HSM for Windows migrated files) are not supported for backup and restore. When you try to restore such a file, the operation fails. 
Workaround: Do not back up volumes, which include stub files or exclude all folders containing such files.
Limitation:  Since V10.1.6. Permanent restriction, see APAR IT34908.
 

Inventory not detecting all file systems when VM was cloned or created from a template (internal reference #SPP-13143)
Problem: The Windows file system inventory in IBM Spectrum Protect Plus is affected by a commonly known issue when the file server instance was created from a template or cloned from other VMs. In this case, the Universally Unique Identifier (UUID) for the Virtual Machine Disks (VMDK) might be the same for original and the cloned VMs. Since the IBM Spectrum Protect Plus UI uses the VMDK UUID to relate the volume to a File Server instance, it displays only one instance of the volume in the UI. All other volumes with identical UUID are not displayed even though the inventory detected these volumes.
Workaround: None.
Limitation:  Since V10.1.6. Permanent restriction, see APAR IT33412.


 


Limitations solved with V10.1.8

Backup fails for the whole SLA instead of just for the vm with the failed backup (internal reference #SPP-14903)
Problem: Backup fails for the whole SLA instead of just for the vm with the failed backup.
Problem Verification: Backup fails for the whole SLA instead of just for the vm with the failed backup.
Workaround: None.
Limitation: Since V10.1.7. Solved with V10.1.8.
 

IBM Spectrum Protect Plus OVA contains unused disks, which are not needed (internal reference #SPP-14805)
Problem: Beginning with IBM Spectrum Protect Plus V10.1.7, the onboard vSnap is no longer included as part of the virtual appliance. However, two virtual disks that were previously used by the onboard vSnap are still included as part of the OVA and Hyper-V distributions of IBM Spectrum Protect Plus. These two disks unnecessarily consume space after deployment even though they are unused.
Problem Verification: Run sudo lsblk on the command line as the server admin user. The problem can be confirmed if the output shows two disks of size 100 GB and 128 GB, which do not contain any partition or file system.
Workaround: Shut down the IBM Spectrum Protect Plus server, then detach the two unused disks of size 100 GB and 128 GB. Power on the server and verify that normal operations are unaffected. It is then safe to delete the detached disks.
Limitation: Since V10.1.7. Solved with V10.1.8.
 

Namespace must exist to restore entire namespace (internal reference #SPP-container-1965)
Problem: If the namespace does not exist, the restore fails. The following message is in the logs.

CTGGK3077 [] The data mover failed to start with the reported reason: None

Workaround: Create the namespace before the restore command.
Limitation: Since V10.1.7. Solved with V10.1.8.
 

Incorrect transfer size in job log while replication or copy is in progress (internal reference #SPP365-181)
Problem: While a replication or copy job is in progress, the job log displays progress messages at 5-minute intervals. The progress messages report the current size transferred and the total estimated size to be transferred. In some cases, the total estimated size might be incorrect, resulting in cases where the transferred size exceeds the total estimated size. The problem is limited to messages that are displayed while the job is in progress. When the job is complete, the total transferred size recorded at the end is accurate.
Workaround: None.
Limitation: Since V10.1.6. Solved with V10.1.8.
 

Replication and offload still report VMs that already took out from the SLA and fail to replicate and offload those VMs (internal reference #SPP-14843)
Problem: Unselected SLA VM being replication messages show up in log files:

Unable to determine storage volume for <vm Name>

Where VM name is the VM, which is unselected from SLA. This behavior is expected as anything backed up is replicated.
Workaround: None.
Limitation: Since V10.1.5. Solved with V10.1.8.
 

Protected and Unprotected VMs report does not show individual tags for selection as an RBAC user. (internal reference #SPP-14248)
Problem: As an RBAC user, the Protected and Unprotected VMs report allows only "(All)" option for the "Tags" parameter.
Workaround: Defined Resource group with a higher-level selection.  For example, data center level or category level.
Limitation: Since V10.1.5. Solved with V10.1.8.
 

Back up to Cloud Object Storage failure due to checksum mismatch (internal reference #SPP-14808)
Problem: At the end of running condense on Cloud Object Storage, the metadata fails to be properly uploaded to the cloud. Normally there is a local copy so there is no visible effect. However, if a customer manually deletes the local data cache under /opt/vSnap-data, the next incremental offload fails if and only if a condense operation runs more recently than a backup operation.
Problem Verification

  • Do an incremental backup to Cloud Object Storage through a one time job
  • Delete the previous cloud snapshot
  • Manually delete the local data cache under /opt/vSnap-data before another backup to Cloud Object Storage runs
  • Do another incremental backup to Cloud Object Storage and verify that it fails

Workaround: Do a new full backup to cloud offload storage by resetting the relationship on the vSnap command line:

vSnap cloud relationship reset –id <relationship_id>

Limitation: Since V10.1.5. Solved with V10.1.8.
 

New user creation results in error when password length is fewer than 8 characters. (internal reference #SPP-10640)
Problem: If the global preferences minimum password length is set to less than 8, the UI accepts shorter than 8 character passwords during user creation. However, submittal of the request to create the user ends with an error indicating the password must have a minimum length.
Workaround: Users must use passwords that are 8 characters or longer.
Limitation:  Since V10.1.5. Solved with V10.1.8.
 

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 action might result in subsequent cleanup failures.
Workaround: Check for active restore jobs pointing to the Application Server before deletion.
Limitation:  Since V10.1.3. Solved with V10.1.8.
 

IBM Spectrum Protect Plus Admin Console reports login error when trial license is expired (internal reference #SPP-12827)
Problem: When the IBM Spectrum Protect Plus trial license is expired, login to the Admin Console fails with "login error" message. There is no indication that the IBM Spectrum Protect Plus trial license is expired.
Workaround: Update the trial license. Alternatively, login to the IBM Spectrum Protect Plus Admin Console by using the system, server admin, password.
Limitation: Since V10.1.0. Solved with V10.1.8.
 

Log Backup: Race condition when scheduled run collides with on-demand run (internal reference #SPP-10286)
Problem: When the scheduled run of the log backup coincides with the on-demand log backup of the main backup job for an Oracle database, errors occur in one of the jobs.
Workaround: Adjust schedules of log backup and SLA backup to avoid simultaneous runs.
Workaround: None.
Limitation:  Since 10.1.0. Solved with V10.1.8.
 

vSnap Storage Utilization Report column truncation in PDF export. (internal reference #SPP-14899)
Problem: Some columns in vSnap Storage Utilization report are cut off slightly in certain resolutions.
Workaround: None.
Limitation: Since V10.1.0. Solved with V10.1.8.


 


Limitations solved with V10.1.7

If no VADP proxy is enabled, VMware VM backup hangs. (internal reference #SPP-14887)
Problem: If no VADP proxy is enabled, VMware VM backup hangs.
Workaround: Have at least one enabled VADP proxy.
Limitation: Since V10.1.7. Solved with V10.1.7.2.
 

Deleting and re-creating the same namespace causes multiple entries for the same namespace when you select resources to restore. (internal reference #SPP-container-1887)
Problem: Deleting and re-creating the same namespace between backups of PersistentVolumeClaims and resources in the same namespace result in the appearance of multiple entries of the same namespace when you restore from the IBM Spectrum Protect Server user interface.
Problem Verification: Use the IBM Spectrum Protect Server user interface to select a restore job and choose a cluster. If this problem occurred, one or more namespaces appear more than once for the same cluster.
Workaround: All unexpired backups are available for restore. Select each identical appearing namespaces to find the wanted restore point.
Limitation: Since 10.1.7. Solved with V10.1.7.2.
 

Baasreq of type "destroy" does not work (internal reference #SPP-container-2004)
Problem: CBS backups are not removed after you run a "destroy" operation by using the command line baasreq interface.
Workaround: Use the GUI to remove prior backups.
Limitation: Since V10.1.7.1. Solved with V10.1.7.2.
 

When you select Kubernetes or OpenShift volumes, and resources for restore, the namespace is duplicated (internal reference #SPP-container-2000)
Problem: Creating and deleting the same namespace multiple times causes the namespace to be treated as separate namespaces for restore.
Workaround: Search through each namespace to find the backup wanted for restore. The backup is in one of the duplicated namespaces.
Limitation: Since V10.1.7.  Solved with V10.1.7.2.
 

Resources baasreq parameter "scope" supposed to be not case-sensitive (internal reference #SPP-container-2015)
Problem: When you create a baasreq to back up resources, the parameter "scope" is required. It must be either "namespace" or "cluster". However, the parameter is case-sensitive. If the parameter is not all lowercase, the resource is assigned to the SLA, but CBS is not able to query for a list of previous backups, so restore is blocked.
Workaround: Use all lowercase to specify "namespace" or "cluster" for the scope parameter, or use the GUI to run the operation.
Limitation: Since V10.1.7. Solved with V10.1.7.2.
 

The restore wizard does not filter all backups (internal reference #SPP-15118)
Problem: The restore wizard show backups that expected to be filtered out by the date filter.
Workaround: None.
Limitation: Since V10.1.7. Solved with V10.1.7.2.
 

Backups of Kubernetes and OpenShift volumes fail with message SLA not found (internal reference #SPP-14829)
Problem: In some circumstances, a query of the SLA of a PersistentVolumeClaim fails to trigger a backup failure.
Problem Verification: In the "Jobs and Operations" page, a job fails with the error message CTGGK3078.
Workaround: Retry the backup job. This error is intermittent.
Limitation: Since V10.1.7. Solved with V10.1.7.2.

Restore wizard shows snapshot backups that are no longer valid (internal reference #SPP-13294)
Problem: Restore wizard shows snapshot backups that do not work. Cause appears to be in the maintenance process somewhere.
Workaround: Choose only the in-retention snapshots in the restore wizard
Limitation:  Since V10.1.7. Solved with V10.1.7.2.
 

Creating new job with the restore wizard results in a missing submit button (internal reference #SPP-14627)
Problem: Double-click of the source type step of the wizard can result in a missing submit button on the final review step.
Workaround: Single click source type step of the wizard.
Limitation:  Since V10.1.4. Solved with V10.1.7.1.
 

Kubernetes and OpenShift restore wizards do not preselect storage class selections in edit. (internal reference #SPP-14737)
Problem: Edit of an existing restore job for Kubernetes and OpenShift will not replay the existing storage class selections. The wizards reset the storage class selections back to the original storage class.
Workaround: Reselect the storage class selections.
Limitation:  Since V10.1.6. Solved with V10.1.7.1.
 

OpenShift restore wizard "New PVC Name" field is automatically filled incorrectly (internal reference #SPP-14807)
Problem: OpenShift restore wizard automatically completes the "New PVC Name" fields incorrectly. This action can result in the final submit button on the review step to be disabled.
Problem Verification: Traversing through the OpenShift restore wizard results in a disabled submit button.
Workaround: None.
Limitation:  Since V10.1.7. Solved with V10.1.7.1.
 

The set destination page of the Kubernetes and OpenShift wizard does not display correct information if you returned from previous selection. (internal reference #SPP-14734)
Problem: If the user returns to the set destination page of the Kubernetes or OpenShift wizard, the previous selections is not displayed properly.
Workaround: Users will still be able to create a valid restore job. Condition: during the process, the user decides not to change the previously selected resources and backup source type.
Limitation:  Since V10.1.7. Solved with V10.1.7.1.
 

IBM Spectrum Protect Plus server can fail when file indexing database exceeds maximum size (internal reference #SPPSUP-1685)
Problem: When file indexing is running by IBM Spectrum Protect Plus, entries are created in an internal database, which are used for file level restores. If this database grows beyond the maximum size (~2.1 billion entries), it might cause the IBM Spectrum Protect Plus server to fail and not be able to restarted. This limitation can be identified in the Virgo log by:

Too many documents, composite IndexReaders cannot exceed 2147483647

Workaround: Complete the following procedure:
Important: File restore for all completed backups do not work after you run this procedure. VMDK and full VM restores continue to work. Backup jobs begin file indexing and future file level restores works based on the new backup jobs.

  1. Open an SSH session to the IBM Spectrum Protect Plus appliance with the server admin account. At the command line, enter:
    $ sudo rm /data3/lucene/lucidx/*
  2. After the removal process completes, start Virgo:
    $ sudo systemctl start virgo
  3. Exclude VMs that have file catalog enabled, which are not required to have file level restores, so that the maximum limit is not reached.

Limitation: Since V10.1.6. Solved with V10.1.7.
 

In rare cases the arbiter node in a distributed MongoDB replica set crash during IBM Spectrum Protect Plus inventory (internal reference #SPP-mongo-182265)
Problem: If a MongoDB replica set is distributed across multiple hosts and contains an arbiter node that resides on a SLES 12 server, the arbiter node can crash during the IBM Spectrum Protect Plus inventory operation. This problem is caused by the external Python library pymongo that is used by the IBM Spectrum Protect Plus MongoDB agent. The arbiter node can be restarted manually.
Workaround:

Or
  • Start arbiter node manually.

Limitation:  Since V10.1.4. Solved with 10.1.7.
 

IBM Spectrum Protect Plus does not use TLS encryption for SMTP (internal reference #SPPSUP-1514)
Problem: The IBM Spectrum Protect Plus server can be set to send email notification for reports. IBM Spectrum Protect Plus does not use TLS encryption for SMTP. As a result, when IBM Spectrum Protect Plus sends a report notification email, it might fail to be sent if the email provider requires TLS encryption.
Workaround: None.
Limitation:  Since V10.1.5. Solved with V10.1.7, see APAR IT32382.
 

First cancelled restore job makes the second job on the same system unusable (internal reference #SPP-13071)
Problem: When two or more file system restore jobs are created for the same system and one of the jobs is canceled, then the restore GUI for the other jobs might no longer be usable.
Workaround: Cancel **restore jobs not before all objects subject to restore from all file systems are finished.
Limitation:  Since V10.1.6. Solved with V10.1.7, see APAR IT33368.
 

File system restore job might remain in state 'running' (internal reference #SPP-13032)
Problem: Running restore it might happen that a restore task remains in state 'Running' although it is finished successfully. This behavior is a display error only.
Workaround: Check the file system if the files and folders subject to restore are restored successfully. Then, cancel the restore operation in the GUI.
Limitation:  Since V10.1.6. Solved with V10.1.6ifix2 and V10.1.7, see APAR IT33370.
 

The granular restore remote package readme file contains syntax error in a command (internal reference #SPP-exchange-1205)
Problem: In granular restore remote package readme file, 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. Solved with 10.1.7.
 

During log backup on the exchange machine, if the log backup scheduler is trying to be updated, then the scheduler might be corrupted. (internal reference #SPP-exchange-1162)
Problem: The process Logbackpup  opens and hold log files under log backup scheduler folder. If an disablelogbackup command comes when logbackpup running at backend (same scheduler), and if IBM Spectrum Protect Plus Exchange agent try to delete the scheduler folder in handling the disablelogbackup command, the disablelogbackup fails by the reason of "failed to delete the scheduler folder".

This problem might happen in this condition:

  • Start the scheduled task at agent machine to run log backup of DB1
  • Disable logbackpup of DB1 and run related SLA to trigger the disablelogbackup command.
    If DB1 is the last DB in the logbackpup scheduler, then Exchange agent tries to delete the scheduler folder.
    If the logbackpup of this scheduler is still running at backend, the disablelogbackup fails.

When this problem happens, the disablelogbackup command fails and the overall status of backup job is PARTIAL.
Workaround: Since the disablelogbackup command failed, IBM Spectrum Protect Plus server sends another disablelogbackup command in next backup job. So if the logbackpup is not running, then, the next disablelogbackup removes the folder successfully.
Limitation:  Since V10.1.6. Solved with 10.1.7.
 

Deploy granular restore package to a remote server that has Microsoft Outlook installed does not work as described in readme file (internal reference #SPP-exchange-1170)
Problem: It is not possible to deploy granular restore by following the deployment steps in the readme file. The reason is that the SetupFCM.exe does not exist in the granular restore deployment package.
Workaround:  to be able to deploy granular restore follow the instructions:

  1. Copy granular restore package from Exchange Application Server
    C:\Program Files\IBM\IBM Spectrum Protect Plus\tools\exchange\imr
  2. Paste to remote server where you manage the granular restore operation from.
    C:\temp
  3. On the remote server, create deployment diagnostics folder.
    mkdir C:\temp\diag
  4. On the remote server, run the following to deploy MMC GUI and granular restore components.
    c:\temp\imr\install_imr.bat <version_nr>-TIV-TSMEXC-Win.exe 10.1.6 c:\temp

Limitation:  Since V10.1.6. Solved with V10.1.7.
 

Log backups fail when Exchange administrator password begins with "$" (internal reference #SPP-exchange 1229)
Problem: As registering an Exchange application server to IBM Spectrum Protect Plus server, if the input password begins with "$", it causes the enabling log backup operation fails.
Workaround: Change to a password not beginning with "$".
Limitation:  Since V10.1.6. Solved with V10.1.7, see APAR IT34212.
 

Exchange Mailbox Restore Configuration Wizard display the Media Check entry. (internal reference #SPP-exchange-1168)
Problem: As running IBM Spectrum Protect Plus - Exchange Mailbox Restore Configuration Wizard to check the requirements items, the Media Check entry is displayed as failed. The media check is obsolete for SPP Exchange thus creating a file 'SetupFCM.exe' is needed to get past the check.
Workaround: Find any valid Windows executable file(.exe) and rename it to SetupFCM.exe. After Media Check failed, click the Failed link on the configuration wizard pane. Specify the SetupFCM.exe in popped up window. The media check succeeds.
Limitation:  Since V10.1.6. Solved with V10.1.7.
 

The ExchSchd directory and Windows Scheduler do not sync after enablelogbakup or disablelogbackup commands (internal reference #SPP-exchange-1137)
Problem: In normal runtime condition, the C:\ProgramData\SPP\ExchScheds directory entries keep synchronized with Windows Scheduler entries. They are all required by IBM Spectrum Protect Plus for Exchange agent to run log backup correctly.
In some rare conditions, such as the user removes or modifies them partially (this action should never be done manually by user, they should do it on Spectrum Protect Plus console GUI). Some invalid ExchScheds directory or Windows Scheduler entries are left. These left entries might cause confusion to the user.
Workaround: There is no workaround. But it's safe to leave all the entries there. There is no data lose and extra system resource consumption.
Limitation:  Since V10.1.6. Solved with V10.1.7.
 


 


Limitations solved with V10.1.6

Restore multiple DBs failed to mount the databases due to files removed (internal reference #SPP-10523)
Problem: Normally Exchange will replay the log files after restore completed. But with the No Recovery option selected, we don’t want Exchange to replay the logs after restore. So we must call VSS SetAdditionalRestores() method. The SetAdditionalRestores() prevents the log files to be replayed. With a wrong logic, the SetAdditionalRestores() is called only in the restore to alternative location case. So in the restore to alternative location case, the log files always be replayed even the No Recovery selected.
Problem Verification: Restore to original location (with empty New Database Name or New Database Name is same as original database name) and select the No Recovery option. After restore, the restored log files will still be replayed and deleted.
Workaround: None.
Limitation: Since V10.1.5. Solved with V10.1.6.
 

Granular restore operation fails with missing required Exchange Roles for the current user (internal reference #SPP-exchange-946)
Problem: During granular restore, in the granular restore UI, a configuration error message pops up. If the user does not have the user rights listed, the protection operations fail. The user does not have the ability to run granular restore until the user rights are updated.
Workaround:
1. Verify that the user domain used to register the server
2. Click OK and add the indicated Exchange roles for the specified user
Limitation: Since V10.1.4. Solved with V10.1.6.
 

The organization name used for the registration of a Microsoft Office 365 tenant must not include dots (internal reference #SPP365-59)
Problem: When the organization name used for the registration of a Microsoft Office 365 tenant includes dots in the name, the restore does not work.
Example: Using the full organization name "my_name.onmicrosoft.com" the backup works, but the restore fails.
Workaround: Use an organization name that has no dots in it.
Example: Using the organization name "my_name".
Limitation: Since V10.1.5. Solved with V10.1.6.
 

Not able to restore an on-demand backup immediately. (internal reference #SPP-Kubernetes-597)
Problem: "kubectl describe" of an on-demand backup shows the backup is done but it is not restorable until the backup is reflected in the schedule backup request.
Workaround: Wait until the on-demand backup is reflected in the schedule backup request before you try to restore the on-demand backup.
Limitation: Since V10.1.5. Solved with V10.1.6.
 

Temporary files can be found in some of the restored directories (internal reference #SPP365-25)
Problem: After the restore job is completed, temporary files can be found in some of the restored directories. The temporary files names start with "~tmp"
Workaround: These temporary files are automatically removed after some time.
Limitation: Since V10.1.5. Solved with V10.1.6.
 

SQL backup failed with a confusing error message when backup LUN was disconnected at the end of the backup. (internal reference #SPP-10623)
Problem: The volume mount status was not validated before accesses the backup LUN.
Workaround: No workaround, job failed.
Limitation: Since V10.1.5. Solved with V10.1.6.
 

The "Unregister" option for a VADP Proxy appears as an empty string (internal reference #SPP-10802)
Problem: In the IBM Spectrum Protect Plus GUI the VAPD proxy page under the system configuration, select a VADP proxy from the list and then chose the 3 dots in the upper right to start the action for VADP proxy. The Unregister option for a VADP Proxy appears as an empty string.
Workaround: Clicking the empty string in the drop-down of options initiates the unregister action.
Limitation: Since V10.1.5. Solved with V10.1.6.
 

Back up target LUNs on vSnap storage do not automatically expand for Hyper-V backups (internal reference #SPP-2719)
Problem: For Hyper-V backups, if the source data store is expanded, the backup target LUN on vSnap storage does not automatically expand.
Workaround: None.
Limitation: Since V10.1.1. Solved with V10.1.6.


 


Limitations solved with V10.1.5

User Interface allows cross-platform restore operations (internal reference #SPP-7292)
Problem: In environments with machines of different OS platforms (for example AIX and Linux x86), the user interface allows the target instance to be of a different OS platform. Hence, you can trigger the restore of a Linux database to a database instance on AIX and vice versa. Even though the user interface does not prevent you from doing so it leads to unexpected results.
Workaround: Ensure that the selected target instance matches the original OS platform.
Limitation: Since V10.1.4. Solved with V10.1.5.
 

Data Protection for Exchange 8.1.8 and IBM Spectrum Protect Plus 10.1.4 Granular Restore GUI cannot coexist on the same application server (internal reference #SPP-exchange-978)
Problem: When IBM Spectrum Protect Plus is used to protect a Microsoft Exchange Server where 8.1.8 Data Protection for Exchange is already installed, if the user attempts to run a granular restore operation, the operation has unexpected behavior. The job log not lists a failure. When the user remotely connects to the application server, the granular restore UI not displays correctly and some functions not work.
Workaround:
1. Cancel the granular restore operation, if it is in the Resource Active state
2. On the Exchange server, close the granular restore or MMC UI
3. Completely uninstall 8.1.8 Data Protection for Exchange
4. Rerun granular restore
Limitation: Since V10.1.4. Solved with V10.1.5.
 

When you upgrade from IBM Spectrum Protect Plus V10.1.3 to V10.1.4, manually running a previously created policy (in V10.1.3) that has an associated subpolicy added results in a null-pointer exception (internal reference #SPPSUP-1115)
Problem: In IBM Spectrum Protect Plus, after you upgrade from V10.1.3 to V10.1.4, manually running a previously created SLA policy that also has an associated subpolicy results in a null-pointer exception. The automatic running of the SLA policy works 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 subpolicy.
Limitation: Since V10.1.3. Solved with V10.1.5, see APAR IT30380.
 

Inventory fails for Db2 databases by using non-ASCII characters in path or file names (internal reference #SPP-5965)
Problem: Databases with non-ASCII characters in path or file names (Database paths, container paths, storage paths, log, and mirror log paths) cannot be inventoried due to the following 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 file names of the database are built from ASCII characters only.
Limitation: Since V10.1.3. Solved with V10.1.5.
 

Redirected restore operations to alternative locations change ownership and permissions for all database paths up to the root file system (internal reference #SPP-Db2-179927)
Problem: When a database is restored to an alternative instance name or database name, all disk paths of the database are altered to the new names during the relocation procedure that is running 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 update applies to the complete path chain up to but not including the root file system ("/"). When the operation is completed, only the database instance user and other members of it is 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 file system so that exclusive write permissions is acceptable.
Limitation: Since V10.1.3. Solved with V10.1.5.
 

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 might still exist in cloud buckets.
Workaround: None
Limitation: Since V10.1.3. Solved with V10.1.5.
 

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

Restore of a Db2 database with renaming might break ssh communication (internal reference #SPP-Db2-185334)
Problem: When a database is restored to an alternative instance name or database name, all disk paths of the database are altered to the new names during the relocation procedure that is running 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 update applies to the complete path chain up to but not including the root file system ("/"). The permission mask being used for this operation is 0775.  
For the case that data or log paths are subdirectories of the Db2 instance user home directory those permissions are updated, too. This update can cause issues with key based ssh authentication given that ssh is configured in strict mode. In strict mode key files and the directories that they are stored in must not be writable by anyone but the owner so the mask must be 0755 or even less for group and others.  The broken ssh connectivity causes the database instance to be nonoperational given that it is multi-partitioned (DPF) and configured for ssh.
Workaround: 
1.
Set "StrictModes" to "no" in sshd_config and restart sshd service.
Or
2. Correct permissions on Db2 instance user home directory after the restore operation is completed.
Limitation: Since V10.1.2. Solved with V10.1.5.
 

vSnap password fails when you attempt 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 during access the CIFS share that uses the same account credentials. The credentials need to be resynchronized to ensure continued access.
Workaround: The vSnap password needs to 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 in to the system. Now you might rerun the job that failed as a result of the problem.

Limitation: Since V10.1.2. Added in IBM Documentation, see IT27300.
 

First entries in lists automatically display in menus that use Microsoft Edge (internal reference #SPP-9354)
Problem: When you select options from drop-down menus in IBM Spectrum Protect Plus, the first entry in a list automatically displays in the menu that uses 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 that use the Microsoft Edge browser.
Workaround: None.
Limitation: Since V10.1.4. Solved with V10.1.5.
 


 


Limitations solved with V10.1.4

In IBM Spectrum Protect Plus, when a data center is associated with an SLA, the number of backed up VMs might be more than the number of VMs in the data center (internal reference #SPP-8509)
Problem: An NFS volume can be mounted to any number of data centers in the same vCenter. When an NFS volume is mounted on more than one data center on a vCenter, even though vCenter treats the same volume as two different data stores, IBM Spectrum Protect Plus treats this single data store and combines all the VMs and VMDKs residing on this data store from all the data centers this data store is mounted on. Therefore, any SLA selection or resolution against this data store causes all the VMs from the different data centers to be backed up.
Workaround: None.
Limitation: Since V10.1.1. Solved with V10.1.4, see APAR IT30102.
 

Automatic VADP proxy update fails when you upgrade IBM Spectrum Protect Plus V10.1.2 to V10.1.3 or V10.1.3 to V10.1.4. (internal reference #SPPSUP-1129)
Problem: When you upgrade IBM Spectrum Protect Plus, the VADP proxy is automatically upgraded. If you upgrade from V10.1.2 to V10.1.3 or V10.1.3 to V10.1.4, this upgrade fails 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 about manually updating VADP proxies, see Updating VADP proxies.
Limitation: Since 10.1.2. Solved with V10.1.4.
 

The EULA cannot be displayed when you upgrade vSnap (internal reference #SPPSUP-707)
Problem: When you upgrade 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<file name> .run     
sudo bash 

 Where <file name> is the name of the vSnap upgrade file
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 preceding step
Limitation: Since V10.1.2. Solved with V10.1.4, see APAR IT28244.
 

SLA filter drop-down appears only after searching on backup selection screen. (internal reference #SPP-6571 & #SPP-5913)
Problem: The SLA filter drop-down under the VMware backup screen does not appear until you search in the backup selection.
Workaround: Search * in the search bar and the SLA filter drop-down appears.
Limitation: Since V10.1.3. Solved with V10.1.4.
 

Failure to access vSnap server for catalog restore after you upgrade from V10.1.2. (internal reference #SPP-6690)
Problem: On Physical vSnap servers, after you upgrade from V10.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. Solved with V10.1.4, see APAR IT30071.
 

Web user interface stuck with the message “Server is being brought up”. (internal reference #SPP-6698)
Problem: Under rare circumstances, when you try to connect to the web user interface to deploy an IBM Spectrum Protect Plus server, the web user interface doesn’t progress past the message:

 Server is being brought up. Please wait…

Workaround: Reboot the IBM Spectrum Protect Plus server appliance.
Limitation: Since V10.1.3. Solved with V10.1.4, see APAR IT30104.
 

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 is 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. Solved with V10.1.4.
 

Test Restore Jobs disappear after a vSnap upgrade (internal reference #SPP-6052)
Problem: Restore Jobs in test mode disappear when you upgrade 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. Solved with V10.1.4.
 

When you create a custom Resource Group, there is no option to add resources through the Tags & Categories view type (internal reference #SPP-1874)
Problem: When you create 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. Solved with V10.1.4.
 

SQL server databases with non-ASCII characters are not available for Backup Selection. (internal reference # SPP-6059)
Problem: If an SQL server has databases with non-ASCII character names, the inventory job for that SQL server completes but the job log has 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. Solved with V10.1.4.
 

Restoring IBM Spectrum Protect Plus Db2 data to an alternative instance on the original host (internal reference #SPP-6709)
Problem: When you are restoring a Db2 resource to an alternative 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 that uses the restore to alternative instance option.
Limitation: Since V10.1.3. Solved with V10.1.4.
 

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 pane. 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 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. Solved with V10.1.4.
 

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

Exchange application server configured in a DAG environment failed to resolve cluster host (internal reference #SPP-6455)
Problem: When you register 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 log warning messages as following:

Failed to resolve cluster host xxxxxx to an application server

The warnings occur for each application server in the DAG that is not registered at the time that the discovery process is running.
Workaround: Register all Microsoft Exchange servers in the DAG or you can ignore the warnings if you do not plan to use IBM Spectrum Protect Plus to protect the not registered Microsoft Exchange servers.
Limitation: Since V10.1.3. Solved with V10.1.4.
 

Exchange application server configured in a DAG environment job log contains warnings (internal reference #SPP-6539)
Problem: In a Microsoft Exchange DAG environment, during the Application Discovery process the job log contains following warning messages:

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. Solved with V10.1.4.
 

Full base backups occur after storage vMotion operation (internal reference #SPPSUP-237)
Problem: Incremental backups are not run after a storage vMotion operation occurs to a new data store. Backups that occur after the storage vMotion operation runs as full base backups.
Workaround: none
Limitation: Since v10.1.1. Solved with V10.1.4
 

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 like following message:
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 before you start a restore operation
Limitation: Since V10.1.3. Solved with V10.1.4.
 

Readme file for installation procedure on remote server needs to 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. Microsoft recommends installing Outlook 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 file is packaged with the product, we provide here the correct readme file:

  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 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 run once. Once the granular restore package is installed, you can continue to use it to run later granular restore operations.

    1. Copy granular restore package from the Application Server to the remote server where you 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 run 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 might need to add trusted hosts to the Exchange Server and server where the MMC GUI is 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 runs 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 more 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. Solved with V10.1.4.
 


 


Limitations solved with V10.1.3 and V10.1.3_patch1

Back up and restore operations in IBM Spectrum Protect Plus V10.1.2 fail after you run a catalog restore of a 10.1.1-based snapshot (internal reference #SPP-4560)
Problem: If an IBM Spectrum Protect Plus V10.1.1 catalog snapshot is used in a catalog restore job in an IBM Spectrum Protect Plus 10.1.2 environment, all backup and restore jobs following the restore operation fail.
Workaround: A script that is available on the virtual appliance must be run if an IBM Spectrum Protect Plus V10.1.1 catalog snapshot was used to restore an IBM Spectrum Protect Plus V10.1.2 appliance. After the catalog restore job is completed, run the following procedure on the IBM Spectrum Protect Plus V10.1.2 virtual appliance on which the restore operation was run.

  1. Log in to the IBM Spectrum Protect Plus V10.1.2 virtual appliance and open a command line interface.
  2. Enter the following command:
    sudo bash
  3. Enter the following command:
    rpm -q --scripts spp-db| grep -A7 -P '# safe to run on every update' | sed 's#\$RPM_INSTALL_PREFIX#/opt/ECX#g' > /tmp/fix.sh; bash -x /tmp/fix.sh

After the script is run, backup and restore operations is functional in the IBM Spectrum Protect Plus V10.1.2 environment.
Limitation: Since V10.1.2. Solved with V10.1.3.
 

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

Upgrading to IBM Spectrum Protect Plus V10.1.2 fails if an emergency fix (efix) was applied to V10.1.1 (internal reference #SPP-4750)
Problem: If an emergency fix (efix) was applied to IBM Spectrum Protect Plus V10.1.1, the following error displays in the administrative console when you upgrade to V10.1.2:

Subscription Errors Encountered: Errors encountered while updating IBM Spectrum Protect Plus 500 - Internal Server Error

This issue applies only if fixes in the .rpm format were installed directly on the IBM Spectrum Protect Plus virtual appliance by 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 V10.1.1 virtual appliance: 

rpm -qa | grep spp

If an efix is installed on the system, it is 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 V10.1.1 virtual appliance: 

rpm -e spp-efix

Once complete, run the IBM Spectrum Protect Plus V10.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 might be aborted before the operation is completed. Data that is transferred before the timeout threshold is met are 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 use local vSnap fail (internal reference #SPP-1000)
Problem: When a catalog is restored from a backup, jobs that were use local vSnap storage fails 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 is restored to the same or new IBM Spectrum Protect Plus appliance. External vSnap servers can be reregistered 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 can fail with a timeout error (internal reference #SPP-1274)
Problem: In a Linux environment, run a VMware-based file restore operation on files larger than 2 GB can fail with the following error:
"Timed out (300 seconds) waiting for command to complete."
However, in some cases, larger file restores complete successfully, the chances of failure increase for files larger than 2 GB.
Workaround: A hot fix is 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 is 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 appear in the Backup Storage list with its status listed as "Not Connected". However, the ability to edit the Backup Storage registration is disabled.
Workaround: If users are deleted or having their access revoked, edit the Backup Storage registration in IBM Spectrum Protect Plus and specify the new credentials before you delete 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 offload of virtual machine templates, you must specify VMENABLETEMPLATEBACKUPS in the data mover option file. A backup of a template can be run only 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, #SPP-1820)
Problem: When you run a backup operation of 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 might 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 domain name server information or by adding appropriate entries in the /etc/hosts file. 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 needs to 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 an SQL Restore job is in progress and the user clicks Cancel, data and log files continue to be restored. Canceling an 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 an SQL server, Inventory jobs associated with the SQL server fail (internal reference #SPPL3-804, #SPP-2107)
Problem: Running an Inventory job on an 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.
 

An SQL database backup with log backup enabled fails when runs against a restored SQL database with an underscore in its name (internal reference #SPPL3-806, #SPP-1499)
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 logged back up 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.
 

IBM Spectrum Protect Plus operations fail that uses default Russian Windows administrator accounts (internal reference #SPPL3-330, #SPP-1695)
Problem: IBM Spectrum Protect Plus operations such as backup of a virtual machine or running file cataloging fail that uses the default Russian Windows administrator account,
Workaround: The account used for IBM Spectrum Protect Plus operations must use English characters.
Limitation: Since V10.1.1. Solved with V10.1.3.
 

The latest incremental backup data is not purged after you run the maintenance job to expire the data (internal reference #SPP-1121)
Problem: When an SLA Policy is defined with vSnap replication, the latest incremental backup data is not purged after you remove the backup job instances and you run the maintenance job to expire the backup data.
Workaround: This behavior occurs when SLA Policy settings are such that the primary backup retention is smaller than the replication frequency. The snapshot is locked and cannot be expired because it is needed for the next incremental replication sync. Once the replication sync occurs, the old snapshot is unlocked and is expired.
Limitation: Since V10.1.1. Solved with V10.1.3.
 

Report categories display when a user does not have access to the reports within the category (internal reference #SPPL3-821, #SPP-1605)
Problem: When no reports from a category are available to a user through their assigned resource group, the category still displays in the Report pane. The category can be expanded, though there are no reports available.
Workaround:  None.
Limitation: Since V10.1.1. Solved with V10.1.3.
 

File names that contain the “|” character are not returned when you run a file search in a Linux environment (internal reference #SPPL3-393, #SPP-1751)
Problem: In a Linux environment, when you search for a file that contains the “|” character in its file name, the file either does not display in the search results, or the file name is split between the file name and path fields.
Workaround: Searching for a file that contains the “|” character in its file name is not supported in a Linux environment.
Limitation: Since V10.1.1. Solved with V10.1.3.
 

When you update IBM Spectrum Protect Plus to V10.1.1, the unzip .rpm is not updated (internal reference #SPP-1300)
Problem: When you update IBM Spectrum Protect Plus from V10.1.0 to V10.1.1, the unzip .rpm, which is included in the update ISO, is not updated to the latest version.
Workaround: To resolve, execute the following procedure:

  1. Update the IBM Spectrum Protect Plus appliance through the administrative console by using spp-10.1.1.iso. For more information about updating your appliance, see the installation and user's guide.
  2. Once complete, transfer the spp-10.1.1.iso file to the /tmp directory on the IBM Spectrum Protect Plus appliance.
  3. Through the command line interface, create a new directory for the ISO mount through the following command:
    mkdir /mnt/update
  4. Mount the ISO through the following command:
    mount -o loop /tmp/spp-10.1.1.iso /mnt/update
  5. Run the following command to update the unzip .rpm:
     yum localupdate /mnt/update/Packages/unzip*
  6. Unmount the ISO through the following command:
    umount /mnt/update
Workaround:  None.
Limitation: Since V10.1.1_patch1. Solved with V10.1.3.

 

After offload completes, the offloaded snapshot does not display on the system > catalog > retention page (internal reference #SPP-2447)
Problem: When an SLA Policy is defined to include offload to IBM Spectrum Protect, the offloaded snapshot does not display in the IBM Spectrum Protect Plus interface under system > catalog > retention. Retention for offloaded snapshots is not handled through IBM Spectrum Protect Plus, but by the associated VE server. Offloaded snapshots not display in the IBM Spectrum Protect Plus retention interface.
Workaround:  None.
Limitation: Since V10.1.1_patch1. Solved with V10.1.3.
 

Restores to an alternative 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 alternative 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 alternative 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 is reported in job log for that backup job instance. Back up 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 end 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 or 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 you set up a Hyper-V restore job and saving it with the wanted Advanced Options selected, the option selections are not preserved when you edit the restore jobs.
Workaround: Make your option selections again before you rerun 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 use NBDSSL and LIBZ compression fails (internal reference #SPP-2634)
Problem: When you run 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 affects only 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 when that uses IBM Spectrum Protect Plus. The feedback form requires an internet connection to capture feedback, but the pop-up window 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, #SPP-1533)
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 files restore jobs simultaneously.
Workaround: Ensure that no other operations are occurring on a virtual machine while you restore 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 need to 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 stand-alone SQL database and a database that is part of an SQL Always On Availability Group are protected through the same SLA policy, and the databases are 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 stand-alone 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 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, #SPP-1987)
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 reassign 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 wanted.
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 use both NTFS and CSVFS formatted drives, the job fails with an error indicating that the mount point is inaccessible.
Workaround: Ensure Hyper-V backup jobs do not include drives that use both NTFS and CSVFS formats.
Limitation: Since V10.1.1. Solved with V10.1.2.
 

A Hyper-V restore operation running in production mode fails if the original source is not overwritten (internal reference #ECC-12235, #SPP-48)
Problem: In a Hyper-V environment, if an attempted restore running in production mode fails to overwrite the original source, the restore fails with a HypervisorVMDeleteException error.
Workaround: You must manually delete the source VM through Hyper-V Manager, then manually resume the restore job in IBM Spectrum Protect Plus.
Limitation: Since V10.1.0. Solved with V10.1.2.


 


Limitations solved with V10.1.1 and V10.1.1_patch1

Virtual machine backup jobs fail after you run a catalog restore (internal reference #SPPL3-724, #SPP-2166)
Problem: After you restore the catalog through a catalog Restore job, certain virtual machine backup jobs fail.
Workaround: For releases before the patch1, the workaround is to create new SLA policies for each backup job that fails to follow 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 you update IBM Spectrum Protect Plus by using Firefox, the Clean Process appears to fail (internal reference #SPPL3-833, #SPP-1808)
Problem: When you update IBM Spectrum Protect Plus through the administrative console by using Firefox, a Clean Process Failure message displays during the update process. The message indicates that the update is applied successfully, but the update cleanup process failed.
Workaround: This message appears consistently when you 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 before 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.
 

Back up and restore operations for SQL Server system databases are not supported (internal reference #SPP-1332)
Problem: Back up 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 before 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 execute 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 can 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 before 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.
 

An SQL restore of data and log files that are in the same path to an alternative 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, an SQL restore of data and log files to an alternative location restores the files to the data file location.
Workaround: For releases before 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 an SQL Failover Cluster Instance fails with a writer error (internal reference #SPP-1270)
Problem: A database or point-in-time restore of an SQL Failover Cluster fails with the following error:

Writer [SQLServerWriter] report error status ([VSS_WSS_FAILED_AT_PRE_RESTORE])

Workaround: For releases before the patch1, when the automount option is disabled on an 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 you select sources at the data store cluster level (internal reference #ECC-12266)
Problem: When you create a backup job definition, the IBM Spectrum Protect Plus interface supports selecting sources to back up at the data store cluster level; however, the backups 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 data stores 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 you delete 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, #SPP-244),
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 local time 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

To see the time zone change, execute:

ls -l /etc/localtime

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 operation by using the production restore type does not preserve the path of the original volume (internal reference #SPPL3-190, #SPP-2205)
Problem: When you restore a Hyper-V virtual machine to the original host by 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, #SPP-1870)
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 source volume C]
Unprotected vm: YYYYY [Failed to format volume. Disk: 39, partition: 2]

Workaround: For releases before 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, #SPP-1931)
Problem: Log truncation might fail for a backup job, when the SQL log truncation option selected. This behavior 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 following message does not appear:

Successfully truncated logs for <vm_name>

Workaround: For releases before 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 run an 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, #SPP-2123)
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 through file discovery. Therefore, 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, #SPP-1748)
Problem: When you run 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 before 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. The file must be restored to an alternative location in this instance, then copied to the wanted 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, #SPPL3-252, #SPP-1643, #SPP-1825)
Problem: A user is unable to access the IBM Spectrum Protect Plus administrative console through port 8090 after installation.
Workaround: For releases before 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, restart 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 remove the previous recovery points from IBM Spectrum Protect Plus.
Workaround: For releases before 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 or Clone mode restore (internal reference #SPPL3-270, #SPP-1882)
Problem: When you restore a virtual machine through a Test or 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 you attempt to run file cataloging.
Workaround:
For releases before 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 starts 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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSNQFQ","label":"IBM Spectrum Protect Plus"},"ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
16 July 2021

UID

ibm16427925