Chat now with support
Chat with Support

Metalogix Backup for SharePoint 6.6 - User Guide

Product Overview Getting Started Configuring Metalogix Backup for SharePoint
Opening the Management Console Connecting a standalone Management Console to the Management Service Configuring Metalogix Backup for SharePoint for your farm Managing the Backup Service Managing farms Configuring fault tolerance Managing self-service recovery Managing preferences Managing alerts Managing backup set disk space Importing a Repository Database
Reviewing backup status Backing up and restoring farm components Restoring granular objects

Learning about the components and architecture

Metalogix Backup for SharePoint provides a robust, easy-to-use SharePoint backup and restore solution. Behind a friendly user interface, this product offers a unique architecture that is both flexible and extremely powerful. Metalogix Backup for SharePoint fits your environment, no matter how simple or complex.

The following diagram illustrates the product components.
diagram

Metalogix Backup for SharePoint uses the SharePoint and Active Directory permissions that you set in your environment to control access to content and to farm components.

How does Metalogix Backup for SharePoint address BLOB storage?

In SharePoint, a large majority of file data is stored as binary data streams known as BLOBs (binary large objects). Users can store BLOBs in a remote or external location to avoid using unnecessary space in the content database. Some versions of SQL Server provide remote BLOB storage (RBS) as an API set that facilitates this remote and external storage. You can also use an external BLOB storage medium (EBS) that runs parallel to your content database.

Metalogix Backup for SharePoint works seamlessly with Metalogix StoragePoint, the Metalogix BLOB storage solution. If your content is being externalized using StoragePoint, then you need to configure an endpoint in StoragePoint itself.

If you are using a BLOB storage system aside from Metalogix StoragePoint, then Metalogix Backup for SharePoint will ignore RBS and EBS data when performing a full farm backup. This is because a backup endpoint cannot be setup, and therefore Metalogix Backup for SharePoint cannot recognize these storage databases.

 

Learning about the components

Metalogix Backup for SharePoint has a light, unobtrusive architecture that easily runs in your environment with minimal configuration. Metalogix Backup for SharePoint does not add to or modify any of your native SharePoint files or services when you install it. When needed, Metalogix Backup for SharePoint does make changes to permissions. For more information about permissions and requirements, see Learning about the requirements.

About the Management Console

The Metalogix Backup for SharePoint Management Console allows you to configure Metalogix Backup for SharePoint, view operation status and history, schedule automated backup activities, and perform other related functions. Comprehensive Today pages for specified farms include a view of the backup status and recent backup and restore operations. You also use the Management Console to configure Metalogix Backup for SharePoint and to perform backup and restore tasks.

Multiple copies of the Management Console can all contact a single Management Service. You can let each of the SharePoint administrators in your environment collaborate to perform backup and restore operations. In addition, if your environment includes multiple SharePoint farms, each Management Console can connect to one or more of the farms simultaneously.

You can use the Metalogix Backup for SharePoint installer to install the Management Console and Management Service on a computer, or you can install the Management Console only. If you install only the Management Console, you must install the Management Service on another computer. The Management Console must be installed on a Web Front End (WFE).

About the Management Service

The Metalogix Backup for SharePoint Management Service receives requests from the Management Console and from the Self-Service Recovery feature. Based on those requests, the Management Service connects to one or more Backup Service installations hosted on a SharePoint Web front End (WFE) or on a SharePoint database server and starts the requested operation.

You can install the Management Service on any computer in your network. The Management Service host does not need to be a part of the SharePoint farm, and can manage multiple farms at once. The host that you select should always be running so that it can contact and manage the Backup Service when needed. Both the Management Service and the Management Console are installed when you perform a full install of Metalogix Backup for SharePoint. You cannot install only the Management Service.

The Management Service uses the Metalogix Backup for SharePoint repository database to store historical data. Each Management Service uses a separate repository database.

If you schedule an activity, the Management Service initiates the scheduled activity and records its progress and status.

About the Backup Service

The Backup Service performs any backup and restore operations you request. When an on-demand or scheduled operation begins, the Management Service contacts the Backup Service and initiates the operation. The Backup Service uses the Microsoft Volume Shadow Copy Service (VSS) to back up SharePoint 2010, 2013, 2016 or 2019 farm components. The Backup Service uses the SharePoint object model to backup and restore granular SharePoint content on any SharePoint 2010, 2013, 2016 or 2019 farm.

To perform Farm Backups for SharePoint 2010, 2013, 2016 or 2019 farms, install the Backup Service on every WFE and every Database Server in the farm.

The Backup Service stores the objects that it backs up in backup sets. Specify a location where the Backup Service stores the sets. You can specify a UNC location or a Tivoli Storage Manager (TSM) virtual client node.

Use the Management Console to discover your WFE hosts and standalone database server hosts and install the Backup Service. You can also use the Metalogix Backup for SharePoint installer to manually install the service on a WFE host or database server host. You can only install one Backup Service on each server, but the Backup Service can be shared by multiple Management Service copies. You can back up content databases from a SQL Server host that is shared between farms as part of the relevant farms.

When it starts, the Backup Service verifies connectivity to the farm and to the Web applications in the farm. To perform backups, the Backup Service account must be assigned a full control policy for every Web application in the farm. When it starts, the Backup Service assigns the required policies to the Backup Service account. If you add a Web application to the farm, you should restart all of the Backup Service copies so that the Backup Service can grant privileges for the new Web application.

About the Repository Database

The Metalogix Backup for SharePoint repository database stores configuration information, backup and restore operation data, and statistical and other data that the Management Service collects. Each Management Service uses a separate repository database. A single SQL Server host can host multiple uniquely-named repository databases. The SQL Server that hosts the repository database does not need to be part of the SharePoint farm. The repository database does not store backed-up SharePoint content.

About the Self-Service Recovery Solutions

The Self-Service Recovery feature saves backup administrators time and effort while also giving site collection administrators fast, convenient access to their backed-up library items. You install the Self-Service Recovery feature when you configure Metalogix Backup for SharePoint for your farm.

Learning about communications and security

Depending on the configuration of your SharePoint farm and your enterprise network, many of the computers in your network can host the Metalogix Backup for SharePoint components. The components use encrypted TCP/IP communications to communicate with one another. Metalogix Backup for SharePoint encrypts all internal communications between components. If a component is not able to negotiate an encrypted communications channel, the communication fails. This helps to ensure the security of your SharePoint data.

Metalogix Backup for SharePoint uses the Microsoft .NET Windows Communications Foundation (WCF) services to secure communications. All communications channels use transport encryption and signing, and do not use non-FIPS encryption methods. All communications within Metalogix Backup for SharePoint are therefore FIPS-compliant.

You can customize the communications ports for each component if you choose. For assistance in changing the port, please visit the Metalogix Technical Support Web page at https://support.quest.com.

Ports Used During Metalogix Backup for SharePoint Setup

The following ports must be open during the installation and setup of Metalogix Backup for SharePoint:

Port

Destination

Details

TCP 1433,

UDP 1434,

or custom

Management Service > Backup Repository

This port can be replaced if an instance or a non-default port is used for SQL server.

TCP 7484

Management Console > Management Service

This port should be open where the Management Service will be installed.

TCP 7485

Management Service >  Backup Service

This port should be open where the Management Service and backup services will be installed.

TCP 137,138,139

or TCP/UDP 445

Management service > Backup Service

Management Console > Management Service

Management Service > SharePoint SQL Server

Management Service > Backup Set location

This port should be open where the Management Service and backup services will be installed.

TCP 1027

Management Service> WFE

Management Service> APP

Management Service> SQL

This port should be opened before the Configuration Wizard runs.

TCP 135

or epmap

Management Service> WFE

Management Service> APP

Management Service> SQL

This port should be opened before the Configuration Wizard runs.

WMI (port 135 and a second, random port)

Management Service> WFE

Management Service> APP

Management Service> SQL

These ports should be opened before the Configuration Wizard runs in order for farm configuration retrieval to take place.  To set up a fixed port for WMI instead of using a random one, refer to the related article on MSDN:
https://msdn.microsoft.com/en-us/library/bb219447(v=vs.85).aspx

 

Additionally, you should enable the Remote Administration option in the Windows Firewall for each server in the farm to let the Metalogix Backup for SharePoint Management Console contact the server. Some ports like 1027, epmap, WMI can be closed after the Configuration Wizard finishes installing and/or updating all components on the farm.

All of the Metalogix Backup for SharePoint components should be hosted by computers that are members of the same farm or by farms that have mutual trust relationships defined. Metalogix Backup for SharePoint encrypts Farm Backups with the AES-128 algorithm. AES-128 is FIPS-compliant.

The following image illustrates the ports, protocols and services used by Metalogix Backup for SharePoint during installation and setup:

 

CommunicationAndSecurityProtocolsServicesInstall

Ports Used for Metalogix Backup for SharePoint Services

In order to use Metalogix Backup for SharePoint components for daily operations, the following ports need to be open:

Port

Destination

Details

TCP 7484

Management Console > Management Service


TCP 7485

Management Service >  Backup Service

Primary Backup Service >Backup Service


TCP 1433,

UDP 1434,

or custom

Management Service > Backup Repository

This port can be replaced if an instance or a non-default port is used for SQL server.

TCP 137,138,139

or TCP/UDP 445

Management service > Backup Service

Management Console > Management Service

Management Service > SharePoint SQL Server

Management Service > Backup Set location

This port should be open where the Management Service and backup services will be installed.

The following image illustrates the ports that need to be open to perform Metalogix Backup for SharePoint operations:

CommunicationAndSecurityProtocolsServicesUsage

Learning about Tivoli Storage Manager

Tivoli Storage Manager (TSM) is a product from IBM that helps you to manage storage and backup on your enterprise network. If your enterprise network includes a TSM deployment, you can configure Metalogix Backup for SharePoint to store backup sets in TSM. Before you can use TSM as a backup location, you must configure it.

info

NOTE: Metalogix Backup for SharePoint supports the 32-bit versions 6.x and 7.x of the Tivoli Storage Manager (TSM), as well as 64-bit versions for 7.x and 8.x of TSM.

The steps to configure TSM in your environment depend on the version of TSM you have installed, and the way that your environment is configured. In general, though, you must do the following:

·Install and configure the TSM client software on every server in your SharePoint farm where the Backup Service is installed.

·On the TSM server, create a single virtual client node that the clients share.

·Grant access to the virtual client node to every server that hosts a Backup Service.

·In TSM, configure the options for the virtual client node. In addition to whatever options are appropriate for your deployment, you must set the option backdel=yes.

·In the Management Console, when you create a TSM backup location, you enter the name of the virtual client node where Metalogix Backup for SharePoint stores the backup data.

The default TSM filespace that Metalogix Backup for SharePoint uses is IderaSPbackup. For information about installing configuring TSM and configuring the TSM client options, see your TSM documentation set. For more information about creating a Backup Location, see Defining the Backup Service preferences.

info

TIP: If you enable data grooming for a backup set that Metalogix Backup for SharePoint stores in TSM or if you manually delete the reference to a backup set that is stored in TSM from the Management Console, Metalogix Backup for SharePoint removes references to the data in Metalogix Backup for SharePoint. In addition, Metalogix Backup for SharePoint sets the data objects to Inactive in TSM. Metalogix Backup for SharePoint does not automatically delete the data itself. If you need to delete the data from TSM, you should use the TSM management tools to do so.

Here are a few considerations for users using Tivoli Storage Manager:

·If you use a Tivoli Storage Manager (TSM) virtual client node as a backup location and the TSM storage pool runs out of free space, Metalogix Backup for SharePoint encounters errors. You should ensure that the TSM storage pool that hosts a backup location does not run out of free space.

·If you import a backup stored in a TSM virtual client node, you can only perform in place restores from that set.

Related Documents