Backup exec 11d with Sharepoint Portal module

[PeterKonstek]

Hi all

I have installed 11d on a clients server, and added the sharepoint portal licences. Here is the spec

Server 2003 x64

BE 11d

Sharepoint 3.0 - Installed as a farm runing SQL 2005 workgroup edition.

SO i have installed it all, and trying to add a farm and it cant find it..

I have run the Debug monitor and here are the messages.

BEREMOTE: [11/10/07 07:41:48] [5052] FS_ResolveDevName: [Server Farm 1 (SERVER)]
BEREMOTE: [11/10/07 07:41:48] [5052] MB2-Resolve returned 1
BEREMOTE: [11/10/07 07:41:48] [5052] Notes Agent:CLNFileSystem::ResolveDeviceName
BEREMOTE: [11/10/07 07:41:48] [5052] ENTER DPM::ResolveDeviceName
BEREMOTE: [11/10/07 07:41:48] [5052] deviceName: [Server Farm 1 (SERVER)]
BEREMOTE: [11/10/07 07:41:48] [5052] DPM: Device NOT claimed
BEREMOTE: [11/10/07 07:41:48] [5052]  EXIT DPM::ResolveDeviceName return=[0x1 S_FALSE]
BEREMOTE: [11/10/07 07:41:48] [5052] ADC_ResolveDeviceName: pid = 4360, checking Server Farm 1 (SERVER)
BEREMOTE: [11/10/07 07:41:48] [5052] GRFS_ResolveDeviceName deviceName Server Farm 1 (SERVER) osId 0
BESERVER: [11/10/07 07:41:48] [4836] -1 Client requested key (1192059865).
BESERVER: [11/10/07 07:41:48] [3344] 01 UpdateDynamicInfo: cluster open unsuccessful.
BESERVER: [11/10/07 07:41:48] [3344] 01 Server Configuration: Client added: 6
BESERVER: [11/10/07 07:41:48] [3344] -1 Client 'SERVER' connected('','WRMCWA\peter'): 0x96f0cd0
BEREMOTE: [11/10/07 07:41:48] [5052]  machine name = SERVER
BEREMOTE: [11/10/07 07:41:48] [4440] This server is NOT an SPS webserver
BEREMOTE: [11/10/07 07:41:48] [4440] This server is NOT an SPS webserver
BESERVER: [11/10/07 07:41:48] [4836] 01 Server Configuration: Client removed: 5
BESERVER: [11/10/07 07:41:48] [4836] -1 Client 'SERVER' Disconnected:0x96f0cd0

This server is NOT a SPS webserver!!!!  huh... ok fair enough then, so the 40 clients hanging off it are all blind!! 

I have looked into this, and another guy has had some luck by changing IIS settings to assign the IP address the site it on, add some hosts records, and i have tried that and no luck. Its almost as if there needs to be a registry setting change to let BE know that it is a sharepoint server.

Any help would be greatly appreciated as Symantec support is crap...

Thanks in advance

[Michael_Ellis_2]

Search the Symantec site for a registry hack to enable logging.  Enable the logging by restarting your remote agents.  Run logging on your WSS and Web Frontend boxes.  Attempt to discover your farm then after your access denied error open your SPSWrapper log on the WFE and WSS server.

Do you have an error simular to this?  If so your are screwed because I have had a ticket with support for almost three months with no resolution :(

Good Luck!

[3a08] 10/11/07 10:02:28    Exception !!
System.ArgumentException: An item with the same key has already been added.   at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)   at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)   at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)   at SPSManagedWrapperHelper.Utility.GetSPIndexLocations()   at SPSManagedWrapperHelper.SpsManagedWrapperV3.b(SPBackupRestoreObject A_0)   at SPSManagedWrapperHelper.SpsManagedWrapperV3.GetBackupRestoreObjects(SPBackupRestoreObjectCollection list)   at SPInteropClass.BuildLists()
[3a08] 10/11/07 10:02:28 Reply buffer for the Get Topology(0x00000001) command.
[3a08] 10/11/07 10:02:28   Status: 0x00000bf1
[3a08] 10/11/07 10:02:28   Waiting for Reply Empty Signal...
[3a08] 10/11/07 10:02:28   ...reply emptied

[MrBuskin]

Check out https://forums.symantec.com/syment/board/message?board.id=115&thread.id=20681

[Michael_Ellis_2]

When you try to add the farm try both the web server and if that fails point to the SQL server.  The problem seem to be with multi-server installations.  If you install it on a single server and use MSDE on that same server it should work, but is not very realistic.

[Mikegyvr]

One would think that fixing this would be a high priority for Symantec.  Talk about false advertising making for some large sales...

Yes,  having the same problems...

Is anyone having VSS failures on their web front-ends?  I am suspecting that known issues with VSS and MOSS/WSS3 may be related.  Just trying to begin validation of the idea...  There is an MS hotfix for VSS on MOSS/WSS3 out there, but I have not tested it for production use yet.

[Michael_Ellis_2]

The topology I have been using for troubleshooting is very simple.  All of the SharePoint services are installed on one server.  All SharePoint databases are located on a backend SQL 2005 server.  I have run the Surface Area Configuration Tool for SQL 2005 and opened/allowed pretty much everything.

My production farm is more complex and traffic passes through firewalls.

[Michael_Ellis_2]

I do not have any VSS errors on either my troubleshooting farm or my production farm.