CA Recovery Point Server. User Guide

Transcription

1 CA Recovery Point Server User Guide

2 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation ) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice. The manufacturer of this Documentation is CA. Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (b)(3), as applicable, or their successors. Copyright 2012 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

3 CA Technologies Product References This document references the following CA Technologies products: CA ARCserve Backup CA ARCserve D2D CA ARCserve Replication and High Availability CA ARCserve Central Host-Based VM Backup CA ARCserve Central Protection Manager CA ARCserve Central Reporting CA ARCserve Central Virtual Standby Contact CA Contact CA Support For your convenience, CA Technologies provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA Technologies products. At you can access the following: Online and telephone contact information for technical assistance and customer services Information about user communities and forums Product and documentation downloads CA Support policies and guidelines Other helpful resources appropriate for your product Providing Feedback About Product Documentation If you have comments or questions about CA Technologies product documentation, you can send a message to techpubs@ca.com. If you would like to provide feedback about CA Technologies product documentation, complete our short customer survey, which is available on the CA Support website at

4

5 Contents Chapter 1: Introducing CA Recovery Point Server 7 Chapter 2: Packages and Installation 11 Chapter 3: Central Management 13 Add Nodes Remotely Deploy CA Recovery Point Server from the Application Chapter 4: Basic Configuration 17 Create a Data Store Import an Existing Data Store Modify or Delete a Data Store Configuring CA Recovery Point Server Protection Specify Data Store Settings Define Retention Settings Enable Optional Replication Settings Chapter 5: CA Recovery Point Server Use Cases 27 Specify RPS in CA ARCserve D2D Backup Job Configuring Complex RPO Hierarchies Create Advanced Retention Policy Specify a Chain of Replication Targets Restoring from CA Recovery Point Server Restore Methods Restore by Recovery Point Restore by Find File/Folder Restore Exchange Mail Application Restore Restore from Windows Explorer Using ARCserve D2D View Chapter 6: Managing Performance 81 Monitoring Performance Contents 5

6

7 Chapter 1: Introducing CA Recovery Point Server Chapter 1: Introducing CA Recovery Point Server 7

8 Add Nodes CA Recovery Point Server is a server that acts as a backup or replication target. These servers centrally store recovery points, which are the production machine backup images generated by CA ARCserve D2D. Storing recovery points on RPS nodes off-loads post-backup processing (such as catalog generation and recovery point merging) from your production servers. Additional features: Offers Client-side and server-side deduplication to save network bandwidth and conserve disk space Supports multiple levels of recovery point replication within the LAN and over WAN. Allows you to retain different combinations of the most recent, daily, weekly, or monthly recovery points on multiple levels of RPS nodes (RPO Hierarchy). With CA ARCserve Central Protection Manager, lets you centrally deploy and manage RPS nodes, define data stores, configure policies, monitor activities, generate reports, and manage recovery points. Integrates with other ARCserve products including CA ARCserve Central Host-Based VM Backup and CA ARCserve Central Virtual Conversion Manager so you can centrally protect virtual machines and convert physical machine recovery points to virtual machines. 8 User Guide

9 Add Nodes Next Steps Install CA Recovery Point Server (see page 11) Centrally Manage Nodes (see page 13) Configure CA Recovery Point Server (see page 17) Read CA Recovery Point Server Use Cases (see page 27) Manage Performance (see page 81) Chapter 1: Introducing CA Recovery Point Server 9

10

11 Chapter 2: Packages and Installation CA Recovery Point Server is an integrated solution that requires the following: CA ARCserve Central Protection Manager -- This application functions as the CA Recovery Point Server user interface so you can centrally manage your recovery points, the nodes that perform backup and restore jobs and the nodes that store recovery points. Recovery Point Server -- This is the software component that allows you to establish a node as a media server in CA ARCserve D2D backup jobs or CA Recovery Point Server replication jobs. CA ARCserve D2D -- This is the software application that actually performs your backups. You can manage installations of this application from CA ARCserve Central Protection Manager or log in directly to each instance to define local backup and restore policies. You can use the CA ARCserve Central Protection Manager to remotely deploy CA Recovery Point Server and CA ARCserve D2D or install them locally. Chapter 2: Packages and Installation 11

12

13 Chapter 3: Central Management You can use the manager interface to add nodes, or remotely deploy CA Recovery Point Server so that managed nodes can be used as backup or replication targets. What Do You Want to Do? Add Nodes (see page 13) Remotely Deploy CA Recovery Point Server (see page 14) This section contains the following topics: Add Nodes (see page 13) Remotely Deploy CA Recovery Point Server from the Application (see page 14) Add Nodes Adding nodes lets you manage policies and data stores as well as the installed products for all protected nodes from a single view for easier management. You can add nodes by IP address or host name, or from a file. In all options, provide the server name, user name and password. You can also add nodes automatically using Deployment. Chapter 3: Central Management 13

14 Remotely Deploy CA Recovery Point Server from the Application Follow these steps: 1. Click Add in the Node category on the toolbar. You can also Edit or Delete nodes from the toolbar. You can add nodes by IP/Name or import nodes from a file. To add nodes by IP or Node Name, complete the following fields: IP/Node Name -- Enter the IP address or host name of the node you want to manage. (Optional) Description -- Type text that describes the function of this node. User Name and Password -- Enter the appropriate credentials to log in. You may need to enter in domain name\username format. To add nodes from a file, complete the following fields: Click Browse to locate the file that lists the nodes in CSV format that you want to add. Click Upload. Wait while the upload is completed. Click Next. The nodes listed in the file are added to the list and verified. (Optional) On the Node Credentials screen, click to select specific nodes or provide a global user name and password to apply to all. Click Finish. The nodes are added. 2. Click OK. The nodes are added to the Node Name list. Note: To delete nodes from the Node Name list, highlight the node and click Delete from the Node category. To view logs for a node, expand All Nodes from the Groups list, select the desired node and click View Logs. Next Steps: Remotely Deploy CA Recovery Point Server (see page 14) Remotely Deploy CA Recovery Point Server from the Application The interface allows you to deploy CA Recovery Point Server to other nodes. The Deployment operation automatically adds nodes to the All Nodes group. 14 User Guide

15 Remotely Deploy CA Recovery Point Server from the Application Follow these steps: 1. Click Deployment from the Actions group on the toolbar. The License Agreement opens. 2. Scroll down to enable the option, I accept the terms of the License Agreement and click it. If you want, you may prevent the license from appearing. Click the option, Do not show this License Agreement again. 3. Click Next. 4. On the Deployment dialog, click Add to add servers to the list. a. On the Add dialog, specify the Server Name, User Name and password, the Port and Install Path. b. Click Allow setup to install the driver. c. Select the desired reboot and HTTPS options. d. Click OK. The server is added to the Deployment list. 5. Click the check box next to each server where you want to deploy software components. 6. Click Deploy Now. 7. Wait while a connection is established and installation is performed. 8. Click Close. Next Steps: After you deploy software components to nodes, you can use those nodes as backup targets in a CA ARCserve D2D policy or as replication targets in a CA Recovery Point Server policy. Configuring Simple Policies (see page 20) Configuring Complex RPO Hierarchies (see page 28) Specify RPS in CA ARCserve D2D Backup Job (see page 27) Chapter 3: Central Management 15

16

17 Chapter 4: Basic Configuration After you deploy CA Recovery Point Server, perform these tasks for basic operation. 1. Manage Data Stores 2. Configure Simple Policies This section contains the following topics: Create a Data Store (see page 17) Import an Existing Data Store (see page 19) Modify or Delete a Data Store (see page 19) Configuring CA Recovery Point Server Protection (see page 20) Create a Data Store Data stores are the folders where your recovery points are saved. When you create a policy, choose a data store from the list that has the options you need enabled. You can create data stores in two ways: 1. From the New Policy dialog, on the Data Store settings screen 2. From the New Data Store dialog. This procedure explains how to create data stores using the New Data Store dialog. Follow these steps: 1. Click a node to select it and then click Add from the Data Store category. 2. You can create a new data store directly or from an existing path. Choose New Data Store. The New Data Store dialog opens. 3. Enter a Data Store Name. 4. Enter or browse to a Backup Destination Path. This is where your recovery points are stored. 5. Complete the following fields on the Data Store Settings screen: Chapter 4: Basic Configuration 17

18 Create a Data Store New Data Store Name Type a name for the data store you want to create. Tip: Use meaningful names that describe the options that you enabled. Backup Destination Path Specify or browse to the shared folder where you want to store recovery points. (Optional) Enable Encryption If you enable this option, specify the Encryption Algorithm and password. You can choose AES-128, AES-192, or AES-256. The default selection is AES-128. Note: Each RPS data store uses its the encryption key specified here for locally managed data. For encryption over the network, consider using HTTPS protocol. (Optional) Enable Compression If you enable this option, choose the Compression Type. You can choose Standard or Max Compression. Max Compression saves the most space but uses more RAM. Standard Compression is the default selection. (Optional) Enable Deduplication If you enable deduplication, specify the following: 6. Click Save. Memory Size -- use the slider to specify how much memory to allocate to deduplication processing. Use Solid State Disk (SSD) to extend deduplication capacity -- enable this option if you wish to store hash values in memory to speed up processing. If you enable this option, specify the Hash Path drive and folder. Use the slider to set the size of the SSD. Deduplication Block Size -- Your data is divided into chunks of the size that is specified here to prepare for deduplication. Smaller size chunks are recommended for database applications but do slow performance. The default size is 4 KB. Use the slider to set the value. Deduplication Ratio Assumption -- Use the slider to calculate how much storage space is required, given the current settings. Adjust as needed. Enable Advanced Settings -- Click this option to specify additional paths. Specify an Index File Path. This path is the location where the deduplication meta file is stored and can be on a different disk, if needed. Specify a Data File Path. This path is the location where you want to save your deduplicated data. This path can also be on the same or a different disk. Specify a Hash File Path. This path is the location where hash values are assigned and compared during the deduplication process. 18 User Guide

19 Import an Existing Data Store Import an Existing Data Store If you want to use a data store where recovery points already exist, use the Add, Data Store with Existing Path option. This option does not create a new data store. It imports an existing one. This option is good for moving a data store from one RPS node to another. Note: You must know the original backup destination path to use this option. Suppose you had a data store that was saving recovery points to a folder called D:\FSD1. Follow these steps: 1. Click a node and then click Add from the Data Store category. 2. Click Data Store With Existing Path. The New Data Store dialog opens. 3. Enter a new name for the data store you wish to use. 4. Specify or browse to the original path, in this example: D:\FSD1. 5. Enable Encryption if you want. Specify the password. 6. Enable Deduplication if you want. Specify the Index, Data, and Hash Files paths. Like the Backup Destination Path, these should also be the original values. 7. Click Save. The data store is added. Modify or Delete a Data Store When you are in Node view, the Modify and Delete options under the Data Store category are dim. Follow these steps: 1. Expand All Nodes in the Groups list. 2. Select a node. 3. In the Data Stores list, click anywhere on the data store entry to highlight it. 4. Click Delete to remove the data store directly or click Modify to open the Modify Data Store dialog. 5. Make the desired changes. 6. Click Save. Chapter 4: Basic Configuration 19

20 Configuring CA Recovery Point Server Protection Configuring CA Recovery Point Server Protection CA Recovery Point Server is a policy-based application that integrates with CA ARCserve D2D. Create policies on the nodes you want to use as either backup destinations for CA ARCserve D2D jobs or as replication targets in other CA Recovery Point Server jobs. A policy is comprised of the following settings: Data Store -- this field is the path to the network share where your recovery points are stored. You can enable encryption, deduplication, or compression on any data store. You can assign more than one data store to an RPS node. Select the data store you want to use on the Basic Settings screen of the New Policy dialog. Basic Settings -- specify retention settings (how many recovery points to store on the RPS source node) and the schedule to process them. Replication Settings -- (optional) specify an RPS target node to store recovery points that are copied from this source. Next, define the replication and make-up job schedules. Choose a policy from the list of assigned target node policies. Remember to define policies on the target node first and then create the source node policy. You cannot save a policy on a source node if the policy selection field on the Replication Settings screen is blank. Alerts -- (optional) Select the conditions that trigger notification such as failed jobs or disk space alerts. Protection is triggered when you select Use RPS in the CA ARCserve D2D backup destination field and specify the policy that you want to use. The server you specify can be local, remote, or in the cloud (a service provider). 20 User Guide

21 Configuring CA Recovery Point Server Protection Create policies as illustrated in the diagram. Follow these steps: 1. Create Data Instance Stores (see page 21) 2. Specify Basic Settings (see page 24) 3. (Optional) Define Replication Settings (see page 25) 4. Set up Alerts in a Policy 5. Define RPS in D2D Backup Job (see page 27) Specify Data Store Settings This procedure explains how to create new data stores directly from the New Policy dialog. Chapter 4: Basic Configuration 21

22 Configuring CA Recovery Point Server Protection Follow these steps: 1. Click a node and then click Add from the Policy category. The New Policy dialog opens and shows the Data Store Settings screen by default. 2. Complete the following fields on the Data Store Settings screen: Data Store Settings Choose an existing data store from the dropdown list or create a new one. You can create a new one by completing the New Data Store fields or by choosing an existing data store from the list and clicking Clone. 3. Complete the following fields on the Data Store Settings screen: New Data Store Name Type a name for the data store you want to create. Tip: Use meaningful names that describe the options that you enabled. Backup Destination Path Specify or browse to the shared folder where you want to store recovery points. (Optional) Enable Encryption If you enable this option, specify the Encryption Algorithm and password. You can choose AES-128, AES-192, or AES-256. The default selection is AES-128. Note: Each RPS data store uses its the encryption key specified here for locally managed data. For encryption over the network, consider using HTTPS protocol. (Optional) Enable Compression If you enable this option, choose the Compression Type. You can choose Standard or Max Compression. Max Compression saves the most space but uses more RAM. Standard Compression is the default selection. 22 User Guide

23 Configuring CA Recovery Point Server Protection (Optional) Enable Deduplication If you enable deduplication, specify the following: 4. Click Save. Memory Size -- use the slider to specify how much memory to allocate to deduplication processing. Use Solid State Disk (SSD) to extend deduplication capacity -- enable this option if you wish to store hash values in memory to speed up processing. If you enable this option, specify the Hash Path drive and folder. Use the slider to set the size of the SSD. Deduplication Block Size -- Your data is divided into chunks of the size that is specified here to prepare for deduplication. Smaller size chunks are recommended for database applications but do slow performance. The default size is 4 KB. Use the slider to set the value. Deduplication Ratio Assumption -- Use the slider to calculate how much storage space is required, given the current settings. Adjust as needed. Enable Advanced Settings -- Click this option to specify additional paths. Specify an Index File Path. This path is the location where the deduplication meta file is stored and can be on a different disk, if needed. Specify a Data File Path. This path is the location where you want to save your deduplicated data. This path can also be on the same or a different disk. Specify a Hash File Path. This path is the location where hash values are assigned and compared during the deduplication process. 5. Repeat these steps to create additional data stores. Next Steps: (Optional) Define Replication Settings (see page 25) Define Retention Settings (see page 24) Chapter 4: Basic Configuration 23

24 Configuring CA Recovery Point Server Protection Define Retention Settings The Basic Settings screen lets you enable catalog generation, set retention policies, and define the recovery points processing schedule. Retention settings are required in all policies. How the Retention Settings Works The value you specify in the field called the Number of Most Recent Recovery Points controls merge/purge operations. The value for N can be any number. (31 is the default). Tips for Setting the Number of Recovery Points to Keep If you are backing up... Set the Value of n to To keep... Hourly 4 4 hours of recovery points Hourly 24 1 day of recovery points Every 4 hours 6 1 day of recovery points Daily 31 (Default value) 1 month of recovery points Follow these steps: 1. Create a New Policy either from a node shortcut menu or from the Add, Policy group. The New Policy dialog opens. 2. Click the Basic Settings screen and specify the following settings: (Optional) Enable Catalog Generating Enable this option to generate the catalog at backup time. The catalog is required to perform granular Exchange restores. 24 User Guide

25 Configuring CA Recovery Point Server Protection Retention Settings Specify the number of most recent backups to always save. This value is any combination of full, incremental, and verify backup jobs. When the value is exceeded, the oldest backup is merged/purged if no advanced retention policy is met. The default value is 31. (Optional) Enable advanced retention policies For more control over retention, enable this option and specify the number of daily, weekly, and monthly backups to retain. Advanced Retention Policies let you establish complex RPO (Recovery Points Objective) hierarchies. The default values are 7 daily, 4 weekly, and 1 monthly retained recovery points. Recovery Points Processing Schedule 3. Click Save. Set the schedule that determines when to start processing recovery points. You can choose immediate processing, or specify the number of hours after a job is finished, as well as the specific time of day or week. Your retention settings are saved. Next Steps: (Optional) Enable Replication Settings (see page 25) Define settings on the CA ARCserve D2D server that will back up to this CA Recovery Point Server. (see page 27) Enable Optional Replication Settings Replication settings are optional. Replication, when enabled, lets you copy recovery points from the source node specified in one policy to a target node, where other policies are assigned. By creating policies that, in turn, specify other policies, you can create complex RPO (recovery point objective) hierarchies to satisfy your SLAs (service level agreements). Policies that are assigned to the target node appear in the Policy list on the Replication Settings screen. Choose a policy to apply. You cannot save replication settings on a source node when there are no policies on the desired target node. Define policies on your final target first and work your way backwards. This procedure explains how to define replication settings on a source server. Before you begin, verify that policies have been assigned to the target server. To do so, find the target server on the Node screen and verify the Policy Count is not 0. If it is 0, assign policies to that server first and work backwards. Chapter 4: Basic Configuration 25

26 Configuring CA Recovery Point Server Protection Follow these steps: 1. From the Policies view, click Add Policy. Or, click Edit to modify an existing policy. 2. On the Policy dialog, click Replication Settings. a. Click the option, Enable Replication Settings. b. In the Replication Target Settings section, specify the following information: Hostname Policy Enter the name of the CA Recovery Point Server node where you want to save the recovery points replicated from the source server. This value is always the next server forward in your series. For example, if you are creating policies on RPS2, specify the hostname of RPS3 as the value for this field. Specify the Port, Protocol, Username and password for this server. Select a policy from the list of policies that were assigned to the server you specified as the target. This policy could include additional replication settings. Enable Bandwidth Throttle Settings Enable this option to specify a Simple or Advanced setting. For Simple Bandwidth Throttling, specify the number of MB per minute. The default is 100. For Advanced Bandwidth Throttling, click the Day and then click Add New Bandwidth Throttle to open the Add Bandwidth Throttle Settings dialog. Specify the Start and End Times and the MB per minute value. Click OK. The setting is added to the list. If you want, click Copy Bandwidth Throttle Schedule to extend an existing setting to additional days. c. In the Replication Schedule section, click a Replication Start Time. d. In the Makeup Job Schedule section, set the desired options. These options control when to launch a makeup job and how many attempts the job makes when replication fails. e. If you want to control how the application uses network bandwidth, enable Throttling. Click Add New Throttling. Specify the Start and End Times and the maximum write speed. You can add multiple throttling settings. Click OK when done. 3. Click Save. Next Steps: Define Retention Settings (see page 24) (Retention settings are required.) Specify RPS in <ccadr> Backup Job (see page 27) 26 User Guide

27 Chapter 5: CA Recovery Point Server Use Cases This section contains the following topics: Specify RPS in CA ARCserve D2D Backup Job (see page 27) Configuring Complex RPO Hierarchies (see page 28) Restoring from CA Recovery Point Server (see page 34) Specify RPS in CA ARCserve D2D Backup Job CA Recovery Point Server does not perform backup jobs directly. It integrates with CA ARCserve D2D so that you can specify RPS nodes as backup destinations to centrally manage the recovery points CA ARCserve D2D creates. Follow these steps: 1. From CA ARCserve Central Protection Manager, log in to the appropriate CA ARCserve D2D node and click Settings. The Settings dialog opens. 2. From the Protection Settings screen, click Use CA Recovery Points Server as the backup destination. The Protection Settings screen updates to show the RPS related fields. 3. Specify the following: a. Hostname -- Enter the RPS node where you defined the policy you want to use to manage this CA ARCserve D2D backup job. b. Username, Password -- Provide login credentials for the node you specified. c. Port--The default is d. Protocol--Select HTTP or HTTPS. e. Policy--Select the appropriate policy from the list. If no policy appears, return to the manager interface and make sure you defined policies on the RPS node specified as the backup destination. Chapter 5: CA Recovery Point Server Use Cases 27

28 Configuring Complex RPO Hierarchies The Policy Summary section lists the data store settings defined in the policy you selected. 4. Specify the remaining CA ARCserve D2D backup settings, as usual. Note that only the CA ARCserve D2D Protection Settings are applied to your RPS node. File Copy and Copy Recovery Point settings in CA ARCserve D2D are not supported in CA Recovery Point Server. 5. Save your settings. You can click Backup Now or wait for until the schedule settings trigger a backup job. The backup job triggers recovery point processing on your RPS nodes according to the policies you defined. Configuring Complex RPO Hierarchies The policy-based protection designed into CA Recovery Point Server lets you construct complex RPO (Recovery Point Objective) Hierarchies. Examples: Define Advanced Retention Settings to store a week's worth of daily backups, a month's worth of weekly backups and a year's worth of monthly backups. Connect a series of RPS nodes together in a replication chain, each with a different retention policy. 28 User Guide

29 Configuring Complex RPO Hierarchies Prerequisites: This scenario presumes that you have already added RPS nodes to the list, created data stores, and know how to create simple policies. What do you want to do? Create Advanced Retention Policy (see page 29) Specify a Chain of Replication Targets (see page 32) Create Advanced Retention Policy Retention settings specify the quantity, time period, and type of recovery points to store on the assigned server. Retention settings are required in all CA Recovery Point Server policies. Retention is continual; recovery points are kept only as long as they satisfy a retention setting and then they are merged/purged off the data store. Number of Recovery Points to Keep - This setting directs the application to keep the most recent n recovery points, regardless of type. This setting protects your data from loss due to network outages or hardware failures during the backup or replication operation. When the value of n is exceeded and Advanced Retention Policies are not enabled, the oldest stored recovery point is merged/purged with the next oldest to form a new baseline. In this manner, the number of stored normal recovery points is maintained at the value that you set for n. Chapter 5: CA Recovery Point Server Use Cases 29

30 Configuring Complex RPO Hierarchies Advanced Retention Settings - These fields let you specify the number of Daily, Weekly, or Monthly recovery points to store on a long-term basis. You can set one or all of these values, according to your needs. Retaining seven daily backups gives you a week of recovery points, four weekly backups is a month of recovery points, and so on. The default values are 7 daily, 4 weekly and 1 monthly backups to retain. Recovery points are stored on a rolling basis only while they satisfy a retention setting. At times when a recovery point satisfies more than one retention setting, it is saved only once. Note: You can combine normal and advanced settings as long as the total number of retained recovery points does not exceed Example: Perform backups every 6 hours. To simplify this example, specify 4 as the Number of Recovery Points to Save (N) so that one full day of backups is always kept, but note that the default value is 31. Keep the default values for the Advanced Retention Settings: Daily = 7, Weekly = 4, Monthly = 3. Normal backups occur every 6 hours and are shown as gray bars on the diagram. The value for N is set to 4 to keep recovery points for the last day but N can be set to any value up to 31. Daily backups are shown as green bars in the diagram and the number of daily backups to keep is set to 7. Weekly backups are shown as blue bars. The number of weekly backups to keep is set to 4. Note, a monthly backup is not shown because the current time is the end of week User Guide

31 Configuring Complex RPO Hierarchies It is now the end of the day at the end of the second week. To date, 56 backups were performed every 6 hours. All normal backup recovery points were merged/purged off the data store according to the retention policy set, except for the last 4, backups 53, 54, 55, and 56, plus six green bars, and one blue bar. These recovery points were skipped from the merge/purge operation because they satisfy a Daily (D=7) or Weekly (W=4) retention setting. What Happens Next? The 57th backup triggers merge/purge of the 53rd, and so on until the 60th backup. The 60th backup is kept because it is also a Daily, which brings the total number of green bars to 7. The next Daily backup (the 64th) will merge/purge the 32nd backup into the 36th, because they are the oldest daily recovery points. Normal and Daily backups continue the retain/merge/purge cycle until the 84th backup. This is the third Weekly backup and adds another blue line to the table. Nothing is purged because the number of weekly backups to keep is set to 4. Backups continue. At the 112th backup, the resulting recovery point now satisfies the Monthly Retention Setting. Prerequisites: This procedure assumes that you already know how to add nodes, and create policies and data stores. Follow these steps: 1. On the source node, click New under the Policy category. The New Policy dialog opens. 2. Complete the Data Store Settings as usual. 3. On the Basic Settings screen, specify the Retention Settings. The default value is 31. This value is a rolling setting and helps you recover from unplanned interruptions like a network outage or hardware failure. 4. Click the option, Enable Advanced Retention Policies. 5. Enter a value for the number of Daily, Weekly, and Monthly recovery points to store on the data store. The default values are 7 Daily, 4 Weekly, and 1 Monthly. These values are long-term retention settings and let you set up complex hierarchies. 6. Complete the remaining New Policy screens as usual. 7. Click Save. Your advanced retention settings take effect with the next scheduled CA ARCserve D2D backup. Chapter 5: CA Recovery Point Server Use Cases 31

32 Configuring Complex RPO Hierarchies Specify a Chain of Replication Targets Replication, when enabled, lets you copy recovery points from the source node (the node where you are creating a policy) specified in one policy to a target node. Any target node can be the source node in another policy. By creating policies that specify other nodes and policies, you can define complex RPO hierarchies to satisfy your SLAs (service level agreements) for recovery. Policies that you assigned to a target node appear in the Replication Target Settings Policy selection list when you create a policy on another node. If no policies are shown in the selection list, you cannot save the policy. Make sure you define policies on each target node first and work backwards to the source. 32 User Guide

33 Configuring Complex RPO Hierarchies Example: Suppose that you want to replicate the recovery points created when a server called D2D 1 performs a backup job. You have four nodes in your RPS Node list: RPS 1, RPS 2, RPS 3, and RPS 4. These nodes can be local or remote or even in the cloud. Replication policies always require a source and a target node. Node pairs are in shaded boxes on the diagram. When you specify a target node in a source node policy, also choose one of the policies that were assigned to that target. If the target node has no policies, you cannot save the source node policy. Therefore, define policies on RPS 4, then RPS 3, RPS 2, RPS 1, and finally, D2D 1. The Policy Definition Steps shown in the diagram correspond to the process. Follow this process: 1. On RPS 4, create a policy with no replication enabled. This node is your final server in the series so replication is not needed. If you add nodes later, you can modify this policy to enable replication and specify a target node. 2. On RPS 3, create a policy with replication enabled. Remember that RPS 3 is the source node and RPS 4 is now the target node. Specify RPS 4 as the target on the Replication Settings screen. Choose the policy that you created on RPS 4 (step 1) that does not have replication enabled. Chapter 5: CA Recovery Point Server Use Cases 33

34 3. RPS 2 is now the source node and RPS 3 is now its target. Create a policy with replication enabled. Specify RPS 3 as the target on the Replication Settings screen. Choose the policy that you created on RPS 3 (step 2) to replicate recovery points to RPS RPS 1 is now the source node and RPS 2 is now its target. Create a policy with replication enabled. Specify RPS 2 as the target on the Replication Settings screen. Choose the policy that you created on RPS 2 (step 3) to replicate recovery points to RPS D2D 1 is now the source and RPS 1 is now its target. Create a CA ARCserve D2D policy and click Use RPS as the backup destination. Specify RPS 1 as the backup destination and then specify the policy you created (step 4) to replicate recovery points to RPS 2. Backup and replication jobs are triggered when the backup schedule defined in CA ARCserve D2D launches, or when you click Backup Now. The backup job stores recovery points on RPS 1, which then replicates those recovery points from RPS 1 to RPS 2. The policy on RPS 2 replicates to RPS 3. The policy on RPS 3 replicates to RPS 4. Replication is the blue arrow on the diagram. Important Note about Global Deduplication -- If you enabled deduplication on any data store in the chain, do so for all data stores. You cannot perform deduplication on only one Source/Target node pair. Restoring from CA Recovery Point Server Restoring data stored on CA Recovery Point Server nodes works as it did from CA ARCserve D2D. Decide what information you want to restore and then perform the appropriate procedure. 34 User Guide

35 Note: CA Recovery Point Server does not support all CA ARCserve D2D Restore Methods. In this release, Restore File Copies, Restore VMs, and Generate an Exchange Granular Restore Catalog before Restore are not supported. Follow these steps: 1. Decide what information to restore 2. Perform one of the following restore procedures Browse Recovery Points Find Files/Folders Restore Exchange Mail Chapter 5: CA Recovery Point Server Use Cases 35

36 Restore Methods The goal of running a successful restore job is to identify quickly the data you need and to retrieve it from the appropriate backup location. CA ARCserve D2D provides various methods to identify and locate the backed up data and allow you to restore it. Regardless of the restore method you select, CA ARCserve D2D uses visual indicators (restore markers) of the objects that are or are not selected for restore. For more information, see Restore Markers (see page 38). Note: CA ARCserve D2D only allows one restore job to run at the same time. If you attempt to launch manually a restore job now, and during that time another restore job is currently running an alert message opens informing you another job is running and requesting you try again at a later time. Restore data 1. From the CA ARCserve D2D home page (or CA ARCserve D2D Monitor), select Restore. The restore methods selection dialog opens. 36 User Guide

37 2. Select the type of restore you want to perform. The available options are Browse Recovery Points, Browse File Copies, Find Files/Folders to Restore, Recover VM, and Restore Exchange Mails. Note: Use the Browse Recovery Points if you want to restore any applications. Browse Recovery Points Lets you browse the available recovery points (successful backups) from a calendar view. The calendar dates that contain valid recovery points are highlighted in green. When you select a recovery date, all the associated recovery points for that date are displayed. You can then browse and select the backup content (including applications) to be restored. For more information, see Restore by Recovery Points. Browse File Copies Lets you browse the available File Copy locations (local disk/network drive or cloud) to locate the specific file or folder that is going to be restored. For more information, see Restore from File Copies. Find Files/Folders to Restore Lets you search for a file name pattern in a specific location and or the file version that is going to be restored. For more information, see Restore by Find File/Folder (see page 44). Recover VM Lets you browse the available virtual machine recovery points from a calendar view. The calendar dates that contain valid recovery points are highlighted in green. When you select a recovery date, all the associated virtual machine recovery points for that date are displayed. You can then browse and select the virtual machine content that is going to be restored. For more information, see Recover VM. Restore Exchange Mails Lets you browse and select individual objects within an Exchange database to perform a granular-level restore. For more information, see Restore Exchange Mails (see page 50). Chapter 5: CA Recovery Point Server Use Cases 37

38 Restore Markers Regardless of which restore method you select, when you navigate to a specific volume, folder, or file to restore, each object displayed in the restore window has a green or gray box to its left called a marker. These markers are visual indicators of the objects that are or are not selected for restore. Green marker Lets you control the extent of the restore for an object directly. Click a marker to exclude an object from a restore or to indicate that you want the restore for the object to be full or partial. As you click the marker, you fill or empty the marker of color, indicating the extent of the restore. Gray marker These markers are associated with objects that are not real and that you cannot restore. Typically, these items serve as placeholders under which other objects are grouped and displayed. As you click the green markers under a gray marker item, the fill proportion of the gray marker changes automatically from empty to partial to full depending on the proportion of files you have chosen to restore. The following table describes the different marker configurations and corresponding restore levels: Marker Configuration Description Completely filled center. Full restore. Partially filled center. Partial restore. Empty center. Do not restore. Note: Gray marker configurations follow the same pattern as green marker configurations, but reflect the proportion of files under them that are selected for restore. 38 User Guide

39 The fill proportion of a marker at a higher level of the directory tree depends on the fill proportions of the markers of the objects at the lower levels. If all the markers at the lower levels are completely filled, then the marker at the higher level is also automatically completely filled. If the markers at the lower levels are a mix of completely filled and partially filled, then the marker at the higher level is automatically partially filled. If you click a marker at a higher level so that it is completely filled, then all the markers at the lower levels are automatically filled completely. Restore by Recovery Point Each time CA ARCserve D2D performs a successful backup, a point-in-time snapshot image of your backup is also created. This collection of recovery points allows you to locate and specify exactly which backup image you want to restore. Restore from a recovery point 1. From the home screen, select Restore. The restore methods selection dialog opens. 2. Click the Browse Recovery Points option. The Browse Recovery Points dialog opens. 3. Specify the location type: RPS Server. When you select this option, the name of the CA Recovery Point Server node is shown as the backup location. Click Change RPS Server to change it. Enter new server credentials and then select the CA ARCserve D2D host used to perform the backup from the list. Click OK. The calendar view highlights (in green) all dates during the displayed time period that contain recovery points for that backup source. 4. Specify the information to restore. a. Select the calendar date for the backup image you want to restore. The corresponding recovery points for that date are displayed, with the time of the backup, the type of backup that was performed, and the name of the backup. b. Select a recovery point that you want to restore. The corresponding backup content (including any applications) for that recovery point is displayed. Note: A clock icon with a lock symbol indicates the recovery point contains encrypted information and may require a password for restore. Chapter 5: CA Recovery Point Server Use Cases 39

40 R Restoring from CA Recovery Point Server c. Select the content to be restored. For a volume-level restore, you can specify to restore the entire volume or selected files/folders within the volume. For an application-level restore, you can specify to restore the entire application or selected components, databases, instances, and so on, within the application. 5. When the backup information to be restored is specified, click Next. The Restore Options dialog is displayed. 40 User Guide

41 6. Select the destination for the restore. The available options are to restore to the original location of the backup or restore to a different location. Restore to Original Location Restores to the original location from where the backup image was captured. Restore to: You can either specify a location or browse to the location where your backup images will be restored. You can click the green arrow icon button to verify the connection to the specified location. If necessary, you may need to enter the User Name and Password credentials to gain access to that location. 7. Select what CA ARCserve D2D will do to resolve any conflicts that are encountered during the restore process. The available options are to whether or not to overwrite the existing files and whether or not to replace any active files. Overwrite existing files Overwrites (replaces) any existing files that are located at the restore destination. All objects are restored from the backup files regardless of their current presence on your machine. Replace active files Rename files Replaces any active files upon reboot. If during the restore attempt CA ARCserve D2D discovers that the existing file is currently in use or being accessed, it will not immediately replace that file, but instead to avoid any problems will delay the replacement of the active files until the next time the machine is rebooted. (The restore occurs immediately, but the replacement of any active files is done during the next reboot). Note: If this option is not selected any active file is skipped from the restore. Creates a new file if the file name already exists. Selecting this option copies the source file to the destination with the same filename but a different extension. Data is then restored to the new file. Skip existing files Skips over and not overwrite (replace) any existing files that are located at the restore destination. Only objects that are not currently existing on your machine are restored from the backup files. By default, this option is selected. Chapter 5: CA Recovery Point Server Use Cases 41

42 8. Select what CA ARCserve D2D will or will not do with the directory structure during the restore process. Create root directory If selected, specifies that if a root directory structure exists in the captured backup image, CA ARCserve D2D recreates that same root directory structure on the restore destination path. When the Create Root Directory option is not selected (unchecked), the file/folder to be restored is restored directly to the destination folder. For example, if during the backup you captured the files "C:\Folder1\SubFolder2\A.txt" and "C:\Folder1\SubFolder2\B.txt" and during the restore you specified to the restore destination as "D:\Restore". If you select to restore the "A.txt" and "B.txt" files individually, the destination for the restored files will be "D:\Restore\A.txt" and "D:\Restore\B.txt" (the root directory above the specified file level will not be recreated). If you select to restore from the "SubFolder2" level, the destination for the restored files will be "D:\Restore\SubFolder2\A.txt" and "D:\Restore\SubFolder2\B.txt" (the root directory above the specified folder level will not be recreated). When the Create Root Directory option is selected (checked), the entire root directory path for the files/folders (including the volume name) is recreated to the destination folder. If the files/folders to be restored are from the same volume name, then the destination root directory path does not include that volume name. However, if the files/folders to be restored are from different volume names, then the destination root directory path does include the volume name. For example, if during the backup you captured the files "C:\Folder1\SubFolder2\A.txt", "C:\Folder1\SubFolder2\B.txt", and also E:\Folder3\SubFolder4\C.txt" and during the restore you specified to the restore destination as "D:\Restore". If you select to restore just the "A.txt" file, the destination for the restored file will be "D:\Restore\ Folder1\SubFolder2\A.txt" (the entire root directory without the volume name will be recreated). If you select to restore both the "A.txt" and "C.txt" files, the destination for the restored files will be "D:\Restore\C\Folder1\SubFolder2\A.txt" and "D:\Restore\E\Folder3\SubFolder4\C.txt" (the entire root directory with the volume name will be recreated) 42 User Guide

43 9. If the recovery point data you are trying to restore is encrypted, you may need to provide the encryption password. A password is not required if you are attempting to restore to the same machine from where the encrypted backup was performed. However, if you are attempting to restore to a different machine, a password is required. Note: A clock icon with a lock symbol indicates the recovery point contains encrypted information and may require a password for restore. 10. When the restore options are selected, click Next. The Restore Summary dialog is displayed. 11. Review the displayed information to verify that all the restore options and settings are correct. If the summary information is not correct, click Previous and go back to the applicable dialog to change the incorrect setting. If the summary information is correct, click Finish to launch the restore process. Chapter 5: CA Recovery Point Server Use Cases 43

44 Restore by Find File/Folder Each time CA ARCserve D2D performs a successful backup, all backed up files/folders are included in the snapshot image of your backup. This restore method allows you to specify exactly which file/folder you want to restore. CA Support: YouTube: How to: Restore Files and Folders How to: Restore Files and Folders Restore by finding a file or folder 1. From the CA ARCserve D2D home page (or CA ARCserve D2D Monitor), select Restore. The restore methods selection dialog opens. 2. Click the Find Files/Folders to Restore option. The Find Files/Folders to Restore dialog opens. 44 User Guide

45 3. Specify where to search (Backup Location and/or File Copy Location) for the file/folder to be restored. If you select Backup Location, you can either specify a location or browse to the location where your backup images are stored. You can click green arrow validate icon to verify proper access to the source location. If you select File Copy Location, you can change the search location to the destination where your file copy images are stored. If you click Change button, the Destination dialog opens and you can select Local or network drive or Cloud. If you select Local or network drive, you can either specify a location or browse to the location where your file copy images are stored. You can click green arrow validate icon to verify proper access to the source location. If you select Cloud, you can either specify a cloud location or click the Configure button to display the Cloud Configuration dialog. For more information, see Specify Cloud Configuration for Restore. Note: If necessary, you may need to enter the User name and Password credentials to gain access to the selected location. 4. Regardless of whether you selected to restore from Local or network drive or from Cloud, when you change the destination to an alternate location a pop-up dialog will appear, asking you if you want to perform a new catalog synchronization or read from the existing catalog. Chapter 5: CA Recovery Point Server Use Cases 45

46 If it is the first time you are performing a catalog synchronization, the "Browse Existing" button will be disabled because there is no existing file copy catalog locally. If a catalog synchronization has been previously performed, this dialog will display details about the last time the catalog was synchronized from this destination. If there were more file copy jobs run since that displayed time, your catalog may not be currently synchronized and you can select the "Sync" option to ensure your file copy catalog is up-to-date. a. If you click the "Sync" button, the file copy catalog will be downloaded from the specified file copy destination to your local machine to allow for faster browsing. b. If you click the "Browse Existing" button, you will use the file copy catalog that is available locally and will not download/sync it again. 5. Specify what to search for (file or folder name to restore). Note: The File Name field supports full name searching and wildcard searching. If you do not know the complete file name, you can simplify the results of the search by specifying the wildcard characters "*" and "?" in the File Name field. The wildcard characters supported for the file or folder name are as follows: "*" - Use the asterisk to substitute zero or more characters in a file or folder name. "?" - Use the question mark to substitute a single character in a file or folder name. For example, if you specify *.txt, all files with a.txt file extension appear in the search results. 6. If necessary, you can also specify a path to further filter your search and select whether to include or not include any subdirectories. 7. Click Find to launch the search. The results of the search are displayed. If searched file has multiple file copy versions, all versions will be listed, sorted by date (with the most recent listed first). It also indicates if the searched file backed up or file copied. 46 User Guide

47 8. Select the version (occurrence) of the file/folder that you want to restore and click Next. The Restore Options dialog opens. 9. Select the destination for the restore. The available options are to restore to the original location of the backup or restore to a different location. Restore to Original Location Restores to the original location from where the backup image was captured. Restore to: You can either specify a location or browse to the location where your backup images will be restored. You can click the green arrow icon button to verify the connection to the specified location. If necessary, you may need to enter the User Name and Password credentials to gain access to that location. Chapter 5: CA Recovery Point Server Use Cases 47

48 10. Select what CA ARCserve D2D will do to resolve any conflicts that are encountered during the restore process. The available options are to whether or not to overwrite the existing files and whether or not to replace any active files. Overwrite existing files Overwrites (replaces) any existing files that are located at the restore destination. All objects are restored from the backup files regardless of their current presence on your machine. Replace active files Rename files Replaces any active files upon reboot. If during the restore attempt CA ARCserve D2D discovers that the existing file is currently in use or being accessed, it will not immediately replace that file, but instead to avoid any problems will delay the replacement of the active files until the next time the machine is rebooted. (The restore occurs immediately, but the replacement of any active files is done during the next reboot). Note: If this option is not selected any active file is skipped from the restore. Creates a new file if the file name already exists. Selecting this option copies the source file to the destination with the same filename but a different extension. Data is then restored to the new file. Skip existing files Skips over and not overwrite (replace) any existing files that are located at the restore destination. Only objects that are not currently existing on your machine are restored from the backup files. By default, this option is selected. 11. Select what CA ARCserve D2D will or will not do with the directory structure during the restore process. Create root directory If selected, specifies that if a root directory structure exists in the captured backup image, CA ARCserve D2D recreates that same root directory structure on the restore destination path. 48 User Guide

49 When the Create Root Directory option is not selected (unchecked), the file/folder to be restored is restored directly to the destination folder. For example, if during the backup you captured the files "C:\Folder1\SubFolder2\A.txt" and "C:\Folder1\SubFolder2\B.txt" and during the restore you specified to the restore destination as "D:\Restore". If you select to restore the "A.txt" and "B.txt" files individually, the destination for the restored files will be "D:\Restore\A.txt" and "D:\Restore\B.txt" (the root directory above the specified file level will not be recreated). If you select to restore from the "SubFolder2" level, the destination for the restored files will be "D:\Restore\SubFolder2\A.txt" and "D:\Restore\SubFolder2\B.txt" (the root directory above the specified folder level will not be recreated). When the Create Root Directory option is selected (checked), the entire root directory path for the files/folders (including the volume name) is recreated to the destination folder. If the files/folders to be restored are from the same volume name, then the destination root directory path does not include that volume name. However, if the files/folders to be restored are from different volume names, then the destination root directory path does include the volume name. For example, if during the backup you captured the files "C:\Folder1\SubFolder2\A.txt", "C:\Folder1\SubFolder2\B.txt", and also E:\Folder3\SubFolder4\C.txt" and during the restore you specified to the restore destination as "D:\Restore". If you select to restore just the "A.txt" file, the destination for the restored file will be "D:\Restore\ Folder1\SubFolder2\A.txt" (the entire root directory without the volume name will be recreated). If you select to restore both the "A.txt" and "C.txt" files, the destination for the restored files will be "D:\Restore\C\Folder1\SubFolder2\A.txt" and "D:\Restore\E\Folder3\SubFolder4\C.txt" (the entire root directory with the volume name will be recreated) 12. The encryption password for file copy destination is loaded automatically. If you select an alternate destination to restore, you need to enter the password manually. Chapter 5: CA Recovery Point Server Use Cases 49

50 13. When the restore options are selected, click Next. The Restore Summary dialog is displayed. 14. Review the displayed information to verify that all the restore options and settings are correct. If the summary information is not correct, click Previous and go back to the applicable dialog to change the incorrect setting. If the summary information is correct, click Finish to launch the restore process. Restore Exchange Mail Each time CA ARCserve D2D performs a successful backup, a point-in-time snapshot image of your backup is also created. This collection of recovery points allows you to locate and specify exactly which backup image you want to restore. For Exchange you can then browse these recovery points to locate the individual objects (mailboxes, mailbox folders, or mail) that you want to restore. To perform an Exchange Granular Restore, the account must have the required permissions. For more information, see Exchange Account Required Permissions (see page 60). 50 User Guide

51 Note: On Microsoft Exchange 2007 and later, Microsoft Exchange Server MAPI Client and Collaboration Data Objects (and later) are not provided as part of the base product installation. Messaging API (MAPI) is a prerequisite for Exchange Granular Restore. If MAPI is not installed on your Exchange server, mailbox or mail level granular restores may fail. To remedy any potential problem, Microsoft provides a download package that contains Microsoft Exchange MAPI and the latest version of Collaboration Data Objects (CDO). To download and install the latest version of this package, see the Microsoft Download Center. CA Support: YouTube: How to: Restore Exchange Mail How to: Restore Exchange Mail Chapter 5: CA Recovery Point Server Use Cases 51

52 Restore Exchange Mail 1. From the CA ARCserve D2D home page (or CA ARCserve D2D Monitor), select Restore. The restore methods selection dialog opens. 2. Click the Restore Exchange Mails option. The Restore Exchange Mails dialog opens. 3. Specify the backup location. You can either specify a location or browse to the location where your backup images are stored. If necessary, enter the User name and Password credentials to gain access to that location. You can click green arrow validate icon to verify proper access to the source location. The calendar view will highlight (in green) all dates during the displayed time period that contain recovery points for that backup source. 4. Select the calendar date for the backup image you want to restore. The corresponding Exchange mailbox databases for that date are displayed, along with the time of the backup, the type of backup that was performed, and the name of the backup. 52 User Guide

53 5. Select a Exchange mailbox database that you want to restore and click Next. Note: If you did not enable the Exchange Granular Restore option during backup (no catalog generated), a notification message will be displayed asking you if you want to generate an Exchange Granular Restore catalog at this time. If you select No for generating a catalog now, you will not be able to browse to or select a granular recovery point. As a result you will only be able to perform full database restore from the Browse Recovery Points Restore dialog. The Restore Exchange Mails dialog is updated to display a listing of the mailbox content for the selected database. Note: Exchange Granular Restore supports restores only. Calendar, Contacts, Notes and Tasks restores are not supported. Chapter 5: CA Recovery Point Server Use Cases 53

54 6. Select the level of Exchange object(s) to be restored (mailbox, folder, or individual mail). You can select the entire content or partial content of the Exchange object to restore. You can select multiple Exchange objects to restore. Note: CA ARCserve D2D does not support granular recovery of Exchange public folder objects. You need to use Application Restore to recover the entire public folder database and then extract the specific Exchange object you need. Note: When using CA ARCserve D2D to restore individual mailbox/mail objects from the Exchange mailbox database, the operating system used for the restore must be same as used when it was backed up (including the same Windows Version number and Service Pack level and also the related version of the visual C++ redistributable package required to support it). Note: During browse and restore of s from the CA ARCserve D2D UI, the "From" field property of the message may not display in the UI for mailboxes which have never logged in to the exchange server. However, if this occurs the s will still be correctly restored. a. You can select a mailbox database. If you select a mailbox database, all of the mailboxes in that database will be restored. b. You can select the mailbox (or mailboxes) to be restored. If you select a mailbox level, all corresponding content (folders and individual mail) within that mailbox will be restored. c. You can select a folder(s) within a selected mailbox to be restored. If you select the mailbox folder level, all corresponding mail content within that folder will be restored. d. You can select the individual mail(s) to be restored. If you select the individual mail level, only the selected mail object(s) will be restored. Note: For Exchange 2003 only, if the individual mail to be restored was sent using any client other than Outlook and the mail had some type of flag status marker attached to it when it was backed up, the mail itself will be restored, but the attached marker will not be included with the restored mail. 54 User Guide

55 7. When the Exchange objects to be restored are specified, click Next. Chapter 5: CA Recovery Point Server Use Cases 55

56 8. Select the destination for the restore. The available options are to restore to the original location of the backup or restore to a different location. Note: For Exchange 2010, archived mailbox items cannot be restored to the original location. Archived mailbox items can only be restored to an alternate location or to a local disk. In addition, regular mailbox items cannot be restored to archive mailboxes. Restore to Original Location Restores the mails to the original location from where the backup image was captured. Mails will retain the same hierarchy and be restored to its original mailbox and original folder. If current machine is not the active Exchange server, CA ARCserve D2D will detect the location of the active server and then restore the mails to that active server. If mailbox has been moved to another Exchange server, but still in the same organization, CA ARCserve D2D will detect the new Exchange server where the original mailbox resides, and then restore to that new server. If the display name of the mailbox was changed, any attempt to restore the mailbox (from an earlier backup session) to its original location will fail because CA ARCserve D2D will not be able to find the changed name. To solve this problem, you can specify to restore this mailbox to an alternate location. Note: When restoring a mailbox or mail to the original location, make sure the destination mailbox is available, or else the restore will fail. CA ARCserve D2D only validates the destination when the restore job is submitted. 56 User Guide

57 Dump File Only Restores the mails to a disk. This disk location can be local or a remote machine.the restored mails will maintain the same hierarchy as they had in the corresponding Exchange Mailbox. The file name will become the subject of mail. Note: If the mail subject, folder name, or mailbox name includes any of the following characters, the character will be replaced by hyphen (-) in file name: \ / : *? " < > For this option, you also need to specify what you want CA ARCserve D2D to do to resolve a conflict situation. In Exchange, you can have multiple mail objects with the same name under the same folder. However in a File System, two files with the same name cannot co-exist under the same folder. There are two options to resolve this conflict situation: Rename - If on the disk, there is a file with the same name as the mail subject, CA ARCserve D2D will still name the mail subject, but will append a number at the end of the mail subject. Overwrite - If on the disk, there is a file with the same name as the mail subject, CA ARCserve D2D will overwrite that file. Note: When you select individual mail objects to restore to the disk (dump), by default the format of the restored mail object will be an Outlook Message (.MSG) file and not a Personal Storage Table (.PST) file. Chapter 5: CA Recovery Point Server Use Cases 57

58 Restore to Alternate Location: Restores the mails to a specified location or lets you browse to the location where your backup images will be restored. The destination must be a mailbox in the same Exchange organization, and a new folder name is required. (If you are attempting to restore mails to an alternate location, the destination cannot be a public folder). Note: When restoring mail to an alternate location, if the specified destination folder already exists, the restore will continue. However, if the specified folder does not exist, then CA ARCserve D2D will create the folder first and then continue the restore. After inputting the User Name and Password, you can click the Browse button to navigate through a list of all Exchange Servers, Storage Groups, Exchange Databases, and Mailboxes in the current organization. Select any mailbox as the destination. 58 User Guide

59 9. When the restore options are selected, click Next. The Restore Summary dialog is displayed. 10. Review the displayed information to verify that all the restore options and settings are correct. If the summary information is not correct, click Previous and go back to the applicable dialog to change the incorrect setting. If the summary information is correct, click Finish to launch the restore process. Note: When the Catalog and Restore Job for Exchange Granular Restore is in progress, the backup session will be in a mounted state. Do not perform any operation (format, change drive letter, delete partition, etc.) on this mounted volume. Chapter 5: CA Recovery Point Server Use Cases 59

60 Exchange Account Restore Permissions To perform an Exchange Granular Restore, the following permissions are required for the account: The account must be a domain account. The account must be a member of the Administrator group. The account must be a member of the Backup Operators group. There must be a mailbox associated with the account and the mailbox must be initialized. For Exchange Server 2003, 2007, and Exchange 2010 this mailbox must be in same Organization (Exchange Organization) of the Exchange server to which you plan to restore to (restore destination). The name of the mailbox must be unique. A unique name is a name that does not exist in the organization as a subset of characters in another mailbox name. For example, if there is a mailbox named Administrator in your organization, you cannot use the name Admin. The account user must have the proper role assignments: For Exchange Server 2003 systems, the User Name must be a domain account with Exchange full administrator role. For Exchange Server 2007 systems, the User Name must be a domain account with either the Exchange Organization administrator role or the Exchange server administrator role. For Exchange Server 2010 systems, the User Name must be a domain account with Exchange Organization management role. Application Restore CA ARCserve D2D allows you to not only protect and recover your data, but also helps you to get the applications that will use that data back up and running. All application recoveries can only be made using the Restore by Recovery Point method. During an application recovery, CA ARCserve D2D takes advantage of Windows Volume Shadow Copy Service (VSS) to help ensure data consistency for any VSS-aware application. With CA ARCserve D2D, you can recover the following applications without performing a full disaster recovery: Microsoft Exchange Server Microsoft SQL Server 60 User Guide

61 Application Restore - MS Exchange Server CA ARCserve D2D allows you to not only protect and recover your data, but also helps you to get the Microsoft Exchange Server application that uses that data back up and running. The Microsoft Exchange Server recovery can only be made using the Restore by Recovery Point method. CA ARCserve D2D supports the following versions of Microsoft Exchange Server: Exchange Single Server Environment. Exchange Single Server Environment, Local Continuous Replication (LCR), and Cluster Continuous Replication (CCR) environment. For Exchange 2007 CCR environment, CA ARCserve D2D must be installed on both the active node and passive node of Microsoft Cluster. Backup can be performed from an active node and passive node, but restore can only be performed to an active node. Exchange Single Server Environment and Database Availability Group (DAG) environment. For Exchange 2010 DAG environment, CA ARCserve D2D must be installed on all member servers in the DAG group. A backup job can also be performed from any member server for both active and passive database copies, but restore can only be performed to an active database copy. Note: Microsoft Exchange Server 2003 Cluster Environment and Microsoft Exchange Server 2007 Single Copy Cluster (SCC) environment are not supported by CA ARCserve D2D. Microsoft Exchange Server can be restored at the following levels: Microsoft Exchange Writer Level If you want to restore all the Microsoft Exchange Server data, you can perform a restore at Microsoft Exchange Writer level. Storage Group Level If you want to restore a specific Storage Group, you can perform a restore at the Microsoft Exchange Storage Group level. (Does not apply for Microsoft Exchange Server 2010). Mailbox Store Level (Exchange 2003) If you want to restore a specific Mailbox Store, you can perform a restore at the Mailbox Store level. Mailbox Database Level (Exchange 2007 and 2010) If you want to restore a specific Mailbox Database, you can perform a restore at the Mailbox Database level. Chapter 5: CA Recovery Point Server Use Cases 61

62 Restore Microsoft Exchange Server Application Note: When performing a Microsoft Exchange Server database restore (to either the original location or a recovery storage group/recovery database), you must verify that the account also has the following administrative privileges: Exchange Exchange Full Administrator Role Exchange 2007/ Exchange Organization Administrator or Exchange Server Administrator Role 1. From the CA ARCserve D2D home page (or CA ARCserve D2D Monitor), select Restore. The restore methods selection dialog opens. 2. Click the Browse Recovery Points option. The Browse Recovery Points dialog opens. 62 User Guide

63 3. Specify Recovery Point Server as the Location Type. 4. Select the recovery point (date and time) and then select the Microsoft Exchange database to be restored. The corresponding marker box becomes filled (green) to indicate that the database has been selected for the restore. Note: If you do not want the transaction log files to be applied after the restore, you must manually delete it before the restore is performed. For more information about manually deleting transaction log files, refer to the Microsoft Exchange Server documentation. Chapter 5: CA Recovery Point Server Use Cases 63

64 5. Click Next. The Restore Options dialog opens. 6. Select the destination for the restore. The available options are to restore to the original location of the backup, restore the dump file only, or restore to a Recovery Storage Group/Recovery Mailbox Database. Restore to original location Restores to the original location from where the backup image was captured. Dump file only Restores the dump files only. For this option, CA ARCserve D2D will restore the Microsoft Exchange database file to a specified folder, and will not bring it online after recovery. You can then move this file to a different server and mount it to exchange server manually to view data contained in it. Note: When a Recovery Mailbox Database exists, restore with Dump file only option will fail. 64 User Guide

65 Replay log on database Specifies that when the database files are dumped to the destination folder, you can replay and apply all Microsoft Exchange transaction log files and commit them to the database file. When the database next starts, and transaction log files that were not yet written to the database files are then applied before the database is again made available to you. Note: This option is not applicable for Microsoft Exchange Server 2003 Restore to Recovery Storage Group (Exchange 2007) Restores the database to a Recovery Storage Group (RSG). An RSG is a storage group that can be used for recovery purposes. You can restore a Microsoft Exchange Mailbox Database from a backup in a Recovery Storage Group and then recover and extract data from it, without affecting the production database that is being accessed by end users. If single storage group or database (except a public folder database) from the same storage group are selected to restore, the default restore destination is "Restore to Recovery Storage Group" (or "Restore to Recovery Database"). If multiple storage groups or databases from multiple storage groups are selected to restore, Exchange can only be restored to the original location or restore with "Dump file only" option. The default restore destination is "Restore to original location". Before restoring an Exchange 2007 database to a Recovery Storage Group, you must create a Recovery Storage Group and Mailbox Database with the same name. For example, if you want to restore MailboxDatabase1 from the First Storage Group to a Recovery Storage Group, you must create a Recovery Storage Group and add the database "MailboxDatabase1" to the Recovery Storage Group. Note: This option is not applicable for Microsoft Exchange Server 2003 Dismount the database before restore and mount the database after restore Typically before a restore, Microsoft Exchange will perform some checks to help ensure the following: The database to be restored is in "Dismounted" status. The database is not restored unexpectedly. To protect a Microsoft Exchange production database from being restored unexpectedly, a switch is added to allow the database to be overwritten during the restore process. Microsoft Exchange will refuse to restore a database if this switch is not set. Chapter 5: CA Recovery Point Server Use Cases 65

66 For CA ARCserve D2D, these two options are controlled by this "Dismount the database before restore and mount the database after restore" option. With this option, CA ARCserve D2D lets you launch the restore process automatically without any manual operations. (You can also specify to dismount/mount database manually). If checked, specifies that the recovery process will automatically dismount the Exchange database before the restore process and then mount the database after the restore process is completed. In addition, if checked, this option will also allow the Exchange database to be overwritten during the restore. If unchecked, specifies that the recovery process will not automatically dismount the Exchange database before recovery and mount the database after recovery. The Exchange administrator would have to perform some manual operations such as dismount the Exchange database, set the Allow Overwrite flag on the database, and mount the Exchange database. (The recovery procedure is performed by Exchange during the mounting of the database). In addition, if unchecked, this option does not allow the Exchange database to be overwritten during restore. Restore to Recovery Database (Exchange 2010) Restores the database to a Recovery Database. A Recovery Database is a database that can be used for recovery purposes. You can restore a Microsoft Exchange Mailbox Database from a backup to a Recovery Database and then recover and extract data from it, without affecting the production database that is being accessed by end users. Before restoring an Exchange 2010 database to a Recovery Database, you must first create a Recovery Database. Note: This option is not applicable for Microsoft Exchange Server 2003 and User Guide

67 7. Click Next. The Restore Summary dialog opens. Application Restore - MS SQL Server 8. Review the displayed information to verify that all the restore options and settings are correct. If the summary information is not correct, click Previous and go back to the applicable dialog to change the incorrect setting. If the summary information is correct, click Finish to launch the restore process. CA ARCserve D2D allows you to not only protect and recover your data, but also helps you to get the Microsoft SQL Server application that uses that data back up and running. The Microsoft SQL Server recovery can only be made using the Restore by Recovery Point method. Chapter 5: CA Recovery Point Server Use Cases 67

68 Restore Microsoft SQL Server Application 1. From the CA ARCserve D2D home page (or CA ARCserve D2D Monitor), select Restore. The restore methods selection dialog opens. 2. Click the Browse Recovery Points option. The Browse Recovery Points dialog opens. 3. Click Recovery Point Server as the Backup Location. 4. Select the recovery point (date and time) and then select the Microsoft SQL Server database to be restored. The corresponding marker box becomes filled (green) to indicate that the database has been selected for the restore. You can select a single or multiple databases to be restored. 68 User Guide

69 5. Click Next. The Restore Options dialog opens. 6. Select the destination for the restore. The available options are to restore to the original location of the backup, restore the dump file only, or restore to an alternate location. Restore to original location Restores to the original location from where the backup image was captured. Chapter 5: CA Recovery Point Server Use Cases 69

70 Dump file only Restores the dump files only. Dump files are created when an application crashes and contains additional (time-stamped) information that can be used to troubleshoot the cause of the problem. When you select this option, you can then specify or browse to the folder location where the dump file will be restored to. Restore to alternate location Restores to an alternate location (not the original location). 70 User Guide

71 Because backups can be copied to network locations, they can be used by multiple SQL Server instances. Multiple database restore can be performed (simultaneously) from the instance level. From this listing, you can select the database instance and specify a new database name and alternate location to restore the database to. In addition, you can also browse to the alternate location where the database will be restored to. When restoring a Microsoft SQL Server application to an alternate location, there are some considerations that you should be aware of. For more information, see MS SQL Server Restore to Alternate Location Considerations. 7. Click Next. The Restore Summary dialog opens. 8. Review the displayed information to verify that all the restore options and settings are correct. If the summary information is not correct, click Previous and go back to the applicable dialog to change the incorrect setting. If the summary information is correct, click Finish to launch the restore process. Chapter 5: CA Recovery Point Server Use Cases 71

72 MS SQL Server Restore to Alternate Location Considerations When you specify to restore a Microsoft SQL Server application to an alternate location, you can either restore it to an alternate location on the same machine or on a different machine. Prior to performing a CA ARCserve D2D restore of a Microsoft SQL Server application to an alternate location, you should consider the following: If alternate location is on the same machine For this option, you can either restore a database to a new location (with the same name) or restore with a new name (to the same location): Same Name - New Location For example, if Database A is installed in the current SQL Server at "C:\DB_A" and has been backed up. You can use this option and specify "Alternate File Location" to restore Database A to an alternate location such as "D:\Alternate_A. After the database has been restored, the database file located at the new location "D:\Alternate_A" will then be used. Same Location - New Name For example, if you have two databases (Database A and Database B) installed in the current SQL Server and both have been backed up. You can use this option and specify "New database Name" to restore Database A to same location as Database A_New. After the databases have been restored, this location will now have three databases (Database A, Database B, and Database A_New). If alternate location is on the different machine The SQL Server installation path must be the same as the path that existed when the backup was performed. For example, if the backup of the SQL Server is installed at "C:\SQLServer", then the SQL Server on the new CA ARCserve D2D server must also be installed at C:\SQLServer. The same instance name for the database that existed when the backup was performed must be installed on CA ARCserve D2D server, otherwise the database associated with that instance will be skipped from the restore. For example, if the backup of the SQL Server contained "Instance_1" with Database A and Database B and "Instance_2" with Database C, but the CA ARCserve D2D server only has "Instance_1". After the restore is complete, Database A and Database B will be restored, but Database C will not be restored. The SQL Server version on the CA ARCserve D2D server must be backwards compatible to the version of the SQL Server used during the backup session. For example, you can restore a SQL Server 2005 machine to a SQL Server 2008 machine; however, you cannot restore a SQL Server 2008 machine to a SQL Server 2005 machine. 72 User Guide

73 Restoring a database of 64-bit instance to 32-bit instance is not supported. Restore from Windows Explorer Using ARCserve D2D View You can use the ARCserve D2D View from Windows Explorer as an alternate method to restore objects that were backed up. The ARCserve D2D View lets you perform such functions as recover, copy, and paste to quickly and easily restore objects. From the ARCserve D2D View, you can perform two types of restore: Restore a file/folder (see page 73) Restore mail objects from Exchange (see page 76) Restore a File/Folder Using ARCserve D2D View For a file/folder restore, you can use the copy and paste function to restore backed up objects (files or folders) from the backup destination to your specific restore destination. (The drag-and-drop method is not supported for a file/folder restore from the ARCserve D2D View). CA Support: YouTube: How to: Restore a File/Folder Using ARCserve D2D View How to: Restore a File/Folder Using ARCserve D2D View Chapter 5: CA Recovery Point Server Use Cases 73

74 Restore a File/Folder Using ARCserve D2D View 1. Access Windows Explorer and from the folders in the left pane, navigate to and select the backup destination. 2. From the right pane, right-click on the backup destination. A pop-up menu is displayed listing the available options. 3. Select the "Change to ARCserve D2D View" option. The Windows Explorer View changes to the ARCserve D2D View. When you enter into that directory, all views are logic views from a CA ARCserve D2D user perspective and displays the recovery points stored at that location. 74 User Guide

75 Note: When using the ARCserve D2D View. if you attempt to browse to or locate a recovery point and all recovery points are not displayed, it may be because your backup destinations were split between your local machine and a remote share machine. For the ARCserve D2D View to display all recovery points, the backup locations (for full and corresponding incremental backups) should all be at the same location (either local or remote). If this occurs, it is a limitation only when using the ARCserve D2D View. To remedy this problem, you can use the CA ARCserve D2D restore UI instead to properly display all recovery points, regardless of being at the same or different locations. 4. Select the recovery point that you want to restore from and expand that directory until you can gain access to the file or folder that you want to restore. Note: From the ARCserve D2D View, the Copy option is only available for file and folder level objects. You cannot use this option to copy volume or machine level objects. Chapter 5: CA Recovery Point Server Use Cases 75

76 5. Right-click on the file or folder to be restored and select Copy. Navigate to the restore location, right-click on the location, and select Paste. Note: Manual operations (such as copy, cut, or paste) for the backup destination folder will not be successful if a job is active or a user is browsing recovery points using the ARCserve D2D View. Note: When restoring backed-up files (with long file names) from the ARCserve D2D View using the copy-and-paste method, the job may fail without any corresponding error or warning. (Windows Explorer has a limitation on the maximum file path length, which may lead to a file copy failure). If this occurs, you can use the installed CA ARCserve D2D UI to perform the restore. 6. When the restore is successfully completed, right-click on the backup destination and select the "Change to Windows Normal View" option. The ARCserve D2D View changes back to the Windows Explorer View. Note: During the time that you are in the ARCserve D2D View mode, the merge/purge process for retaining the maximum number of recovery points will be disabled. As a result, CA ARCserve D2D will continue to save recovery points beyond the specified number of recovery points until you exit the ARCserve D2D View and return to the Windows Normal View. When you exit the ARCserve D2D View, all retained recovery points beyond the specified number will then be merged/purged. Restore an Exchange Object Using ARCserve D2D View For an Exchange object restore, you can use the recovery function or the copy and paste (or drag-and-drop) functions to restore backed up Exchange (mailboxes, mail folders, mail) from the backup destination to your specific restore destination. Note: If you are using a non-windows shared folder as your backup destination, you will not be able to switch to the ARCserve D2D View for a local or remote Windows machine. CA Support: YouTube: How to: Restore an Exchange Object Using ARCserve D2D View How to: Restore an Exchange Object Using ARCserve D2D View Restore an Exchange object using ARCserve D2D View 1. Access Windows Explorer and navigate to the backup destination. 76 User Guide

77 2. Right-click on the backup destination. A pop-up menu is displayed listing the available options. 3. Select the "Change to ARCserve D2D View" option. The Windows Explorer View changes to the ARCserve D2D View. When you enter into that directory, all views are logic views from a CA ARCserve D2D user perspective and displays the recovery points stored at that location. Chapter 5: CA Recovery Point Server Use Cases 77

78 Note: When using the ARCserve D2D View. if you attempt to browse to or locate a recovery point and all recovery points are not displayed, it may be because your backup destinations were split between your local machine and a remote share machine. For the ARCserve D2D View to display all recovery points, the backup locations (for full and corresponding incremental backups) should all be at the same location (either local or remote). If this occurs, it is a limitation only when using the ARCserve D2D View. To remedy this problem, you can use the CA ARCserve D2D restore UI instead to properly display all recovery points, regardless of being at the same or different locations. 4. Select the recovery point that you want to restore from and expand that directory until you can gain access to the Exchange object that you want to restore. 5. From the ARCserve D2D View, the Recovery and Copy options are only available for mailbox, folder, and individual mail objects. You cannot use these options to restore an entire Exchange mailbox database. Note: If the Exchange mailboxes are not displayed when you are trying to browse the mailbox database in a recovery point, the Exchange Granular Restore may not have been enabled during backups and the corresponding catalog was not generated. Prior to performing the restore, you can generate the catalog manually from the Restore Exchange Mails dialog. For more information, see Generate an Exchange Granular Restore Catalog before Restore. 78 User Guide

79 6. Right-click on the file or folder to be restored and select Recovery or Copy. a. If you select Copy, you can then navigate to the restore location, right-click on the location, and select Paste. (You can also use the drag and drop method to copy an Exchange object to a restore destination). Note: If you are attempting to use the drag-and-drop function to restore items (mail objects) from a remote destination and this function does not work, verify that the remote folder URL is included to the "Trusted Sites' in Internet Explorer. b. If you select Recovery, the Restore Options dialog opens. Select the destination for the restore. Chapter 5: CA Recovery Point Server Use Cases 79