Tchater maintenant avec le support
Tchattez avec un ingénieur du support

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

Scaled-Out Farm deployment

In a Scaled-Out Farm deployment, the SharePoint SQL Server Instance, application server, and web server each reside on a dedicated server. Optionally, SharePoint Administrators can deploy extra dedicated web servers. The plug-in is installed on a single web or application server and performs all backup and restores from this server.

Figure 3. Plug-in deployed in a Scaled-Out Farm deployment

Scaled-Out 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 scaled-out farms, use 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. Quest also recommends 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 Scaled-Out Farm deployments.

Assigning the SP_DATA_ACCESS role for SharePoint 2013 and later

Although SP_DATA_ACCESS database role is the default role for database access in SharePoint 2013 and later, Quest recommends that you ensure that the domain user account has the SP_DATA_ACCESS role.

1
On the server where the SharePoint SQL Server Instance resides, open SQL Server Management Studio.
2
In the Object Explorer, navigate to the Security folder.
3
Under the Security folder, select Logins.
4
Right-click the name of the domain user account, and select Properties.
5
In the Login Properties dialog box, select User Mapping.
6
In the list of databases, select the SharePoint configuration database.
For example: SharePoint_Config
7
In the Database role membership section, select the following options:
•
Public
•
SharePoint_Shell_Access
•
SPDataAccess
•
WSS_Content_Application_Pools
Quest also recommends that you select the db_accessadmin role.
8
Add the same role memberships to the other SharePoint configuration databases, including:
•
SharePoint_AdminContents
•
SharePoint_Config
•
WSS_Content
9
To save your changes, click OK.

Installing or upgrading the plug-in

1
Access the NetVault Configuration Wizard or Manage Clients page.
 
* 
NOTE: If the selected clients are all the same type, you can use the configuration wizard to install the plug-in on multiple clients at the same time. When you select multiple clients, verify that the plug-in binary file is compatible with the OS and platforms of the target clients. From the Manage Clients page, you can only select one client for plug-in installation.
•
To access the NetVault Configuration Wizard page:
a
In the Navigation pane, click Guided Configuration.
b
On the NetVault Configuration Wizard page, click Install Plugins.
c
On the next page, select the applicable clients.
•
To access the Manage Clients page:
a
In the Navigation pane, click Manage Clients.
b
On the Manage Clients page, select the machine that contains the SharePoint Server, and click Manage.
c
On the View Client page, click the Install Plugin button ().
2
Click Choose Plug-in File, navigate to the location of the “.npk” installation file for the plug-in, for example, on the installation CD or the directory to which the file was downloaded from the website.
Based on the OS in use, the path for this software may vary on the installation CD.
3
Select the file entitled “sps-x-x-x-x-x.npk,” where xxxxx represents the version number and platform, and click Open.
4
To begin installation, click Install Plugin.
After the plug-in is successfully installed, a message is displayed.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation