I am confused by the documentation for backing up a SharePoint 2003 Portal farm with NMM. The docs do not tell me where I need to install and run the client software from. In our farm, we have a stand alone SQL server that has many other databases on it. Do I need to run NMM on that server to backup the SharePoint databases or do I run it on one of the front end servers?
If I am just backing up the databases, why would I do that with NMM as opposed to just using the standard SQL client like we are now?
Any help to clear up my confusion would be appreciated.
We have several SharePoint servers. Our best solution was this, and what we found to be easiest for our needs.
WSS has a built in backup utility. We use these to backup the individual sharepoint sites to a local disk.
We configured our SQL server with a maintenance plan, that backups the databases to disk. Mind you, Sharepoint is in a single SQL database, and all the individual sharepoint sites are inside this single database, (Least my understanding of it.) So we now have SQL maintenance plan dump backups to disk as well. The maintenance plan also deletes backups older than 2 days old. (Same for the WSS backups.)
Networker via the standard client then backups these two directories.
We have had to do sharepoint restores for clients before, and this method has worked flawlessly and given us the least amount of headache versuses using the SQL agent and doing a hot backup of it via that.
Also, it is much easier to restore a site instance using the WSS utility then trying to recover the database back into SQL etc.
HacknDos1
1 Rookie
•
66 Posts
329
0
Posted September 30th, 2009 13:00
WSS has a built in backup utility. We use these to backup the individual sharepoint sites to a local disk.
We configured our SQL server with a maintenance plan, that backups the databases to disk. Mind you, Sharepoint is in a single SQL database, and all the individual sharepoint sites are inside this single database, (Least my understanding of it.) So we now have SQL maintenance plan dump backups to disk as well. The maintenance plan also deletes backups older than 2 days old. (Same for the WSS backups.)
Networker via the standard client then backups these two directories.
We have had to do sharepoint restores for clients before, and this method has worked flawlessly and given us the least amount of headache versuses using the SQL agent and doing a hot backup of it via that.
Also, it is much easier to restore a site instance using the WSS utility then trying to recover the database back into SQL etc.
Last note: we are using WSS 3.0
Thanks
Paul