Quest® Recovery Manager for SharePoint
Version 3.2.2
Release Notes
December 8, 2009
Welcome to Quest Recovery Manager for SharePoint
Quest Recovery Manager for SharePoint is an innovative recovery solution for Microsoft SharePoint 2003 and 2007. The product allows to perform item-level granular recovery of SharePoint content from content database backups.
Support for SQL Cluster with Tivoli - Recovery Manager supports backup discovery, analysis and data restoration from Tivoli backups produced by Virtual TSM nodes located on one Cluster Node.
Support for HP Data Protector - Recovery Manager 3.2.2 supports backup discovery, analysis and data restoration from HP Data Protector (HPDP) full, differential and transaction log SQL VDI backups and full or copy SQL files VSS backups.
Recovery Manager for SharePoint Easy Deployment - To simplify the deployment for the Premiere Edition customers, the Recovery Manager for SharePoint and Web Access are now merged and installed by running a common setup. Upgrade from previous versions is available.
Recovery Manager for SharePoint Settings Page (Web Access-based) - Recovery Manager for SharePoint 3.2 has the Web Access-based settings page. The user now can benefit from the native web-based approach to change the settings including the Automatic Backup Analysis, Backup Discovery Schedule, Cache and Temporary Database Location, and Temporary Database Path. The settings will be preserved during the upgrade.
Discovery Window - Now you can specify the backup discovery scope. By default, only the backups created within the last fifty weeks are added to Recovery Manager. The information for the older backups is automatically deleted from the Recovery Manager Repository and Cache databases.
Dedicated Server Mode Support for Enhanced Backup Analysis and Restore for LiteSpeed 5.2 Customers- Recovery Manager allows to store cache database on dedicated SQL server instances when using Enhanced Backup Analysis and Restore for LiteSpeed, enabling customers to benefit from the rapid analysis and recovery for native SQL or LiteSpeed backups, and configure dedicated SQL Server instance to store the backup cache data without creating or requiring additional databases on the production SQL server instances. To activate this feature, Install Recovery manager Backups Reader component to your Dedicated SQL server and switch Recovery Manager to the Dedicated Server Mode.
Support for Unattached Database Files (*.mdf) - Recovery Manager supports analysis and restore from MDF files.
Enhanced Backup Analysis and Restore for LiteSpeed 5.2 Customers - With LiteSpeed 5.2 or higher installed, Recovery Manager provides a rapid analysis and recovery with low disk space requirements for SQL native and LiteSpeed backups enabling you to search for up-to-date SharePoint objects. You can install Recovery Manager Backup Reader to the SQL servers used as alternate locations to rapidly restore content to them.
Enhanced Backup Analysis and Restore for SQL Server Native Backups with Backup Reader - If you are using native SQL backups, you can benefit from the LiteSpeed technology used by Recovery Manager to ensure rapid analysis and restore with low disk space requirements as Recovery Manager no longer requires staging location. To activate this feature, install Recovery Manager Backup Reader component to your original SQL server and switch Recovery Manager to the Original Mode.
The following is a list of issues addressed and enhancements implemented Quest Recovery Manager for SharePoint 3.2.1:
|
Feature |
Enhancement |
Change Request |
| General | ||
| If a user opens the settings page and closes it without making any modifications, Recovery Manager for SharePoint goes to the Dedicated server mode from the Original mode without a warning message and backup analysis does not work. | CR#64050 | |
| Working with Tivoli Backups | The "ANS1309I (RC9) The requested data is offline." error occures while restoring data from Tivoli backups. | CR#63586 |
| If the database has filegroups containing more than one file, the "file can not be overriten" error occures while analyzing or restoring data from Tivoli backups. | CR#64006 |
The following is a list of issues addressed and enhancements implemented Quest Recovery Manager for SharePoint 3.1:
|
Feature |
Enhancement |
Change Request |
| Working with Tivoli Backups | ||
| The analysis and restoration from Tivoli backups works properly when Tivoli Storage Manager for Databases version 5.2 is used to protect WSS2 or SharePoint Portal server content databases. | CR#62397 | |
| Backup Analysis and Restore | The rapid backup analysis and restore work properly in the Japanese environment. You need to install Backup Reader 5.2.0.1240. | CR#63162 |
The following is a list of issues known to exist at the time of Recovery Manager release:
| Feature |
Known Issue |
Change Request |
| General | Some SharePoint hotfixes and updates may not be supported by Recovery Manager out of the box. To ensure full compatibility with SharePoint hotfixes and updates, please contact Quest Support. | CR#00000 |
By default, Recovery Manager for SharePoint does not work with Microsoft SQL Server 2005 Embedded Edition.
To workaround the issue, take the following steps:
|
CR#22170 | |
|
If you reinstall or repair Site Administrator on the computer running Recovery Manager for SharePoint, you must repair Recovery Manager by uninstalling Recovery Manager and installing it again. |
CR#15832 | |
|
An issue with the Recovery Manager console may arise when a connection to the Site Administrator database or the corresponding SharePoint server content database is lost. The error messages are displayed. Recovery Manager continues to work properly once the connection is restored. |
CR#20154 |
|
|
All product features are not available for 64-bit operation system installation,
if Recovery Manager 2.7.4 is installed with QMC version prior to 2.0.3.1023.
To fix the issue, create the StorageMachineName and StorageName keys in the HKEY_LOCAL_MACHINE\SOFTWARE\Quest Software\Sharepoint Manager hive. Set the values to SA Repository server and database. Note: If the product is installed from the CD, QMC automatically creates the required registry keys. |
CR#00000 | |
| Discovering Backups | Backup discovery schedule will be lost while upgrading from 2.6.0 and older. | CR#00000 |
|
If you are running Windows 2008,
RMSP Discovery scheduler offers
you to create a new discovery task,
although the task is already present on your machine.
To modify the default discovery schedule, use the Windows Task Scheduler from the Administrative Tools. Locate the RMSP-Discovery task and make your changes. |
CR#58418 | |
| Restoring Items |
Restoring SharePoint items from a backup requires the account under which the SQL Server hosting Site Administrator configuration database is running to have access rights to the network share which stores the backup. |
CR#15587 |
| If a SharePoint farm contains several content databases with the same name, restoring a site collection from a backup of one of them may lead to creating an inaccessible site collection invisible in SharePoint Central Administration Console. | CR#54761 | |
| "The given array is zero sized" error occurs when restoring items from the tree view of a SharePoint backup. Restart the console and try to restore once again. | CR#33240 | |
| Recovery Manager fails to restore objects to a SharePoint site that has been moved in the site hierarchy after the backup was made. The recovery operation reports success but the object is not restored. To workaround this issue, restore the item to the new site location using Restore to option. | CR#32102 | |
| Restoring an individual web part page to an alternate location will result in web parts missing on the restored page. Therefore it is recommended to restore web part pages as part of the sites they belong to. | CR#00000 | |
| When Recovery Manager is restoring site collections, sites, document libraries and lists as a whole, the number and the size of the objects being restored might not be displayed correctly. | CR#00000 | |
| Personal sites restored with Recovery Manager for SharePoint are not displayed in the Management Console tree, since Site Administrator does not display personal sites by default. | CR#26018 | |
| Recovery Manager allows you to restore lists and document libraries to a SharePoint site that is created using a different site definition from the original site. However this may lead to restored lists being corrupted or non-functional and should be avoided. | CR#33106 | |
| The restoration of workflow state may not work properly for the documents with the expired due date when restoring a Site/Site Collection to the same location. To workaround the issue, restore the list with invalid workflow state again from the Recovery Manager console. | CR#58379 | |
| Direct links to list items may not work after list recovery because list item IDs are modified during item recovery. | CR#41582 | |
| Relationship between the calendar entry and the meeting workspace are not restored when restoring the calendar entry only. | CR#49991 | |
| Recovery Manager does not restore values in Lookup fields such as links from the Posts list in a blog site to the Comments list with comments to posts. | CR#41581, CR#41579 | |
| Only Last Name information is available for the contacts and contact lists displayed in the SharePoint backup tree. | CR#36133 | |
| URLs may not be restored correctly in a Links list. | CR#41595 | |
| Thumbnails are not restored for pictures in a picture library (used in picture properties views and picture library slideshow view). | CR#41584 | The Hidden Document Not implemented error is displayed when attempting to restore the system template.doc template file. | CR#33200 |
| Child object (list item, document, list, site) with permissions inherited from the parent is not accessible after recovery when permission mode (use inherited/unique permissions) is changed for the parent object after the backup was taken. | CR#41169 | |
| Unique permissions are not restored for reply items in a discussion board. | CR#41519 | |
| Restoring Items to Alternate Location | ||
| Recovery Manager cannot restore the selected item(s) to an alternate location in the same content database as the original site. Select a site in a different content database or on a different server. | CR#33098 | |
| The hostname-relative path of the target SharePoint site must not include the relative path of the original site when restoring it from to an alternate location. E.g. if you restore the http://server1/sites/test site to a sub-site of http://server2/sites/test or http://server2/sites/test5, the restored site will be inaccessible in SharePoint. | CR#41615 | |
| You should restore entire MOSS 2007 portal site collection to an alternate location. Subsites of a portal site (Site Directory, etc.) may not work properly if restored as an individual site to a different location. | CR#41613 | |
| When restoring the entire portal area structure (starting from the root Home area) to an alternate portal site, the restore operation will fail if the target portal site areas have naming conflicts with the areas being restored. It's recommended to restore to an empty portal site with the Home area only. | CR#38847 | |
| When portal area listings are restored to an alternate portal site, the audience targeting settings are not preserved for the restored listings. Effectively, the restored listings will be visible to the default All Portal Users audience. | CR#38845 | |
| When restoring a multipage meeting workspace to a site at an alternate location, web parts on the supplemental web part pages (other than the Home page) are not restored. | CR#41601 | |
| Alerts are not restored for SharePoint document libraries, lists and items when restoring backed up content to an alternate location. | CR#33096 | |
| If a SharePoint object (document, list, document library or site) is restored twice into two alternate locations in the same content database, the object only appears in the location, where the object was restored last. | CR#36431 | |
| List items and documents are restored to a target container at their relative path in the source list or document library when restoring individual item and documents to an alternate location. | CR#33280 | |
| After repeated restoration of the site to an alternate location, the autostarted workflows associated with lists in the site may not start if the new document is added. | CR#59274 | |
| When the site with workflows is restored to an alternate site collection, the users which are restored to the alternate site collection have no access to the collection as they do not belong to any site collection group. As a workaround, add the users to the target site collection group manually. | CR#59313 | |
| When restoring subsites, lists, document libraries, folders, documents, items to an alternate location, their permissions and security medata are not restored. This applies to WSS2 and SPS2003. | CR#60214 | |
| When restoring folders, documents, items to an alternate location individually (not withing a list or web), their permissions and security medata are not restored. This applies to WSS3 and MOSS2007. | CR#60215 | |
| Working with DPM snapshots | ||
| If the path to the DPM snapshot generated by DPM is too long, use the Database Files Location tab to modify the default path to the folder where Recovery Manager temporary database is stored. | CR#00000 | |
| Working with LiteSpeed Backups |
If you use LiteSpeed backup encryption and differential backups of SharePoint databases, you will need the corresponding full backup analyzed before you can analyze/restore from a differential backup.
Locate the most recent full backup, start analysis and enter the password to decode the data. The password is then stored in the Recovery Manager cache database and used automatically to decrypt the full backup content when working with differential backup sets. |
CR#00000 |
Upgrade from earlier versions of Recovery Manager for SharePoint versions is supported. To upgrade the version, run the Recovery Manager for SharePoint 3.2.2 setup.
Note: Make sure you upgrade the Recovery Manager Agents (Tivoli, NetBackup) when installing a newer version of the product.
Customers who use Quest LiteSpeed and SQL Server or SQL and SharePoint native tools to create database backups can leverage the new enhanced analysis and recovery. To ensure faster backup analysis and recovery after the upgrade to Recovery Manager 3.2.2, follow the steps below:
Before installing Recovery Manager, ensure your system meets the following minimum hardware and software requirements:
| Platform | Intel x86, x64 (500MHz or higher) |
| Operating System | Either of the following:
|
| Additional Software & Services |
|
| Software & Services |
Either of the following:
|
| Platform | Intel x86 /x64 |
| Memory | Minimum 512MB. 2GB of RAM are recommended. |
| Additional Software |
Either of the following:
|
Note: Before installing Recovery Manager for SharePoint {Backup Type} Agents, make sure you have Microsoft .NET Framework 3.0 installed. You can install it from the Redistributables folder available in on the CD.
This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.
This release is Unicode-enabled and supports any character set. It supports simultaneous operation with multilingual data. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan.
The Quest Recovery Manager for SharePoint Release Package contains the following:
For installation instructions, refer to Quest Recovery Manager for SharePoint Quick Start Guide.
| info@quest.com | |
| Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA |
|
| Web |
Refer to our Web site for regional and international office information.
Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract.
Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com.
From SupportLink, you can do the following:
View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures.
The guide is available at: http://support.quest.com/pdfs/Global Support Guide.pdf.
This document contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.
© 2009 Quest Software, Inc. ALL RIGHTS RESERVED.
Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Fastlane, Final, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, Internet Weather Report, InTrust, IT Dad, JClass, Jint, JProbe, Knowledge Xpert, LeccoTech, LiteSpeed, LiveReorg, Matrix Insight, Matrix.Net, MIQ, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Speed Change Manager, Speed Coefficient, Spotlight, SQL Firewall, SQL Impact, SQL LiteSpeed, SQL Navigator, SQLab, SQLGuardian, SQLProtector, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Vintela, Virtual DBA, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.
If you have any questions regarding your potential use of this material, contact:
|
Quest Software World Headquarters
LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656 Email: legal@quest.com |
The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.