Please enter search query. Search <book_title>...
Veritas NetBackup™ for Microsoft SharePoint Server Administrator's Guide
Last Published: 2021-01-01
Product(s): NetBackup (22.214.171.124, 9.0)
- Introducing NetBackup for SharePoint Server
- Installing NetBackup for SharePoint Server
- Installing and configuring NFS for SharePoint Granular Recovery
- About configuring Services for Network File System (NFS)
- Configuring NetBackup for SharePoint Server
- Configuring a SharePoint backup that uses Granular Recovery Technology (GRT)
- Configuring SharePoint client host properties
- Configuring NetBackup for SharePoint backup policies
- About configuring a backup policy for SharePoint
- Adding schedules to a NetBackup for SharePoint policy
- Creating a backup selections list for a SharePoint Server policy
- Performing backups and restores of SharePoint Server and SharePoint Foundation
- About user-directed backups of SharePoint Server and SharePoint Foundation
- About restores of SharePoint Server and SharePoint Foundation
- Protecting SharePoint Server data with VMware backups
- About protecting an application database with VMware backups
- About configuring a VMware backup that protects SharePoint Server
- Disaster recovery
- About NetBackup for SharePoint debug logging
- About NetBackup status reports
Performing a manual backup
After you configure the servers and clients in your environment, you can test the configuration settings with a manual backup. Perform a manual backup (or backups) with the automatic backup schedules you created.
To perform a manual backup
- In the left pane, click Policies.
- In the All Policies pane, select the policy you want to test.
- Select Actions > Manual Backup.
- Select the schedule that you want to use for the manual backup.
- Select the clients that you want to include for the manual backup.
A parent job contains the whole file list and one or more child jobs. A child job is automatically launched for each host that contains SharePoint data. For example, assume that a SharePoint farm consists of four separate hosts. In this case, one parent job and four child jobs appear in the Activity Monitor. The front-end web server is listed as the client name for all jobs.