Backup Manager Configuration And Deployment Guide - N-able

Transcript

Backup Manager Configuration and Deployment Guide Version 9.1 N-central 9.1 Backup Manager Configuration and Deployment Guide Contents Backup Manager 3 Backup Manager Support 9 Backup Manager Configuration and Deployment Defining a Backup Manager Profile 14 14 Configuring Backup Shares and Device Credentials 16 Deploying Backup Manager 17 Review the Installation Status of Backup Manager 18 Scheduling Device Reboots 19 Additional Backup Manager Tasks 20 Restoring Data 21 Outcome 23 Backup Manager Status 23 -2 - N-central 9.1 Backup Manager Configuration and Deployment Guide Backup Manager Backing up data is a vital function for any information technology environment, used to protect against data loss and to provide data retention capabilities. Backup Manager, N-central's integrated backup functionality, provides a local solution that is cost-effective, simple to both deploy and manage, and allows you to provide effective coverage for your managed devices. Backup Manager is based on CA Technologies' D2D (disk-to-disk) backup software using proven and reliable technology to protect and preserve data. Similar to Patch Management and Endpoint Security, Backup Manager is implemented through Profiles. Configuring and applying Backup Manager Profiles allows you to target specific devices (or groups of devices) on which data backup policies can be applied. Backup Manager Architecture Note: The following information was derived from CA Technologies' technical documentation. For more information, refer to https://support.ca.com/ Backup Manager allows you to perform frequent and periodic block-level backups of your devices. These backups can be stored on: l l an internal drive, an external drive, or -3 - N-central 9.1 Backup Manager Configuration and Deployment Guide l a remote network share. Note: To avoid continuous backup cycles, the drive volume that is being backed up cannot be specified as the backup destination. Backup Manager can perform the following types of backups: l l l Full - complete block-level backup, Incremental - partial backup of only data that has been modified since the last backup, or Verification - re-synchronization of backups to ensure there has been no data loss or damage. The underlying sequential process behind Backup Manager includes: 1. When you initiate a backup (either following a schedule or manually), Backup Manager captures a complete VSS snapshot. 2. It then backs up only data blocks that have been changed from a previous successful backup. 3. During this block-level backup process, Backup Manager captures the data and creates a catalog containing relevant information including: l l l l operating system, installed applications (Microsoft SQL and Microsoft Exchange only), configuration settings, and necessary drivers. This comprehensive process provides you with the capability to restore backed-up data images so you can recover either specific data or an entire drive. Block-Level Incremental Backups During an incremental backup (which can be run either according to a schedule or manually), Backup Manager divides the specified volume into subordinate data blocks that are then backed up. The initial backup is considered the "Parent" and is a complete backup of the source volume used to establish the baseline data blocks that will be monitored. Before performing the backup, a VSS snapshot is created and an internal monitoring driver then checks each data block to detect any changes. As scheduled, Backup Manager then incrementally backs up only those data blocks that have changed since the previous backup. Backup Manager allows you to schedule subsequent block-level incremental backups ("Child" backups) as frequently as every 15 minutes in order to provide up-to-date backup images. When used to restore volume information, Backup Manager locates the most recently backed up version of each data block and then rebuilds the entire volume using the most current blocks. -4 - N-central 9.1 Backup Manager Configuration and Deployment Guide Infinite Incremental Backups A potential issue is that as incremental backups continue (as often as 96 times per day if configured to take place every 15 minutes), these periodic backups will accumulate a large chain of data blocks that need to be monitored every time a new backup is performed. This will require additional space to store the accumulating backup data images. To minimize this potential problem, Backup Manager allows you to define a limit for the number of incremental "Child" backups to be stored. This is done by configuring Recovery Points. When the configured storage limit is reached, Backup Manager will merge the earliest incremental "Child" backup into the "Parent" backup to create a new baseline image consisting of the "Parent plus oldest Child" set of data blocks (unchanged blocks will remain unchanged). This cycle of merging the oldest "Child" backup into the "Parent" backup will repeat for each subsequent backup, allowing you to perform infinite incremental snapshot backups while maintaining the same number of stored (and monitored) backup data images. Verification Backups -5 - N-central 9.1 Backup Manager Configuration and Deployment Guide Backup Manager can perform Verification (or re-synchronization) backups to check the stored backup data image and re-synchronize the data blocks with the source data if necessary. A Verify backup will examine the most recent backup of each individual data block and compare the content and information to the original source data. This comparison verifies that the latest backed up blocks represent the corresponding information at the source. If the backup image for any data block does not match the source data (possibly because of changes in the system since the last backup), Backup Manager will refresh (or re-synchronize) the backup of the data block that does not match. A Verify backup can also be used to provide the same data security as a full backup without taking up the space of a full backup. The advantage of a Verify backup is that it is very small in comparison to a full backup because only the changed data blocks (blocks that do not match the last backup) are backed up. A drawback, however, is that Verify backups are also slower than Incremental backups because Backup Manager has to compare all of source disk blocks with the blocks of the last backup. File Level Data Restore During a block-level backup, each backed up file consists of a collection of data blocks that define that particular file. A catalog file is created containing a list of the backed up files, the individual blocks that were used for each file, and the available recovery points for these files. When you need to restore a particular file, you can search your backup and select the file that you want to restore. You then select the recovery point that you want to use from which data will be restored. Backup Manager collects the version of the blocks that were used for the recovery point of the specified file, and re-assembles and restores the file. -6 - N-central 9.1 Backup Manager Configuration and Deployment Guide Bare Metal Recovery Bare Metal Recovery refers to restoring a computer system from "bare metal" by re-installing the operating system and software applications, and then restoring the data and user settings. The most common reasons for performing a bare metal recovery are because: l l l l a hard drive fails, a hard drive becomes full, you want to upgrade (migrate) to a larger drive, or you want to migrate to newer hardware. Bare metal recovery can be provided by Backup Manager because during the block-level backup process, Backup Manager captures not only data but also all information related to the operating system, installed applications, configuration settings, and necessary drivers. All relevant information that is necessary to completely rebuild the original computer system from "bare metal" is backed up into a series of blocks and stored on the backup location. Note: Dynamic disks will be restored at the disk-level only. If your data is backed up to a volume on a dynamic disk, you will not be able to restore this dynamic disk (including all its volumes) during bare metal recovery. When you perform a bare metal recovery, the Backup Manager Recovery boot disk is used to initialize the new computer system and allow the bare metal recovery process to begin. When the bare metal recovery is started, Backup Manager prompts you to select or provide a valid location from which to retrieve these backed up data blocks as well as the recovery point to be restored. If necessary, you may also be prompted to provide valid drivers for the new computer system. When this connection and configuration information is provided, Backup Manager obtains the specified backup image from the backup location and restores all backed up data blocks to the new computer system (empty blocks will not be restored). After the bare metal recovery image is fully restored to the new computer system, the machine will be back to the state that it was in when the last backup was performed, and Backup Manager backups will be able to continue as scheduled. -7 - N-central 9.1 Backup Manager Configuration and Deployment Guide Note: After completion of bare metal recovery, the first backup will be a Verification Backup. -8 - N-central 9.1 Backup Manager Configuration and Deployment Guide Backup Manager Support Integration with CA ARCserve D2D N-central Backup Manager supports integration with devices that have the following versions of CA ARCserve D2D already installed: CA ARCserve D2D Version N-central Version Already Installed N-central 8.2 to N-central 9.0 Note: R16 After integration with these versions of N-central, the CA ARCserve D2D software will automatically be upgraded to R16 Update 4. R16 Update 1 R16 Update 2 R16 Update 3 R16 Update 4 N-central 9.0 SP1 and later Note: R16 After integration with this version of N-central, the CA ARCserve D2D software will automatically be upgraded to R16 Update 6. R16 Update 1 R16 Update 2 R16 Update 3 R16 Update 4 R16 Update 6 Warning! Backup Manager does not support integration with CA ARCserve D2D R16 Update 5 due to potential issues with password validation. Supported Operating Systems N-central Backup Manager is supported on devices using the following operating systems: -9 - N-central 9.1 Backup Manager Configuration and Deployment Guide Operating System Operating System Variant Microsoft Windows Server 2003 Service Pack 1 or l Service Pack 2 l l l l l Microsoft Windows Server 2003 R2 l l Microsoft Windows XP l l Microsoft Windows Server 2008 Enterprise Edition (32-bit and 64-bit) Standard Edition (32-bit and 64-bit) Web Edition (32-bit and 64-bit) Datacenter (32-bit and 64-bit) Storage Server R2 Windows Small Business Server R2 R2 Enterprise Edition (32-bit and 64-bit) R2 Standard Edition (32-bit and 64-bit) Professional (32-bit and 64-bit) Home Edition (32-bit) l Enterprise (32-bit and 64-bit) Standard (32-bit and 64-bit) Datacenter (32-bit and 64-bit) Web Server (32-bit and 64-bit) Storage Server (32-bit and 64-bit) Core (32-bit and 64-bit) Server Foundation (64-bit) Windows Server 2008 Hyper-V (64-bit) – l physical only Windows Server 2008 R2 Hyper-V (64- l bit) – physical only Windows Small Business Server 2008 l (SBS 2008) Windows Small Business Server 2011 l l l l l l l (SBS 2011) - 10 - N-central 9.1 Backup Manager Configuration and Deployment Guide Operating System Operating System Variant Microsoft Windows Server 2008 R2 l l l l l l l Microsoft Windows Vista l l l l l Microsoft Windows 7 l l l l l l R2 R2 R2 R2 R2 R2 R2 Enterprise (64-bit) Standard (64-bit) Datacenter (64-bit) Web Server (64-bit) Server Foundation (64-bit) Core (64-bit) Storage Server (64-bit) Ultimate (32-bit and 64-bit) Home Basic (32-bit) Home Premium (32-bit and 64-bit) Business (32-bit and 64-bit) Enterprise (32-bit and 64-bit) Ultimate (32-bit and 64-bit) Enterprise (32-bit and 64-bit) Professional (32-bit and 64-bit) Home Premium (32-bit and 64-bit) Home Basic (32-bit) Starter edition (32-bit) Supported Applications for Recovery Backup Manager also supports the following for application recovery: Application Application Variant Microsoft Exchange l Microsoft Exchange Server 2003 Service Pack 1 or Service Pack 2 Stand- l alone Microsoft Exchange Server 2007 Standalone or Cluster Continuous Rep- l lication (CCR) configuration Microsoft Exchange Server 2010 Standalone or Database Availability Group Server (DAG) configuration Microsoft SQL l Server l Microsoft SQL Server 2005 Express, Standard, Workgroup, or Enterprise Microsoft SQL Server 2008 Express, Web, Standard, Workgroup, or Enter- l prise Microsoft SQL Server 2008 R2 Express, Web, Standard, Workgroup, or Enterprise Supported Disk Types Note: The following information is based on CA Technologies' Knowledge Base Article #TEC523227. Backup Manager supports the following types of disks as backup sources, backup destinations, and for use with Bare Metal Recovery. - 11 - N-central 9.1 Backup Manager Configuration and Deployment Guide Bare Metal Recovery SupDisk (Volume) Type As Backup As Backup Source Destination port Data Vol- System and ume boot volume 1 GPT Disk System Reserved Partition (Windows 2008 1 n/a R2 Boot Manager) Mounted Volume (No drive letter/NTFS formatted) RAW Volume (No drive letter/Not formatted) 2 VHD Mounted Volume (Windows 2008 R2) Dynamic 3 No RAID Disk Software RAID-0 RAID (Stripe) RAID-1 (Mirrored) RAID-5 Hardware RAID (Include Embedded RAID) File System Format 4 FAT/FAT32 File System Share Type Windows Shared Volume - 12 - N-central 9.1 Backup Manager Configuration and Deployment Guide Bare Metal Recovery SupDisk (Volume) Type As Backup As Backup Source Destination port Data Vol- System and ume boot volume Linux Shared Volume (samba shared) Is File System Temporary? Removable Disk (for example, Memory Stick, RDX) Notes: 1. Backup Manager only supports BIOS systems as uEFI systems are not supported. 2. The VHD mounted volume used as a backup destination should not reside on a volume that is selected as a backup source. 3. Spanned volume cannot be used as boot volume. 4. FAT/FAT32 file systems cannot hold a single file larger than 4 GB. If the D2D file is larger than 4 GB after compression (because the source is very large), the backup will fail. - 13 - N-central 9.1 Backup Manager Configuration and Deployment Guide Backup Manager Configuration and Deployment The following procedures provide examples of how to configure Backup Manager Profiles and how to deploy Backup Manager through N-central. A Backup Manager Profile must be configured to address the data backup and restoration needs of the customer and as with any backup solution, a re-start of the customer's devices will be required in order to complete the deployment and installation of the Backup Manager. This demonstration procedure describes: l l l l l l Defining a Backup Manager profile Configuring Customer-level Backup Shares and Device Credentials Deploying Backup Manager Scheduling device reboots Additional Backup Manager Tasks Restoring data Note: The following information is current as of October 18, 2012 and applies to N-central 8.2.0.1152 and above. Warning! Before proceeding, verify that your devices meet the "Supported Disk Types" requirement as described under Backup Manager Support on page 9. Defining a Backup Manager Profile 1. Select the Service Organization level from the View Selection Menu in the top left of the main menu bar. 2. Click Configuration > Backup Manager > Profiles. 3. Click Clone beside Daily Incremental Backup/Weekly Verify Backup. 4. Type a Name for the Backup Manager Profile. Example: Entire Machine Backup - 365 Incrementals (Export every 31st Recovery Point) 5. Click Save. 6. Click the newly created Backup Manager profile. 7. In Backup Settings > Setting Module, click Edit Settings. 8. In Destination Settings > Backup Destination, verify that Use default Backup Share for the Customer is selected. - 14 - N-central 9.1 Backup Manager Configuration and Deployment Guide Note: Default Backup Shares are configured at the Customer-level within N-central to reflect customer specific network paths and share credentials. Customer Backup Share's will be configured later in this procedure. 9. In Destination Settings > Backup Type after Destination Change, verify that Full Backup is selected. 10. In Administrator Account > Credentials, verify that Use device credentials is selected. Note: Device credentials are specified on the Properties tab of each device within N-central. Configuring default device credentials for all Windows Devices within a customer will be described later in this procedure. 11. In Source Settings > Backup Source, verify that Backup the Entire Machine is selected. 12. In Backup Settings type 365 as the Number of Recovery Points to keep. 13. Verify that Standard Compression is selected. Tip: Enabling compression will save disk space although it will also increase the processing and time required to complete the backup and restoration of data. 14. Select No Encryption within the Encryption Algorithm drop-down menu. Warning! Encryption passwords cannot be retrieved! If an Encryption Algorithm is selected, a password must be set and is required to decrypt the data backup. The encryption password cannot be retrieved and if lost, the encrypted backup cannot be restored. 15. Click Save. 16. In Backup Settings >Schedule Module, click Edit Settings. 17. Verify that Enable Full Backup is not selected. Note: Backup Manager will always perform one full backup of the device initially, as a full backup is required before any incremental backups can be performed. The initial full backup will occur at the time of the first scheduled incremental or full backup that is configured within the Backup Manager profile. 18. Verify that Enable Incremental Backup is selected. 19. Select Repeat Every: 1 days. 20. Verify that Enable Verify Backup is selected. 21. Select Repeat Every: 7 days. 22. Click Save. - 15 - N-central 9.1 Backup Manager Configuration and Deployment Guide 23. In Backup Settings > Advanced Settings Module, click Edit Settings. 24. In Exchange and SQL Server Log Truncation, verify that Enable SQL Server Log Truncation is selected. 25. Select Weekly for Truncate SQL Server Log. 26. In Exchange and SQL Server Log Truncation, verify that Enable Exchange Server Log Truncation is selected. 27. Select Weekly for Truncate Exchange Server Log. 28. In Exchange Granular Restore Catalog, verify that Generate Exchange Granular Restore Catalog after each backup is selected. 29. In Throttle Backup Settings, verify that Enable Backup Throttling is not selected. 30. Click Save. 31. In Copy Recovery Points > Recovery Points Copy Settings Module, click Edit Settings. 32. Select Enable Copy Recovery Points. 33. Type the Destination path. Note: The Copy Recovery Points destination must be different than the Backup destination. Copied Recovery Points offer a method of recoverying data in the event the full and/or incrementatl Backups become inaccessible. 34. Select the User Name to be used to authenticate to destination. 35. Select Password. 36. Select 31 in the Copy files after field. 37. Specify 1 for the Number of Copy Recovery Points to keep. 38. Verify that Standard Compressionis selected. 39. Select No Encryption in the Encryption Algorithm drop-down menu. 40. Click Save. Configuring Backup Shares and Device Credentials As Backup Shares and Device Credentials are unique to each customer environment, these configurations will be set at the customer level within N-central. 1. Select the Customer from the View Selection Menu in the top left of the main menu bar. - 16 - N-central 9.1 Backup Manager Configuration and Deployment Guide 2. Click Configuration > Backup Manager > Backup Share. 3. In Default Backup Share, select a Network Share Path that is relevant to the customer network. 4. Type the Network Share Access Username and Network Share Access Password. Note: The network share and credentials configured within the previous step will be leveraged by the Backup Manager profile configured earlier within this procedure. 5. Click Save. Note: If Device Credentials have not been previously configured within N-central, complete steps 7 through 10 below. 6. Click Administration >Defaults > Agent/Probe Credentials. 7. Type the Domain Administrator credentials. 8. Click Propagate . Note: The Propagate setting will verify that the credentials specified are distributed to the Properties tab of each device within the N-central Customer. These credentials will be used during the installation of Backup Manager and must be local or domain administrator credentials. Credentials can be adjusted on the Properties tab of individual devices. 9. Click Save. Deploying Backup Manager 1. Verify that the Customer is selected from the View Selection Menu in the top left of the main menu bar. 2. Click All Devices. 3. Filter the All Devices view if necessary and select the checkbox beside one or more devices on which you want to deploy Backup Manager. 4. Click Edit. 5. In the Backup Management section, Select Enable Backup Management. 6. An N-central Agent is required for Backup Manager. In the Backup Management modal box, select Best Available. 7. Click Save. - 17 - N-central 9.1 Backup Manager Configuration and Deployment Guide 8. If you are deploying Backup Manager to a Windows Server, select the appropriate Backup Manager license type. 9. If you are deploying Backup Manager to a Windows Workstation/Laptop, the Windows Workstation/Laptop Backup Manager license type will be applied automatically (no configuration is required). 10. In the Select Backup Management Configuration Profile, select the Backup Manager Profile configured earlier in this procedure. Tip: As reboots are required to complete the installation of Backup Manager, you may choose Restart if Necessary under the Monitoring Options section. This configuration will allow N-central to restart the remote device (or devices) when necessary to complete the installation of the Backup Manager. Alternatively, do not select Restart if Necessary under the Monitoring Options section and schedule the device to be restarted at another time. Scheduling a device restart is covered later in this procedure. 11. Click OK. Review the Installation Status of Backup Manager To retrieve a listing of all devices that have Backup Manager installed, a filter should be created at the SO level within N-central. 1. Select the SO Customer from the View Selection Menu in the top left of the main menu bar. 2. In the left navigation pane, click Configuration > Filters. 3. Click Add. 4. In the Create New Filter screen, configure the following: l Filter Name: Backup Manager Enabled Devices l Is available to: Everyone l Show in Drop-down: selected Tip: Only filters that are configured to Show in Drop-Down can be associated to dashboards. 5. In the Find devices where section, configure the following: l Device > Backup Manager Enabled > EQUAL TO > True Note: The filter described above will locate any device (or devices) that have Backup Manager enabled. Optionally, you may wish to create two filters: one for Windows Servers and another for Laptop/Workstations. - 18 - N-central 9.1 Backup Manager Configuration and Deployment Guide Filter for Windows Servers Filter for Windows Laptop/Workstations Backup Manager Enabled Windows Backup Manager Enabled Windows Servers Laptop-Workstation (A AND B) (A AND (B OR C) A. Device > Backup Manager Ena- A. Device > Backup Manager Ena- bled > EQUAL TO > True bled > EQUAL TO > True B. Device > Class > EQUAL TO > B. Device > Class > EQUAL TO > Servers - Windows Laptop - Windows C. Device > Class > EQUAL TO > Workstation - Windows 6. Click Save. 7. Click Active Issues. 8. Click the Filter button and select the Backup Manager Enabled Devices filter created previously in this procedure. 9. Select the relevant Customer. 10. Select the Warning and Failed statuses. 11. Hover the mouse over any service status icon for a preview or select a service to view all details. 12. Click the Backup Manager Status service to review devices that are requiring a reboot to complete the installation of Backup Manager, Scheduling Device Reboots For Windows XP, Vista, Windows 7, Windows 2003 and Windows 2008 devices, N-central contains a Reboot Windows.vbs script which can be deployed to reboot remote devices. 1. Verify that the Customer is selected from the View Selection Menu in the top left of the main menu bar. 2. Click Actions > Run a Script. 3. In the Script section, verify that From N-central's Script Repository is selected in the Location drop-down menu. 4. In the Repository Item drop-down menu, select Reboot Windows. 5. In the Targets section: - 19 - N-central 9.1 Backup Manager Configuration and Deployment Guide a. Click By Filter Only. b. Select Backup Manager Enabled Devices (created previously in this procedure). c. Click > to move devices into the Selected Devices list. d. Click By Device Only. e. Select the devices requiring a restart. f. Click > to move the devices into the Selected Devices list. 6. Schedule the execution of the Reboot Windows script appropriately. 7. Select Notification recipients if necessary. 8. Click Save. Tip: In the navigation pane, click View > Job Status to review the progress of the script. Additional Backup Manager Tasks Additional Backup Manager tasks can include: l l Running an on-demand backup On-demand export of the last recovery point Running an On-demand Backup Perhaps before introducing a new application, upgrading an existing application or changing hardware configurations on a remote device, you wish to perform an backup of the device for disaster recovery purposes. 1. Verify that the Customer is selected from the View Selection Menu in the top left of the main menu bar. 2. Click Actions > Run a Backup. 3. Click Incremental Backup as the Backup Type. Note: An Incremental Backup is an excellent way to capture changes to the device since the last scheduled backup. 4. Select the device on which you wish to perform the backup. 5. Click Now in the Schedule Type drop-down menu. 6. Select Notification recipients if necessary. 7. Click Save. - 20 - N-central 9.1 Backup Manager Configuration and Deployment Guide Running an On-demand Export of Last Recovery Point Perhaps before conducting maintenance or changing hardware configurations on the network storage device which contains all customer backups, you wish to export the last recovery point for disaster recovery purposes. 1. Verify that the Customer is selected from the View Selection Menu in the top left of the main menu bar. 2. Click Actions > Export Last Recovery Point. 3. For Current Location, select The Recovery Point can be found in the location specified in the 'Copy Recovery Points' section of the device's Backup Manager profile. 4. For Desired Location, select Specify a custom destination. Note: In the event that the destination of all previously exported recovery points is the network attached storage on which you are performing maintenance, it would be best to export the last recovery point to an alternate location. 5. Type the Backup Destination Location. 6. Type the appropriate User Name and Password for the destination. 7. Select an Encryption Algorithm and type the Password if required. 8. Select the Compression type if required. 9. In the Targets section: a. Click By Device Only. b. Select the device (or devices) from which you will export the last recovery point. c. Click > to move the devices into the Selected Devices list. 10. Schedule the export as required. 11. Select Notification recipients if necessary. 12. Click Save. Tip: In the navigation pane, click View > Job Status to review the progress of the script. Restoring Data Restoring data from a backup must be done at the console of a device with Backup Manager installed. To access the Backup Manager web console from N-central, perform the following: 1. Navigate to the device within N-central from which you wish to restore data. - 21 - N-central 9.1 Backup Manager Configuration and Deployment Guide 2. Click the Remote Control tab. 3. Select Web Page as the Connection Type. 4. Select Local Agent for Connect Using. 5. Select HTTP as the Protocol. 6. Type 8014 for the Target Port. 7. Click Save. 8. Click Launch Remote Control. 9. Type the appropriate credentials to access the Backup Manager Console. 10. Click Restore in the Tasks pane displayed on the right side of the Backup Manager Console. 11. Click Find Files/Folders to Restore. 12. Verify that the Backup Location is correct. Tip: You can click -> to validate the connection between the device and the specified Backup Location. Tip: You can click Browse to select another Backup Location. 13. Select the search criteria to be used. 14. Click Find. 15. Select one or more File(s)/Folder(s) to be restored. 16. Click Next. 17. Click Restore File(s)/Folder(s) to either their original or a custom location. 18. Select the method to be used for resolving file/folder conflicts. 19. Select whether you want to create a root directory during the restore . 20. Click Next. 21. Review the Restore Summary. 22. Click Finish. - 22 - N-central 9.1 Backup Manager Configuration and Deployment Guide Outcome l l l l l A Backup Manager profile has been defined. Devices have been configured with appropriate credentials to allow the installation of the Backup Manager. Backup Manager has been deployed. Devices have been restarted to complete the Backup Manager installation. On-demand backups, exporting of recovery points and restoring data from backups have been described. Backup Manager Status N-central's Backup Manager Status Report can be used to display the history and status of backup jobs performed by Backup Manager and can provide an overview of the Backup Manager licenses that have been deployed to devices. To generate the Backup Manager Status Report within N-central: 1. Sign-in to N-central. 2. Select the appropriate Customer from the View Selection Menu in the top left of the main menu bar. 3. In the navigation pane, click Reports > Status > Backup Manager Status. 4. Select a report period. 5. Select the device (or devices) you want to be included in the report. 6. Select the Backup Type to be included in the report. 7. Select Include Licensing Information to display the type of Backup Manager license applied to each device. 8. Click View Report. - 23 - Disclaimer This document may include planned release dates for service packs and version upgrades. These dates are based on our current development plans and on our best estimates of the research and development time required to build, test, and implement each of the documented features. This document does not represent any firm commitments by N-able Technologies Inc. to features and/or dates. N-able Technologies will at its best effort, try to meet the specified schedule and will update this document should there be any significant changes. N-able Technologies reserves the right to change the release schedule and the content of any of the planned updates or enhancements without notice. Publication or dissemination of this document alone is not intended to create and does not constitute a business relationship between N-able Technologies and the recipient. Feedback N-able Technologies is a market driven organization that places importance on customer, partner and alliance feedback. All feedback is welcome at the following email address: [email protected]. About N-able Technologies N-able Technologies is the global leader in remote monitoring and management software for managed service providers and IT departments. N-able’s award-winning N-central platform and complementary toolsets, backed by best-in-class business and technical services, are proven to reduce IT support costs, improve network performance and increase productivity through the proactive monitoring, management and optimization of IP-enabled devices and IT infrastructure. N-able is 100% channel-friendly and maintains operations in North America, the U.K., the Netherlands and Australia. Copyright © 2012 N-able Technologies All rights reserved. This document contains information intended for the exclusive use of N-able Technologies' personnel, partners, and potential partners. The information herein is restricted in use and is strictly confidential and subject to change without notice. No part of this document may be altered, reproduced, or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of N-able Technologies. Copyright protection includes, but is not limited to, program code, program documentation, and material generated from the software product displayed on the screen, such as graphics, icons, screen displays, screen layouts, and buttons. N-able Technologies, N-central, and Report Manager are trademarks or registered trademarks of N-able Technologies International Inc., licensed for use by N-able Technologies, Inc. All other names and trademarks are the property of their respective holders.