Bug

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's like to install software via Active Directory it may fail with Error: %%1274.

Symtoms:

• You can reboot as often as you'd like and your deployed Software always fails with Error %%1274
• Eventlog entry:
  • Source: Application Management Group Policy
  • Event ID 101
  • Description: Die Zuweisung der Anwendung ShoreTel Communicator 16.23.5631.0 der Richtlinie ShoreTel Communicator ist fehlgeschlagen. Fehler: %%1274
  • Description: The assignment of application ShoreTel Communicator 16.23.5631.0 from policy ShoreTel Communicator failed. The error was : %%1274

Workaround:

• Explicitly set the policy Startup policy processing wait time: Activated Amount of time to wait (in seconds): 120s. This is normally not required if FastLogonOptimization is disabled, but Windows 7 seems to have a bug here.

History:

• 04/09/2011: Exists in Windows 7 RTM and SP1
• 13/04/2011: Implemented Activated Amount of time to wait workaround.

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:

Mid January 2011 we found a bug in Commvault's Exchange Public Folder Archiver. This bug prevented us from restoring items that have been archived in past. It was a bit random, but my feeling was it is related to mails with attachments. As always supposed, it was not an issue of the MAPI connection configuration or other issues on our side. This is a Commvault bug and nothing else.

Required:

• Commvault Simpana 8.x
• Commvault Simpana 9.x

Symtoms:

• Archived public folder items cannot restored.
• Mails with attachments have mostly failed.
• User received very unspecific error message from Commvault Archiver Add-on in Outlook.

Solution:

This issue describes symptoms that occur for ages with HP Data Protector and that may become a critical issue for your if you don't see them. There will be no notification from DP at all if this happens. The main cause of these bugs seems to be very unreliable internally error handling process in Data Protector. I personally see this for many years now and nothing get's really better over time in these product if you don't stress your bugs.

Symptoms:

• Job is running and cannot killed. You can try to kill it 1000 times and you can wait days for the kill, but it never get's killed.
• Planned backup jobs with same job name are not running any longer as DP is waiting for the hanging job to finish.
• Restarting all Data Protector services will not kill a job.

How to identify:

If you are one of the HP DataProtector 6.11 customers and you have scheduled MsSQL transaction log and full backup to start simultaneously you will experience the below issue. We found this after an upgrade to latest 6.11 in November 2010 and a hotfix was build for us on 19. November 2010. We are running with this patch for 8 weeks successfully.

Cell Manager patch level:

Client SQL Server patch level: