Release Notes. Autonomy Connected Backup. Contents. Version Revision 1

Transcription

1 R E L E A S E N O T E S Autonomy Connected Backup Version Release Notes Revision 1 This document describes new features and resolved issues for Autonomy Connected Backup. You can retrieve the latest available product documentation from the Autonomy Knowledge Base on the Customer Support site. Contents New in this Release Resolved Issues Requirements Notes Documentation 13 December 2013 Copyright 2009 Autonomy Copyright Corporation 2013 Hewlett-Packard plc and all its affiliates. Development All rights Company, reserved. L.P.

2 Autonomy Connected Backup New in this Release This section lists the enhancements to Autonomy Connected Backup version Multiple language support for PC Agents. PC Agents now support multiple languages. By default, the Agent displays text in the language specified by the computer s Region and Language settings in Control Panel. If the Agent does not support the specified language, it displays text in English (United States). If necessary, you can override the Agent s use of the Region and Language setting so that the Agent displays text in a different language than the operating system. For example, if the Region and Language setting is German, you can configure the Agent to display its text in English (United States). NOTE Agent Setup files (AgentSetup.msi) are locale-specific and do not support multiple languages or support the Region and Language setting of the computer. The Setup file and its Setup Wizard, which performs interactive installations, display text only in the language defined by the Agent version specified in the Agent Configuration. The Agent installed, however, does support multiple languages. For complete details about multiple language support in PC Agents, refer to the Connected Backup Installing PC Agents (English version only). For the list of languages that this release supports, refer to the Connected Backup Application Localization Matrix. Compactor account selection changes. The Compactor no longer selects for compaction accounts that are on hold or reserved. In addition, if you provide Compactor these types of accounts by another method, such as through command line parameters, Compactor does not process them. Expanded operating support for Agents. This release now officially supports the following operating systems: Mac OS X 10.9 (Mavericks), for Mac Agents Windows 8.1, for PC Agents NOTE After you upgrade a client to Windows 8.1, the first time an existing Agent backs up files, it also sends file attribute data for each file in the backup set. This occurs because the OS upgrade causes slight differences in each file s attribute data that the Agent detects and must back up. 2 Autonomy Connected Backup Release Notes

3 Resolved Issues Resolved Issues This section lists the resolved issues in Autonomy Connected Backup version CB Japanese PC Agents now display the End User License Agreement (EULA) in Japanese. Previously, the EULA was in U.S. English. CB In the German versions of the PC Agent, corrected the typographical error in the product name. CB Resolved an issue where Compactor s DiskCache value was used incorrectly on disk-only Data Centers. CB Resolved an issue with Compactor that prevented DCMC from displaying the account currently undergoing compaction and its compaction state. CB Resolved an issue with Compactor that prevented it from compacting accounts in a standalone Data Center environment. CB Resolved an issue where the compaction batch could fill with accounts on hold and therefore prevent Compactor from compacting any active accounts. CB Resolved an issue where in some environments, the Compactor failed to selected canceled accounts for compaction. This release also contains resolutions to several issues that were previously resolved in Connected Backup , but not included in Connected Backup 8.8: CB-37877, CB Resolved an issue that caused backups to fail with ReasonCode <'23'> when the agent erroneously identified a problem with Master File Table (MFT). CB Resolved an issue that caused backups to fail with errors and NAK code 14. When these issues occurred, the Agent sent an invalid message to the Data Center and so the Data Center ended the backup session. CB The registration process was modified to reduce duplicate accounts that could occur in an LDAP Community from a command-line installation. In addition, the Agent now generates a registration.log file that captures information about account registration failures. Autonomy Connected Backup Release Notes 3

4 Autonomy Connected Backup Requirements Autonomy Connected Backup version supports 64-bit standalone, mirrored, or clustered configurations installed as one of the following: new installation upgrade from Connected Backup 8.6, and later For information about the system requirements, supported platforms, and software dependencies for Connected Backup , refer to the Connected Backup 8.8 Requirements Matrix. Notes Single Sign On Support This topic provides Connected Backup installation and upgrade for specific scenarios. If you host your own Connected Backup environment, also refer to Connected Backup Installing the Data Center or Connected Backup Upgrading the Data Center documentation for complete installation or upgrade information. If you plan to enable communities for single-sign on (SSO) support, you must ensure that your Connected Backup environment is correctly configured to support SSO. To do this: Ensure that you have an identity provider that contains the network accounts you plan to use for Connected Backup technician IDs and users accounts. If you host your own Connected Backup environment: Install Connected Backup For information about how to install or upgrade to this release, refer to the Connected Backup Installing the Data Center or Connected Backup Upgrading the Data Center guide. Configure Connected Backup components and the SSO service provider that supports your Connected Backup environment to support SSO. For information about how to configure these items for SSO support, refer to the Connected Backup Administering the Data Center guide. Enable communities for SSO support and create SSO technician IDs and user accounts. For detailed information, refer to Support Center help. 4 Autonomy Connected Backup Release Notes

5 Notes If you do not host your own Connected Backup environment, you need only enable communities for SSO support, and then create SSO technician IDs and user accounts. For detailed information, refer to Support Center help. Upgrade Agents to Connected Backup If your environment contains Connected Backup Agents that do not use the filter driver, you must perform a few additional steps after you install the Data Center to upgrade Agents to this release. To determine whether the filter driver is disabled for an Agent, use Support Center to examine the File Scans setting on the configuration s Agent Settings > Backup page. Before You Begin Install the Connected Backup Data Center. If you plan to use a custom Agent configuration instead of the default Agent configuration, such as one that disables the filter driver, use Support Center to create it. To upgrade Agents that do not use the filter driver to this release 1. In Support Center, enable the filter driver in the Agent configurations associated with your Agents. The File Scans setting on the configuration s Agent Settings > Backup page configures the filter driver option. 2. On a client where an Agent resides, perform the following steps: a. Attempt a backup. Although the backup fails, the Agent receives the updated configuration that enables the filter driver. b. Ensure that the Agent interface is closed, and then restart the AgentService. c. Start the Agent, and then perform a backup. The backup should complete successfully. 3. Use Support Center or Center Administration to change the Agent s configuration to either the default configuration or a custom version, if you created one. 4. On the client, perform a backup to retrieve the new Agent configuration. 5. For each additional Agent you want to upgrade, repeat steps 2 through 4. Autonomy Connected Backup Release Notes 5

6 Autonomy Connected Backup Migration Mode Details and Caveats Connected Backup version 8.8 introduced a migration mode feature that affected the retrieval of files after an account recovery. Starting with version 8.8, during the first backup after an account recovery, the Agent no longer marks for deletion files that reside in the Data Center but are missing from your computer. The introduction of this feature means that if you do not retrieve files before the first post-recovery backup, you can retrieve them after backup regardless of how many backups occurred since you recovered the account. The migration mode feature uses two types of migration mode flags. The first, set in the UserPrefs.xml file on the client, indicates whether the feature is turned on. The second, set internally for each file, identifies files in migration mode those that exist in the Data Center but that you have not yet retrieved to their original location on the client after account recovery. The Agent removes a file from migration mode only after you retrieve it to its original location (that is, to the same exact drive and case-sensitive path). As long as a file is in migration mode, the Agent will not mark it for deletion even though it exists only in the Data Center and not on your local client. There are two common reasons why a file remains in migration mode after an account recovery: 1. You did not retrieve the file, either because you did not need it or you simply forgot. In this case, the file resides only in the Data Center. 2. You retrieved the file, but not to its original location. A copy of the file resides on both the Data Center (original file) and your client (copy). The migration mode feature can be beneficial, such as in case 1. You can retrieve files after an account recovery at your leisure; the Agent will not mark for deletion files you fail to retrieve before your first post-recovery backup. You should understand, however, that there are some caveats when files remain in migration mode. Files that you do not retrieve (case 1) or retrieve to a different location (case 2), impact the backup set size limit, if one exists. When the Agent calculates the current size of your backup set, it includes the size of files in migration mode on the Data Center and the size of the files on your client that you have selected for backup. If you are over the limit, you can remove files from your backup set to return to the limit; however, you can remove only files that exist locally. This is because the Backup panel, which lets you remove files from the backup set, displays local files only. It does not display those that reside only on the Data Center. 6 Autonomy Connected Backup Release Notes

7 Notes To remove from your backup set a file that resides only on the Data Center, you must first retrieve it to its original location. Once the file exists locally, you can do one of the following: Cancel its selection, which removes it from your backup set. Delete it, which removes it from your computer and marks it for deletion from the Data Center. Keep it selected, which enables the Agent to continuously protect it. Files you do not retrieve to their original location (case 2), have the following impact: Increase to the amount of Data Center storage required to store files of recovered accounts. Seemingly duplicate files available for retrieval from the Agent. The Agent Retrieve panel displays two copies of the file for retrieval the original one that resides only in the Data Center and the one you retrieved to a different location and continue to protect through backups. To ensure that you select the most recent copy of the file, you can search for files to retrieve, and then either filter results by modification date or select to view only the most recent version of files. To avoid issues that might arise due to these caveats, we highly recommend that you retrieve all files after an account recovery to their original location. To ensure that you do not encounter these issues in situations where you do not want to retrieve all files or cannot retrieve files to their original locations, you can turn off migration mode. For example, if you use account recovery to restore users data during mass migrations, such as when migrating users to a new operating system (OS), you might want to turn off migration mode on each computer. Different operating systems use different folder hierarchies so you cannot retrieve user data backed up from one OS to the same exact location on a computer with a different OS. Just remember, turning off this feature reverts Agent functionality to the same as in previous Connected Backup releases the Agent will mark for deletion all files you do not retrieve before your first post-recovery backup. To turn off the migration mode feature on the Agent 1. On the client, turn off the migration mode feature for the Agent. In installdrive\programdata\autonomy\connected Backup\ UserPrefs.xml, set the MigrationModeActive element to 0: <MigrationModeActive>0</MigrationModeActive> 2. Restart the Agent Service. Autonomy Connected Backup Release Notes 7

8 Autonomy Connected Backup 3. Perform a backup. During backup, all files in the Data Center that do not exist locally are marked for deletion from the Data Center. Compactor will remove these files from the Data Center over time due according to its file expiration rules. After backup, the Agent no longer displays files it marked for deletion on its Retrieve panel or includes their size in its calculation of the current backup set size. NOTE Each account recovery turns migration mode on. Therefore, if you turn it off and then later perform another account recovery that does not recover files to their original location, you might want to perform this task again to turn migration mode off. Documentation The following documentation was updated for this release. Connected Backup Application Localization Matrix Connected Backup Documentation Localization Matrix Connected Backup Installing PC Agents (English version only) Connected Backup Requirements Matrix A Japanese version of the following Connected Backup 8.8 documentation was provided for this release: Connected Backup Administering PC Agents Connected Backup Installing PC Agents Connected Backup for PC Agent Quick Start You can retrieve the current product documentation from the Autonomy Knowledge Base on the Customer Support Site. A document in the Knowledge Base displays a version number in its name, such as IDOL Server 7.5 Administration Guide. The version number applies to the product that the document describes. The document may also have a revision number in its name, such as IDOL Server 7.5 Administration Guide Revision 6. The revision number applies to the document and indicates that there were revisions to the document since its original release. Periodically check the Knowledge Base for revisions to documents for the products your enterprise uses. 8 Autonomy Connected Backup Release Notes

9 Documentation To access Autonomy documentation 1. Go to the Autonomy Customer Support site: 2. Click Login. 3. Type the login credentials that you were given, and then click Login. The Customer Support Site opens. 4. Click Knowledge Base. The Knowledge Base Search page opens. 5. Search or browse the Knowledge Base. To search the knowledge base a. In the Search box, type a search term or phrase and click Search. Documents that match the query display in a results list. To browse the knowledge base a. Select one or more of the categories in the Browse list. You can browse by: Repository. Filters the list by Documentation produced by technical publications, or Solutions to Technical Support cases. Product Family. Filters the list by product suite or division. For example, you could retrieve documents related to the imanage, IDOL, Virage or KeyView product suites. Product. Filters the list by product. For example, you could retrieve documents related to IDOL Server, Virage Videologger, or KeyView Filter. Version. Filters the list by product or component version number. Type. Filters the list by document type. For example, you could retrieve Guides, Help, Packages (ZIP files), or Release Notes. Format. Filters the list by document format. For example, you could retrieve documents in PDF or HTML format. Guides are typically provided in both PDF and HTML format. 6. To open a document, click its title in the results list. To download a PDF version of a guide, open the PDF version, click the Download icon in the PDF reader, and save the PDF to another location. Autonomy Connected Backup Release Notes 9

10 Autonomy Connected Backup To download a documentation ZIP package, click Get Documentation Package under the document title in the results list. Alternatively, browse to the desired ZIP package by selecting either the Packages document Type or the ZIP document Format from the Browse list. 10 Autonomy Connected Backup Release Notes