09-12-2007 07:56 AM
09-13-2007 12:09 AM
09-14-2007 11:08 AM
09-18-2007 02:41 AM
09-21-2007 12:31 PM
09-26-2007 06:18 AM
09-26-2007 07:39 AM
10-02-2007 05:54 AM
10-02-2007 07:58 AM
"Fortunate" enough to have a support contract with Symantec so have sat though the torturous on old music, flaky telephone line and frustrating phone menu system for the last 30 minutes and logged a "Major" case.
Should have a call back in 8 hours, but its pretty much guaranteed to be outside of any normal humans working hours (you'd think a call centre could conceptualise time zones hey!?).
With a bit of luck within an hour I’ll be able to convince the 1st line support guy I know how to move a mouse and get passed onto someone with some knowledge about the product - I’ll update the thread if I get a solution!
The day Veritas was sold to Symantec was a dark one.
Tom
10-02-2007 11:38 AM
10-03-2007 02:54 AM
RESULT!
I've made some progress in getting towards the root cause of this... without the assistance of Symantec support still awaiting the call back from them! "Major" obviously has a different meaning to me as it does to them!
Short explanation:
Seems to be an issue with having two NICS on different IP's with IIS set to use (All Unassigned).
I've had a fair bit of experience troubleshooting problems with Backup exec, as a result of their terrible support I have had to teach myself to use their advanced troubleshooting and debugging tools.
So I fired up SGMon, the Backup Exec Debug Monitor to try and have a look at the communications between the server front end, the backup exec database and the client on MOSS.
When trying to add the MOSS Server farm I can see the server talking to the database and retrieving its stored record for it. This succeeds.
The Server then attempts to communicate with the client - at this point i noticed it was trying to establish the connection with alternative NIC - x.x.x.200 address instead of the primary NIC x.x.x.89.
The .89 was a manually configured IP while the .200 was DHCP.
Obviously the DNS was issuing the .200 address over the .89 because of the link between DHCP and DNS in Windows server environment.
So I did the following:
1. Went to the MOSS server and disabled the second NIC.
2. In IIS on the MOSS server manually configured the IP address the websites were being served on to the .89 address instead of (All Unassigned)
3. Opened Backup Exec Remote Agent Utility on the MOSS server and enabled Remote Agent Publishing and reduced the Publishing Interval to 5 Minutes.
4. Rebooted the server.
5. On the backup exec server opened the C:\WINDOWS\system32\drivers\etc\hosts file and added lines for the server simple name and the servers FQDN
6. I Ran an ipconfig /flushdns.
7. Restarted the Backup exec server.
After this I was able to add the server farm with a domain admin account and am currently running a backup!
Some of these steps are probably unnecessary - but this is how I got the **bleep** thing working!
I am still not happy with the setup – it is currently working with a Domain Admin User account and not a service account for example, but I will work these issues out as I continue to test.
10-03-2007 04:22 AM
10-03-2007 06:37 AM
10-04-2007 04:54 AM
10-04-2007 05:24 AM
10-05-2007 05:33 AM
10-08-2007 02:21 AM
10-09-2007 04:57 AM
10-09-2007 05:03 AM
10-09-2007 05:07 AM