Chatee ahora con Soporte
Chat con el soporte

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

Full Backup

A Full Backup is the most common type of backup performed. It backs up the entire SharePoint Farm for disaster recovery, media failure, or data corruption across many content databases or site collections.

Full Backups consume more space and time per backup and are typically supplemented by Differential Backups, which are created more frequently. With Full Backups, you can re-create a SharePoint Farm in one step. To do so, you can restore the entire farm or you can restore an individual web application or content database from the same Full Backup.

The entire SharePoint Farm is backed up during a Full Backup even if individual web applications or site collections are selected on the NetVault Backup Selections page. A Full Backup does not depend on any other backup and can be restored in a single step.

Differential Backup

With a Differential Backup, only the data that has changed since the last Full Backup occurred is backed up. Differential Backups reduce your risk of data loss because they are smaller and faster than Full Backups.

A Differential Backup is useful if some of the site collections are modified more frequently than others. In this case, Differential Backups let you back up frequently without the overhead of Full Backups.

A Differential Backup must always have a “base” backup, which is a Full Backup. Performing a Differential Backup without first performing a Full Backup may lead to backup failures in addition to an inability to restore and recover your SharePoint Farm properly.

Individual Site Collection

Individual Site Collection backups are an ideal option when you only want to protect a subset of individual site collections or duplicate one or multiple site collections to a test environment. Individual Site Collection backups are independent of an established sequence of backups and do not affect the recoverability of Full or Differential Farm Backups. However, they should not be used as a replacement for a Full and Differential Backup strategy.

Examples of backup sequences

Following are a few examples of backup sequences that support multiple restore scenarios and that you can implement to meet your SharePoint data protection requirements.

•
Full Backups only: When requirements guarantee data protection up to the previous day, performing Full Backups nightly should suffice when one or more of the following conditions exist:
•
Backup windows are large.
•
Databases are small.
•
Updates are infrequent across the entire SharePoint Farm.
•
Databases are only for testing or development purposes.
•
Full + Differential Backups: When requirements guarantee data protection up to the previous day and backups have to be as fast as possible, Full Backups coupled with Differential Backups is a valid strategy. For example, Full Backups are performed every Sunday at 11:00 P.M., while Differential Backups are performed Monday through Saturday at 11:00 P.M. Each Differential Backup includes all the changes since the last Full Backup, which is known as the differential base.
No matter when recovery is performed, the same number of restore jobs is required. For example, if recovery is performed on Tuesday, Sunday’s Full Backup and Monday’s Differential Backup must be restored. Whereas, if recovery is performed on Thursday, Sunday’s Full Backup followed by Wednesday’s Differential Backup must be restored.
Even though Differential Backups increase not only in size but in duration, restores are quicker due to the fewer restore jobs that must be run.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación