..after our recent upgrade from MOSS 2007 to SharePoint 2010, we had to re-think about real scenario restoration; balancing compliance with the organizational SLAs.
Never we had a second thought that we should rely on with one kind of backup for our infrastructure. So we bridged 4 kinds of SharePoint backups including real-time replication functionality from third party vendors.
- Backup using SharePoint STSADM command which starts with a script and alerts the completion status.
- SQL Content DB level backups
- SharePoint 2010 content level backups from Symantec Backup Exec
- Real-Time replication to the disaster recovery site using AvePoint's DocAve replicator.
I'm also testing the SQL mirroring which would eventually eliminate the third party applications for replication. The only hurdle is huge database data transfer over MPLS line and fine tuning and enabling proper listner ports. I will shortly achieve that.. anyhow, I'm highlighting below the only issue what we encountered during 3rd party content backup.
Issues and remediation:
using Symantec Backup Exec 2010R3, server farm addition ended up with error: "none of the web servers for the specified server farm could be accessed" 
adding backup exec system account (BESA) to the SP Farm Admin's group and addition of BESA to SharePoint's BE DB server with public and sysadmin privilege sorted the issue.
Sharepoint Farm visible from Backup Exec application
here you can restore a single file, site or anything which went erroneous before the previous backup.
note: make sure you have a valid SharePoint per server license from the vendor.
0 comments:
Post a Comment