サポートと今すぐチャット
サポートとのチャット

NetVault Plug-in for SharePoint 12.1 - User Guide

Introducing NetVault Backup Plug-in for SharePoint Deploying, installing, and removing the plug-in Configuring the plug-in Backing up data Restoring data
Understanding the SharePoint restore process Restoring backups in SharePoint Restoring a single Full Backup,a Full + Differential sequence, or an Individual Site Collection Backup Using other restore procedures
Common tasks Restoring to the same server or farm Restoring to an alternate server or farm
Extra items to protect using NetVault Backup and the Plug-in for FileSystem Troubleshooting

Single Server deployment

In a Single Server deployment, the SharePoint SQL Server Instance, application server, and web server all reside on the same computer or server. The plug-in is installed on this single server and performs all backups and restores from this server.

Figure 1. Plug-in deployed in a Single Server deployment

Single Server deployment prerequisites

Verify that the following prerequisites are met:

•
Set up a user account that is a member of the Administrators group on the local computer.
•
Create a directory for temporary files on the SharePoint Server that stores the temporary backup packages created by the SharePoint PowerShell Cmdlets or STSADM.
Every backup stores information, called a backup package, in this directory. The backup package for a Full Backup must be available to perform a Differential Backup because a Full Backup is the base of all subsequent Differential Backups. For this reason, Quest recommends that you use the same directory for every backup in a backup sequence. Quest also recommends that you clean out this directory before you perform a new Full Backup.
•
Ensure that the SharePoint Administration service in the Windows Control Panel is started. This service is not started by default on Single Server deployments.

Small Farm deployment

In a Small Farm deployment, the SharePoint SQL Server Instance resides on a dedicated server while the application server and web server reside together on a separate server. The plug-in is installed on the server where the application server and web server reside and performs all backups and restores from this server.

Figure 2. Plug-in deployed in a Small Farm deployment

Small Farm deployment prerequisites

Verify that the following prerequisites are met:

•
Create a domain user account that is a:
•
Member of the Administrators group on each server on which SharePoint Setup is run.
•
Member of the following SQL Server security roles:
•
Logins
•
Securityadmin
•
Dbcreator
•
For SharePoint 2013 and later, ensure that the domain user account has the SP_DATA_ACCESS role. For more information, see Assigning the SP_DATA_ACCESS role for SharePoint 2013 and later.
•
Create a directory for temporary files that stores the temporary backup packages created by the SharePoint PowerShell Cmdlets or STSADM.
For small farms, use Universal Naming Convention (UNC) share paths, such as \\machine_name\SPbackup, so that the SQL Server Database and search components are written to the same location. This directory must exist, and all the servers in the SharePoint Farm must be able to access it.
In addition, verify that Change and Read Share Permissions for the file share are granted to the domain account user.
Every backup stores information, called a backup package, in this directory. The backup package for a Full Backup must be available to perform a Differential Backup because a Full Backup is the base of all subsequent Differential Backups. For this reason, Quest recommends that you use the same directory for every backup in a backup sequence and that you clean out this directory before you perform a new Full Backup.
 
* 
IMPORTANT: Unrelated SharePoint Farms should not use the same UNC Share for the Directory of Temporary Files; otherwise, the SharePoint PowerShell Cmdlets or STSADM backup history includes backups for unrelated farms, which can lead to unnecessary complexity.
•
Ensure that the SharePoint Administration service in the Windows Services is started. This service is not started by default on Small Farm deployments.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択