Note: The SharePoint plug-in is not supported in V7. For documentation detailing how to back up SharePoint in V7, visit the Partner Area.
Click Edit User Information.
Select the Site collection administrator checkbox and click Save and Close.
Navigate back to the first page (by re-entering the page name directly into the address bar) to confirm that the settings are correct.
Depending on the level of security on your SharePoint server’s SQL instance, you may need to assign permissions to the service user within SQL. Using SQL Management Studio, you need to give the user the "db_owner" role for the SharePoint Config database and the SharePoint Site database. These can be found in the Users table under Security.
SharePoint Config database:
SharePoint Site database:
Add the backup service user to each database, and ensure that "db_owner" is selected as shown below.
In the registry, grant the user read access to LocalMachine\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\. Without this permission, errors will occur.
The user also needs full control of the SharePoint dump directory, but this permission will be inherited for the default path if Full Control is specified for the Attix5 Pro directory.
The SQL service needs full control of the SharePoint dump folder (the user for this is will be either "Local System" or "NETWORK SERVI" by default).
Typically, the installation should display something similar to this:
Note: The details populated into the plug-in are taken from the registry key at LocalMachine\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\Secure\ConfigDB\dsn.
SharePoint should appear in the Backup Selection tab.
Browse through the available nodes and select the items that you want to back up as you would select files and folders in the default Backup Selection tab. After you have made your selection, click the Backup toolbar button to initiate the first backup.
Note on Windows SharePoint Services 3.0
If you are using WSS 3.0 the SQL database will be SQL Server Embedded Edition (SSEE), which will appear in the services list as "Windows Internal Database (MICROSOFT##SSEE)". This version of SQL database is only accessible from the local machine, and is not intended for use as a standalone SQL server. As with other SQL versions, permissions need to be set if using the SSEE.
To connect to SSEE:
The permissions to be set remain the same as above.