Upgrade to R2 issue

[NewAdm]

As of yesterday we were running Server 2003 Standard with SP2 and commvault 6.1 Things were working fine. After upgrading to Server 2003 R2, things are not so fine. Every time I try to launch the console (locally or remote), the commserve service dies and shows "unknown" in the Service Control Manager. I get the error message: unable to connect to commcell, the session will be terminated.

I uninstalled and reinstalled, planning to do a DR restore. It launches ok with a blank database, but after using the GUI DR Restore it does not launch.

Any ideas?

 

[NewAdm]

Just a little more info

When I do a blank DR restore (the one that was generated when I first installed), it launches with no problem. Can the database become corrupted, and are there tools to fix it? Looking at the databases, they are very low on free space.

Help please =)

 

[birky]

Have you tried using an earlier .dmp file through the DRRestoreTool?

 

[NewAdm]

I am attempting to reinstall again and will have to pull an archived dmp file. What could cause corruption?

 

[birky]

It's a db...they can always get corrupted.

There are ways of getting them fixed but, you would have to send the .dmp file off to support for them to fix.

Just try the .dmp file from the previous days DR backup and see if it works.

Make sure when you rebuild the CommServe that you;-
1) Install just the CommServe and nothing else
2) Accept the default settings during the CommServe install for everything

After successfully applying the DR backup then you can install any other agents (eg Media Agent, FileSystem iDA etc).

 

[NewAdm]

Got the issue resolved.
#1. NEVER buy support for commvault through Dell. We spent over 4 hours on the phone before they escalated to CommVault proper. Dell has 1 CommVault support specialist and he does not seem that knowledgeable.
#2 After getting to CommVault the issue was resolved in less than a half hour. The issue was both CommVault's DST patch and Microsoft's DST patch were conflicting. We reinstalled and CommVault gave me a reg fix because I was on the Galaxy version. Hopefully this helps someone.