A little while back I came upon an issue where a customer was using the Backup Exec agent for SharePoint 2007 and experiencing an error message when adding a MOSS farm to the backup selection. The error message you receive is:
An error was encountered while attempting to browse the contents of SiteName (xx)\Content-DB 1 (SQLServerName\SQLInstanceName\DatabaseName). A network connection to the server could not be established.
The error occurs if you use Parentheses () in your web application names. Further details are provided in the following article: http://seer.entsupport.symantec.com/docs/294620.htm
In other words if you have a Web Application called “SharePoint (MySite)” and one called “SharePoint (Portal)”. Backup exec will not back this up.
Symantec claim this issue is fixed with the release of version 12.5 of Backup Exec.
A SharePoint Blog with a difference...well actually not that different but hopefully still useful
Thursday, 3 July 2008
Wednesday, 2 July 2008
Interesting points from the SDPS Deployment and Customisation Plan
Just been reading through the SDPS Deployment and Customisation Plan and picked up on the following stuff. Just wondered how many people are doing this already? I always make the SSP service and SSP App Pool identity separate accounts and was not aware of disabling NetBios over TCP/IP on WFE’s and Index Servers.
- SSP App Pool Identity and Service account recommended to be the same account
- NetBIOS over TCP/IP (NetBT ) support should be disabled on all network cards on the Web Front End and Index servers.
- Avoid more than eight Application Pools per farm
Subscribe to:
Posts (Atom)