WSS 3.0 Backup
We execute a backup using the sts command. stsadm -o backup -directory \\%COMPUTERNAME%\TFSSharePointBackups -backupmethod fullWe see that this backup process actually creates SQL .bak files, for example \\%COMPUTERNAME%\TFSSharePointBackups\spbr0000\0000000E.bakAfter logging into the SQL Embedded DB \\.\pipe\mssql$microsoft##ssee\sql\query using SQL Server Management Studio Express, we can see that the WSS_Content backup references the 0000000E.bak file.I've tested restoring this WSS Content DB to a new installation of WSS 3.0 and everything seems good.Is there any reason we shouldn't use this as a backup strategy?I haven't found any posts about doing it this way but from what I can tell everything is working.
February 13th, 2010 1:19am
that backup is fine to use. I would just caution you that you need to backup all your sql database periodically
February 13th, 2010 1:48am
Just note that its fine to be used for content databases backup and restore. However, for Farm level recovery, especially for configuration database recovery, you should follow more complicate procedure to stop the farm before backup or use tools such as Microsoft System Center Data Protection Manager 2007. For further information, please refer to http://technet.microsoft.com/en-us/library/cc287880.aspx
February 15th, 2010 10:35am