Release Notes - Service Pack 13

Whether you are installing this software for the first time, or upgrading from a previous version, please note these important considerations.

Downloading the Service Pack

Obtain the latest major service pack using the CommCell Console. For instructions, see Getting Started - Download Updates.

If you are unable to download the service pack using the CommCell Console, download the service pack from the Cloud Services Web site. For instructions, see Downloading from Cloud Services.

Installing the Service Pack

To install the service pack on the CommServe, MediaAgent, and client computers, see Getting Started - Install Updates.

Known Issues

SQL Server 2012 and 2014 Log Restores to a Database in a Stand-By State May Fail

SQL Server log restores to a database in the stand-by state are affected by a Microsoft issue. Refer to Microsoft Support article Restore Log with Standby Mode on an Advanced Format disk may cause a 9004 error in SQL Server 2008 R2 or SQL Server 2012. As a workaround, perform restores of database and transaction logs using the NORECOVERY option.

Edge Drive Upload Not Supported on Bitlocker Enabled ExFAT volumes

Data residing on Bitlocker enabled ExFAT volumes cannot be uploaded to Edge Drive. As a workaround, reformat the volume to NTFS.

Service Pack Updates Might Fail If Applications are Running

On computers running the Explorer Plugin, the installation of updates might fail with the message “Failed - Applications are locking files to be replaced [Refer UpdateInfo.log on client for more details]. Reboot client for successful completion of update install in next attempt.” This error is caused by running applications using the Explorer Plugin, preventing updates. To work around this issue, restart the computer, then run Install Updates again.

Increase in Backup Time after Fix for VMware CBT Error for expanded VMDKs (Service Pack 9 and later)

SP9 provides a crucial fix to prevent data loss. As a result of applying this service pack, the time and disk space for backups is increased.

After a virtual machine disk (VMDK) is expanded beyond 128 GB or any doubling of 128 GB, VMware ESXi 4.x or ESXi 5.x can return incorrect information about virtual machine disk sectors, and Changed Block Tracking (CBT) can produce unrecoverable backups. This is a flaw in VMware APIs used by backup software, and can lead to data loss if not addressed immediately.

For Service Pack 9 and later, the Simpana software automatically detects expanded disks and resets CBT. As a result, the following actions are taken:

  1. The first backup job resets CBT for all virtual machines with a disk size greater than 128 GB. The CBT Status for the affected virtual machines is displayed as Reset.
  2. The software stores the size of each VMDK file in the .vmx file for each virtual machine.
  3. For any backup jobs going forward, the backup job compares the current size of each VMDK file with the size recorded in the .vmx file.
  4. If a disk has been expanded, the software resets CBT and backs up all blocks for the virtual machine's VMDKs.

As a result of resetting CBT, the time required for backups increases because the first backup after resetting CBT backs up all blocks for any virtual machines on which CBT was reset. This change can also increase disk storage requirements for backups. The change does not affect scheduled backup cycles or data aging.

For more information, see KB Article VMW0009: VMware CBT Error for expanded VMDKs.

Communication Through a Firewall with Upgraded Version 8.0 Clients

Effective with Version 10 Service Pack 9, client firewall software configurations must be compatible with Version 10. For more information, see Firewall - Getting Started - Overview.

Block Level Backup

Browse from backup set level fails. As a workaround, on the Browse and Restore Options dialog box, click the Advanced Options tab, and select the local MediaAgent from the Use MediaAgent list.

Change in PostgreSQL Dump Format

A PostgreSQL pipe-based native dump backup in compressed format on the Windows platform results in corrupt backup data. This causes the restore operation performed from the dump to fail. To address this issue, the PostgreSQL dump output format has been changed in SP11 from a compressed format to the uncompressed TAR format. After you install SP11 or later, run fresh backup jobs so that the backup data can be successfully restored. To achieve better performance for dump based backups, enable SnapProtect compression. For more information, see Data Compression - Overview.

Proxy Computer Requirements for Fpolicy (Simpana OnePass for NetApp)

Your proxy computer for Simpana OnePass for NetApp must be Windows XP 64-bit or later. If the proxy computer runs on Windows XP 32-bit version or earlier, do not upgrade to Version 10 Service Pack 12 or later.