The Advanced Installation Guide provides information about the installation, upgrade, and removal of Metalogix Backup for SharePoint in various SharePoint farm configurations.
When you install Metalogix Backup for SharePoint, the installer creates a new Web application policy that grants full control to every Web application in the farm, and then assigns this policy to the Backup Service account.
This version of Metalogix Backup for SharePoint includes changes to the way that permissions are handled in differential backup and restore. When you upgrade to the current version, you should immediately perform a differential backup to accurately capture any permissions changes.
If you add a Web application to the farm after you install Metalogix Backup for SharePoint, you should restart all of the Backup Service instances in the farm.
Here are a few general considerations about Metalogix Backup for SharePoint to keep in mind:
·When you specify a backup set location, the full path of the location, including the backup set folder and the file name of any contents, must be less than 255 characters. If the path name is too long, backups may complete successfully, but restore operations fail. If a restore operation fails and the error message indicates that the file does not exist in the source directory, verify that the path is less than 255 characters.
·When you perform an out-of-place restore of any item, the full path of the item, including the item file name, must be less than 255 characters.
·If you use "Restore" to restore in place and the target item already exists or is in the site or site collection recycle bin, a duplicate item may appear. Alternatively, an error may occur during the restore process. When you restore an item in place, you should ensure that the items that you are restoring do not exist in the site recycle bin, or the site collection recycle bin.
·When searching for items in a backup set, if there is a large number of matches for a given search term, some items that match the search term may not be included in the search results.
·The Management Service maintains a cache of the members of the farm administrators group. If you create a new farm administrator, the new administrator does not have rights to existing backup sets until the Management Service refreshes its cache. Normally, the Management Service refreshes the cache every five minutes. You can also use the Services control panel to restart the Management Service to force it to rebuild its cache.
·If ActiveX Scripting is set to prompt, Metalogix Backup for SharePoint help may not load properly, and the help window displays a blank screen.
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.
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 Specifying Backup Storage Locations.
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.