Metalogix Backup for SharePoint 6.11 - Release Notes

Implemented capability to expose the Volume Shadow Copies used for farm backup operation over a path other than the %SystemRoot%\TEMP folder. It is now possible to use the folder path configured in the configuration file of Management Service or to use environment variables. Contact Metalogix Technical Support for further details.

LID 19145

Resolved issue where pages stored at the root directory of a host-named site collection were not being restored.

LID 19296

Resolved issue where Backup was unable to mount data files from a Windows 2008 R2 clustering server.

LID 18503

Resolved issue where the custom Web Part that allows to upload a file was not being restored.

LID 19250

Resolved issue where database backups fail if the databases files are located on non-standard file path definitions.

LID 19160

Resolved issue where items from List Template Gallery were not being restored.

LID 18327

Resolved issue where Master pages from Master Page Gallery and that are used by default were not being restored.

LID 18325

Resolved issue where custom Home Page with custom Web Parts is not restored during granular restore operation.

LID 16153, LID 18157,
LID 18160

Implemented new feature which allows Backup to perform backup and restore operations over SharePoint with a SQL Alias server without having to configure hostnames or DNS records for the SQL Alias server.

LID 17309

Implemented new feature which allows for the automatic restart of Backup’s services in the event that services crash.

LID 18098

Implemented the ability to mount content databases in SQL 2008 or lower versions.

LID 17366

Implemented support for Tivoli 7.x.

LID 15016

Resolved issue where scheduled backups (full or differential) were not being queued when another full or differential backup was already running.

LID 18454

Resolved the issue where a custom Master page selected on the “Master Page Settings” page was not being restored.

LID 18325

Resolved issue where alert notifications for the preparation of mounting databases were registering as Canceled instead of Successful.

LID 17155

Resolved issue where the content from a host-named site collection was not being displayed.

LID 17850, LID 18390

Resolved issue of object reference error displaying when attempting to get the language from the source site collection.

LID 17987

Resolved issue where a canceled operation was not disposing of VSS shadows.

LID 15544

Resolved issue where scheduled differential farm backups were not starting.

LID 17719

Resolved issue related to the inability to restore Out-Of-Place for differential farm backups.

LID 17701

Resolved issue where SharePoint Databases, located inside the folder of a Mounted Volume, were not able to be backed up.

LID 17693

Resolved issue where a backup set, located in a TSM server, could not be deleted the first time.

LID 13747

Resolved issue where mounting content databases through the Full Farm Wizard failed if the full farm backup was backed up in a TSM server.

LID 16891

Reworking of the Granular Restore section. For this release we removed the ability to new granular backups, but users can still work with granular backup sets taken on previous versions. Backup now provides the option to Mount or Link Content Databases in order to get SharePoint content to perform a Granular Restore using the Metalogix Framework.

LID 13730

New feature which allows users to Mount Content Databases after completing a Full Farm Backup operation that backed up a Content Database.

LID 14459

Resolved issue related to Full Farm Backup over SharePoint Farms that have their databases over Availability Group (SQL AlwaysOn Feature), so from this release SharePoint Backup supports Full Farm Backups of databases over Availability Groups.

LID 14159
LID 14163

Resolved issue during a Farm Restore of databases over SQL Servers that are registered in Central Administrator with a FQDN name.

LID 14173