Event ID 3353 (Windows SharePoint Services health model)

Event ID 3353 (Windows SharePoint Services health model)
Windows SharePoint Services 3.0

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2008-04-27

When you back up a Web site, you back up the content database for the site, including all pages in the site, files in document libraries, files attached to lists, security and permission settings, and feature settings. The backup process creates a single file that contains all of this data. The restore process uses this file to restore the content database for the site. For more information about backup and restore, see Administering backup and recovery for Windows SharePoint Services 3.0 technology (http://technet2.microsoft.com/windowsserver/WSS/en/library/64171b8c-5608-4e69-881a-67996080b7ff1033.mspx) on TechNet.

Event Details  

Product:

Windows SharePoint Services

ID:

3353

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_3353

Message:

Backup failure: insufficient permissions on %1.

Resolve Assign sufficient permissions

Windows SharePoint Services 3.0 could not complete the backup because the account being used does not have sufficient permissions to the backup share. The backup might be performed either as an individual logon or using the Windows SharePoint Services Timer (SPTimer) service.

Correct the permissions and then retry the backup operation again.

On the file share, and in NTFS permissions, ensure that the following accounts are granted Change and Read permissions:

  • Account used by the SQL Server (MSSQLServer) service.

  • Windows SharePoint Central Administration application pool account if using Central Administration or a timer job to perform the backup.

  • The logged on account if using the Stsadm command-line tool to perform the backup manually.

  • If the backup is being performed by a timer job, the computer from which the backup operation is being performed must also be granted access. You can grant a computer permissions to a file share by using the following format: <Domain>\<Sharename>$. For example, “Contoso\WSSBackups$”

    Note:
    When backing up to a remote file share, you must use a domain account rather than a local system account. You must have Modify permissions to the share to perform these tasks.

Verify

Ensure that backups can complete successfully. You must be a member of the SharePoint Administrators group to perform this task.

To check if backups can complete successfully

  1. Important: Ensure that the target location has sufficient drive space for the backup.

  2. In Central Administration, on the left navigation pane, click Operations.

  3. On the Operations page, in the Backup and Restore section, click Perform a backup.

  4. On the Select Component to Backup page, choose the components you want to back up, such as a farm or an individual site. To test the backup job, choose a site or some smaller component.

  5. When you have selected all the components that you want to backup, click Start Backup Process.

  6. On the Start Backup page, in the Backup File Location section, enter the UNC path to the backup folder.

  7. Click OK.

  8. You can view the backup job status on the backup status page by clicking Refresh. The page will also refresh every 30 seconds automatically. Backup and Restore is a Timer service job, so it might take a few seconds for the backup to start.

  9. If you receive any errors, you can find more information by looking in the spbackup.log at the UNC path you specified previously.

To find the location of the log file folder

  1. In Central Administration, on the left navigation pane, click Operations.

  2. In the Logging and Reporting section, click Diagnostic Logging.

  3. On the Diagnostic Logging page, in the Trace Log section, the path to the log file is displayed in the Path box.

Related Management Information

Backup and Restore (Health model)

Windows SharePoint Services 3.0 health model

Related:

Leave a Reply