Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Exchange Problem CV 6.1

Status
Not open for further replies.

AFStorageTech

IS-IT--Management
Sep 3, 2008
26
US
Morning,

This issue I have as been troubling me for the last three weeks and I still can't find a solution. I have a base that is trying to upgrade from 6.1 to 7.0, but before we get to do that we had to recreate a new backup server due to space issues. When we had everything looking the same as the old server, one of my exchange servers started to error with this statement on the Database backup:

The operation cannot be completed as the host is offline.

I have looked at the services on this server, rebooted the server, made host files and still nothing. I dont know what else to do.

I need help asap as this server has not been backed up for more than a month and if something happens the General will not like it.

Thanks
 
Worse case and assuming Exchange 200/2003 and not 2007 just use NTBackup to do an Exchange Aware backup to get the databases backed up to disk and get the logs purged.

After a month just get a backup then worry about the Commvault bits IMO.
 
There isn't much info in your post but based on what you've described it looks like some names might be pointing to the wrong place (or DNS isn't correctly mapping to one or more addresses).

Suggest you start by looking in the CV GUI - right click the client (not the agent or sub-client) and carefully note the fully qualified domain name (FQDN) of the client. Then on the CommServer (CS) and Media Agent (MA), start a DOS prompt and type in "NSLOOKUP <that-FQDN>". Note the address that comes back, then check the reverse lookup (which MUST also work): "NSLOOKUP <address>" - this should give you the original FQDN back again.

Then on the client, start a DOS prompt and do an NSLOOKUP of the FQDN of the MA and CS and check their reverse lookups too.

If all that still looks OK, check the CV logs for a failed job. They're chock-a-block with far too verbose info which should indicate where it's failing.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top