Template:Introducing new module

From SEPsesam
Jump to: navigation, search


Copyright © SEP AG 1999-2020. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

Mark the topic as a draft until it is finished. If you are describing an extension, you should make two separate topics for it: one for installation, configuration and backup, and another for restore and related tasks. The title convention should be: Extension_name Backup, Extension_name Restore. Familiarize yourself with the [instructions for translating documents] before you start writing a topic. /span>

Draft.png WORK IN PROGRESS
This page is a draft. Treat the information on this page with caution as it may be incomplete.

Start with heading level 2, level 1 is reserved for the page title!/span>

Overview

Provide a few paragraphs about the newly supported module: what is supported, what are the features and how they work. See the example from the topic Hyper-V Backup 4.4 below. SEP sesam provides efficient data protection for Microsoft Hyper-V environments. It allows you to backup multiple VMs running on a Hyper-V single server with a single task as well as all VMs on the same node in a cluster at once. SEP sesam enables you to restore your Hyper-V data directly from storage swiftly and reliably. A variety of storage devices is supported, allowing you to back up any Hyper-V system to any virtual machine-supported storage. By using the integrated Si3 target deduplication for Hyper-V backups, you can benefit from reduced disk capacity and increased overall storage performance.

License

If this feature requires a special license, provide information on license. If not, skip this section.
See the example from the topic SharePoint_Backup_4.4.2#License below.

SharePoint Recovery Pro (Ontrack PowerControls for SharePoint) license is always issued for the size of the SQL databases and log files. To estimate the SQL size, count the size (GB) of all data (*.mdf) files and transaction log (*.ldf) files. If the size of your *.mdf and *.ldf files is larger than the size specified in the license, you will not be able to restore your data using the SharePoint Recovery Pro (Ontrack PowerControls for SharePoint).

To obtain a license, contact the SEP sesam sales at Contact.

Key features

Provide a description of the key features - marketing department might use this section to reference it. See the example from the topic SharePoint_Backup_4.4.2

  • SEP sesam currently supports FULL and COPY backup types for SharePoint. With these backups all data defined by the backup task is backed up, regardless of when it was last changed.
  • Using Advanced Search Agent for SharePoint provides administrators with a quick access to the arhived items, enabling them to search backed up SharePoint databases file by keyword, item type, user or date, rather than perform a full restore to find a single lost item.
  • Administrators can perform a single item recovery by simply searching, dragging & dropping the selected items to the target destination, which can be a live environment or alternate location. For details, see SharePoint Restore 4.4.2.
  • The integrity of your SharePoint data is preserved by preventing any data from being modified while it is archived. For example, if an administrator searches for some individual items and retrieves them, their version in the archived SharePoint stays unaltered while the retrieved items are stored to the target destination with all relevant metadata.


Quick setup overview

Setting up SEP sesam to fully protect the entire SharePoint environment is similar to standard environment setup with some SharePoint specific tasks, which are described below.

Setup.jpg


Configuring components

Prerequisites

  • SEP sesam Server or SEP sesam Remote Device Server (RDS) running on Windows x64.
  • SEP sesam ordinary data store (Path) or SEP sesam Si3 data store is required for single item recovery.
  • In case the backups are encrypted, stored on tape or on Linux datastore, a manual restore to a prepared Windows x64 system with SharePoint Recovery Pro is required. See Manual restore.


Preparing SEP sesam environment

  1. You need to install the SEP sesam Client package v. 4.4.2 or higher to all SharePoint and SQL Servers . Since version 4.2.2.26, the SharePoint extension for SharePoint Server 2010/2013 is already included in all SEP sesam packages (SRV/GUI/CLI). You can download it from SEP Download Center. For details, see SEP Sesam Quick Install Guide.
  2. Ensure that the SEP sesam service is running with the rights of an AD user with sysadmin role and full access to the SharePoint server. If the sysadmin role is not set, it must be added to the SharePoint administrator account, e.g., the user sp_sfa. If the SQL Server is running on another node, the SEP sesam service on that SQL Server node must run with the rights of an AD user with sysadmin role and full access to the SQL Server.
  3. Register the SharePoint Services Writer. Login as a SharePoint farm administrator and execute the following command with the administrator rights for SharePoint (e.g., qs12\sp_sfa):
    #> stsadm.exe -o registerwsswriter.
    For details, see MS article SharePoint 2013 VSS Writer.

Installing SEP sesam SharePoint Recovery Pro package (Ontrack PowerControls for SharePoint)

SharePoint Recovery Pro consist of two packages: Ontrack PowerControls for SharePoint and Ontrack PowerControls Agent for Content Transfer Service. To obtain a license, contact the SEP sesam sales at Contact.

Step 1: Download the SharePoint Recovery Pro (Ontrack PowerControls for SharePoint) from the link that was provided by SEP sales. Extract the Ontrack PowerControls for SharePoint files to a directory of your choice on the Windows x64 system, which is a SEP sesam server or RDS. Then double-click the setup.exe, select only SharePoint, and follow the instructions.

Step 2: Install the Ontrack PowerControls Agent to the SharePoint Server, which has a SEP sesam client already installed:

  1. Log on to the SharePoint server using admin privileges.
  2. Run the Ontrack PowerControls Agent .exe file.
  3. Follow the onscreen instructions. In the Logon Information step of the install wizard, enter the user name (in the format DOMAIN\username) and password for the SharePoint farm administrator.
  4. In the Agent for Content Service Setting step, in the Port Number field, use the default value or enter another available port number. You must memorise the port number since you will have to enter it when using Ontrack PowerControls for SharePoint. Note that the firewall configuration must be set to allow communication over this TCP port.
  5. In the Temporary File Location field, use the default path or browse for the one you want to use. This location is used as a temporary storage for your SharePoint data during restore. Make sure to select a temporary location with sufficient space to enable succesfull restore.

Installing the license file for SharePoint Recovery Pro

You need a special license file for SEP sesam SharePointRecovery Pro feature. Licenses are made available immediately once your purchase/renewal is completed.

ATTENTION

The license counts all *.mdf and *.ldf files of all SharePoint databases. If you ordered a license with too small license size value (TB), the restore will not work!

  1. Go to Start -> All Programs -> SharePoint Recovery Pro and open it. A message License file not installed appears.
  2. Click the button License info and import the license.ini file.

Configuring SharePoint backup

To fully protect your SharePoint environment, you have to create different backup tasks for the SharePoint servers and a separate task for your SQL Server. The procedure for creating a backup task is the same, you just need to select a different backup type for each task according to the data source you want to protect.

After you have configured your backup task, you have to set up a backup schedule (specify when you want to back up your data) and link a backup event to it (select where to back your data to and how). For details, see Standard Backup Procedure.

Since you have to configure more backup tasks for the SharePoint servers, only specific backup type and source for each is introduced within the general steps.

  1. You configure your backup task(s) from the Main Selection -> Tasks -> By clients -> select your SharePoint client -> New backup task.
  2. From the Backup type drop-down list and for the Source, select:
    • backup type SharePoint and source all -> schedule this task to run daily type FULL
    • backup type Path and source all -> schedule this task to run once every week type FULL, and the other days INC
    • backup type System Recovery and source system_state -> schedule it to run daily type FULL
  3. Backup task-select type.png


  4. Once you configured a schedule, you need to create a new backup event for it. Go to the Main Selection -> Scheduling -> New Backup Event, click the Parameter tab and select COPY or FULL backup from the Backup Type drop-down list. Note that COPY/FULL is the only supported backup level type for SharePoint clients!

SEP sesam does not truncate the transaction logs of the SQL Server, because truncating would break the log chain and disable point-in-time restore. Therefore you should set up periodic backups of SQL Server:
When configuring a task for your SQL Server, specify MS SQL Server as backup type and source all -> schedule it to run once every week type FULL, and the other days INC. For details, see SEP sesam Microsoft SQL Server.

Additionally, depending on whether your server is a physical or virtual machine, do one of the following to prepare for a complete system recovery:

  • If your server is a physical machine, use SEP sesam BSR pro to ensure successful disaster recovery. For details, see SEP sesam BSR Pro – Backup Configuration.
  • If your server is a virtual machine, start a daily VM snapshot backup of the VM.

What is next?

How to restore SharePoint