Simpana 9.x

If you are installing a CommCell Console GUI on your Administrator PC it normally download and installs all patches from the CommCell Server to the client. You do not need to do anything manually, but with this bug these feature is more or less broken.

Symptoms:

• CommCell Console GUI 9.x SP3 is not installing patches at all.
• CommCell Console GUI starts up and update dialog is shown. After you press Yes for installing the patches, nothing at all happens and patches are not installed.

Reason:

• Upgrade logs complain about some missing dependencies that are not fullfilled. Looks like the patch references table on CommCell is broken again and missing required references.

Solution:

• Upgrade your CommCell from SP3 to SP3a

History:

If you are running Simpana 9.0 SP2a and you backup Windows 2003 servers they are no longer backed up after you have installed SP2a. There is no notice or warning at all. You will not get an email if the job has failed to backup your data. Hopefully you have no data loss before you came aware of this bug...

Symtoms:

• Windows 2003 machines are not backed up. Windows 2008 or Windows R2 is not affected.
• Alert system does not notify you about the data backup failure.
• It does not matter if you use VSS or not.
• It does not matter if you have selected some files or all files for backup.
• Only the Commvault Jobs folder and SystemState is backed up.

Solution:

Commvault has an Exchange public folder archiver and you are running it to get your public folder store size reduced.

If you are running Simpana 8.0 you should be aware that all written public Commvault documentation has told by fault that Exchange 2010 is suppported, but it wasn't. This wrong documenation was public until Oktober 2010 and has been removed in a "cloak-and-dagger operation" with my support call. We banged on this migration wall while moving from Exchange 2003 to 2010 and have been made by Commvault to wait for Simpana 9.0 SP1 that came available in mid January 2011. Because of so many bugs in the product we have been made waiting until mid May 2011 (SP2). You may be working with Exchange 2010 since November 2009 and you may have just waited for Exchange 2010 SP1 that has been released in June 2010 to get a more stable Exchange 2010 and to finish migration.

You may have just upgraded from Simpana 8.x to Simpana 9 SP2 or later and installed the Exchange DA Client on your Windows 7 client (x64) or Windows XP. Outlook is x86 version and Simpana 9.x Outlook Addin (MSI).

The Commvault documentation Install Using AD Group Policies just tell you in the last sentence that you need permission to Galaxy.Ex2KMBDM.CVEAAddin key. That sounds like a bad joke as it does not explain that you cannot set this value with a GPO together with the installation GPO and also not with two GPOs ordered one after the other (what Support suggested). The setup removes all it's registry keys and reinstall them later (also on updates over existing versions). To apply the permissons on the registry keys and folder you need to reboot the machine after the setup has been completed. But the setup does not reboot itself as there have been no files in use that require a reboot. Now, try to explain this reboot requirements to a few hundred users...

If you are installing a CommCell Console GUI on your Administrator PC it normally download and installs all patches from the CommCell Server to the client. You do not need to do anything manually, but with this bug these feature is more or less broken.

Symptoms:

• CommCell Console GUI before 8.x SP4 is not installing patches on Windows XP at all.
• CommCell Console GUI with 8.x SP4 installed fails to upgrade to SP5.
• CommCell Console GUI starts up and update dialog is shown. After you press Yes for installing the patches, nothing at all happens and patches are not installed.

Reason:

• Proper UAC (User Account Controll) logic implementation seems missing for Windows Vista and Windows 7 in Simpana 8.x and 9.x. By Microsoft certification rules the product is therefore not certified for Vista / Windows 7.
• Auto-Upgrade often fails to install other required patches

Workarounds: