Virtual Server Protection (VSP) for VMware and Microsoft Hyper-V

Transcription

1 Virtual Server Protection (VSP) for VMware and Microsoft Hyper-V User Guide 1

2 Commvault, Commvault and logo, the CV logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Simpana OnePass, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, IntelliSnap, ROMS, Commvault Edge, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice. DISCLAIMER Minor revisions and/or service packs that are released by application and operating system vendors are supported by our software but may not be individually listed in our System Requirements. We will provide information on any known caveat for the revisions and/or service packs. In some cases, these revisions and/or service packs affect the working of our software. Changes to the behavior of our software resulting from an application or operating system revision/service pack may be beyond our control. The older releases of our software may not support the platforms supported in the current release. However, we will make every effort to correct the behavior in the current or future releases when necessary. Please send an to for any problem with a specific application or operating system. Additional considerations regarding minimum requirements and End-of-Life policies from application and operating system vendors are also applicable. Support For support, send an to VM@commvault.com. 2

3 Contents Introduction to Virtual Server Protection (VSP)... 5 Key Features... 5 System Requirements... 6 Backup Server... 6 Hyper-V Nodes... 6 Virtual Machines... 7 Supported Web Browsers... 7 Hypervisor Platforms... 7 Installation... 8 Before You Begin... 8 Information Required... 8 Software Components Installed During Installation... 8 Installing VSP... 8 Using Quick Setup Before You Begin Logging In Registering Configuring Adding a Server Adding Storage Adding a Collection Performing a Backup Managing Schedules Restoring Virtual Machine Data Initiate the Restore Guest File Restores Virtual Machine Files Disk Level Restores (VMware only) Full VM Restores Adding Users

4 Managing Jobs Job Status Information Managing Alerts Alert Notifications Viewing Events Event Information Reports Commvault Enterprise Software Terminology Buying VSP or Extending Your VSP License

5 Introduction to Virtual Server Protection (VSP) Virtual Server Protection (VSP) can be deployed as an all-in-one data protection and recovery solution for virtual machines. The VSP package contains all components that are required to protect virtual machines in a compact configuration that can be used for evaluation and to provide ongoing protection. Virtual Server Protection uses a web-based interface that enables you to back up virtual machines running on VMware or Microsoft Hyper-V, restore data from virtual machines, and manage protection operations. To get started quickly, you can perform simple configuration of virtual machine servers, storage, and virtual machine collections in a few minutes, then initiate protection operations immediately. The Virtual Server Protection dashboard can be used to initiate backups and restores, provide summary information about virtual machine protection, and manage jobs, schedules, alerts, events, and users. Support To schedule a review session with a Systems Engineer to conduct a product overview, discuss best practices, design concepts, or general administration, or if you are having issues installing the software or are receiving error messages that require assistance, please submit a request to VM@commvault.com. Key Features Includes all components required to protect virtual machines in a VMware vcenter or ESX server, or in cluster shared volume (CSV) storage attached to Hyper-V servers. Provides a Quick Setup interface to configure host connectivity, storage, and backups in a matter of minutes, and back up selected virtual machines immediately. Performs off-host backups for virtual machines to support continuity of operations and disaster recovery. Provides granular backup and recovery options. Enables scheduled backup and restore jobs; virtual machines are automatically protected without user intervention. Provides source-side or target-side deduplication to reduce backup storage requirements and network traffic. Includes advanced configuration and management options. Includes monitoring and reporting tools for intelligent VM data analytics. Additional features for Microsoft Hyper-V: Enables backups of Hyper-V nodes without requiring that an agent be installed in each node. Includes automatic cluster awareness with full integration of CSVs and Live Migration protection for VMs that migrate to a new node. Provides application-consistent protection to enable rapid recovery of applications running inside virtual machines. 5

6 System Requirements Backup Server The backup server is the computer where you install VSP. This can be a physical computer or a virtual machine. For Microsoft Hyper-V environments, the backup server can be a standalone server or a node in the Hyper-V cluster. If VSP is installed on a standalone server, the server must be running Windows Server 2012 R2 or later. Ensure that the computer satisfies the following system requirements: Operating Systems Hard Drive Microsoft Windows Server 2012 R2 x64 Editions Microsoft Windows Server 2012 x64 Editions Microsoft Windows Server 2008 x64 Editions 100 GB recommended. Depending upon the number of virtual machines that you are planning to backup, ensure that the backup server computer has sufficient free space to store all virtual machine data. Memory Processor IIS 16 GB RAM minimum required All Windows-compatible processors supported IIS must be enabled on the backup server. Hyper-V Nodes For Microsoft Hyper-V, VSP can be installed on a standalone Windows machine, a standalone Hyper-V Server, or a node in the Hyper-V cluster. If VSP is installed on a machine that is not running Microsoft Hyper-V, additional software must be pushed to one or more Hyper-V Server nodes during Quick Setup. Hyper-V nodes must satisfy the following system requirements: Operating systems Microsoft Hyper-V Server 2012 R2 with latest Microsoft HotFixes installed Hard drive 100 GB recommended. If performing backups with the granular recovery option enabled, the location of the Job Results folder should contain additional space to accommodate at least 2% of the total amount of data being backed up. Memory Processor NTFS volumes 16 to 24 GB RAM minimum required beyond the requirements of the operating system and running applications. Dual Core with minimum of 2.2 GHz required The cluster size or the allocation unit size of an NTFS volume in a virtual machine must be a multiple of 1024 bytes. You can set the cluster size before formatting a volume. The default cluster size is 4096 bytes. 6

7 Virtual Machines For Hyper-V environments, VSP supports all guest operating systems supported by Microsoft Hyper-V. For VMware environments, the following system requirements apply for virtual machines: Virtual Machine Host The following versions are supported for vsphere, vcenter, vcenter Server Appliance, and ESX/ESXi: 4.1 or later, 5.0.x, 5.1.x, 5.5, 5.5.1, 5.5.2, 5.5.3*, 6.0, For any ESXi servers, the VADP is not available in the free version of ESXi. The Essentials licensing level or higher is required. Virtual Machine Hardware Virtual Machine Operating Systems VMware Tools on Virtual Machines Version 4.0, 7.0, 8.0, 9.0, 10.0, 11.0 All Guest Operating Systems supported by VADP and VCB Install the latest version of VMware Tools supported by the host on each virtual machine. At a minimum, the version of VMware tools on virtual machines must also be supported on the host; unsupported versions must be upgraded. Supported Web Browsers VSP can run on the following web browsers: Google Chrome v5 or later Microsoft Internet Explorer (IE) v8, v9 or later Mozilla Firefox v or later Safari v2.0.4 or later Hypervisor Platforms System Requirements for VMware System Requirements for Microsoft Hyper-V 7

8 Installation Install the software on a physical computer or a virtual machine. This computer is called the backup server. For Microsoft Hyper-V environments, the backup server can be a standalone server or a node in the Hyper-V cluster. If VSP is installed on a standalone server, the server must be running Windows Server 2012 R2 or later. Before You Begin Verify that the computer where you install the software satisfies the minimum requirements specified in System Requirements - Backup Server. Ensure that Server Manager is not running during the installation. Information Required Preferred installation path (if you do not use the default path) User credentials for the VSP administrator Notes: Do not install the software to a mapped network drive or on a compressed drive. When specifying the destination folder, use only alphanumeric characters. Do not use the following characters: / : *? " < > # Software Components Installed During Installation During the VSP installation, the following components are installed if they are not already available on the backup server: VSP software, including the Virtual Server Agent and MediaAgent Java 7 Update 17 Microsoft.NET Framework 4.0 Microsoft SQL Server 2008 R2 Microsoft Visual C++ Redistributables (2005, 2008, and 2010; can co-exist with other versions of this software) Commvault Web Server Commvault Web Console Installing VSP To install VSP, perform the following steps: 1. Log on to the backup server as an Administrator or as a member of the Administrator group on that computer. 2. From the location on the server where you downloaded the VSP installation package, right-click the package and select Run as administrator, then click Yes in the User Account Control dialog box. 3. In the Commvault Installer dialog box, verify the file path for the software installation. 8

9 4. You can choose Install Packages to install the software on the computer you are using, or Download Packages to download package files for installation on another computer. The installer downloads installation files and checks for prerequisite software. 5. If the server does not have.net Framework 4.0, the installer prompts you to continue by installing it..net Framework 4.0 can co-exist with other versions of.net Framework. Click Yes to continue by installing.net Framework. After installing.net Framework, the installer installs the VSP software and database engine. The installer customizes firewalls on the server, configures the Virtual Server Agent (VSA), initializes the database, and applies any required service pack updates. 6. When prompted, enter the user name and password for the VSP administrator. 7. When the setup is complete, click Finish. After installation, the web-based Admin Console launches automatically in your default browser. 8. Bookmark the page for future reference. The CommCell Console (desktop Administrative Console) also launches automatically; but you can close it and work in the web-based Admin Console. 9

10 Using Quick Setup After installation, use the Admin Console to configure your environment and run your first backup. Before You Begin Before beginning, gather the following information: Cloud Services user credentials VSP administrator s and SMTP server Server information and credentials for vcenter, ESX server, Hyper-V node, or Hyper-V cluster Additional Hyper-V nodes to serve as proxies Local or network storage location Small number of virtual machines to use for testing backup and recovery Logging In 1. To access Virtual Server Protection, point your web browser to the URL provided by your system administrator. For example: 2. Enter your user name and password, and then click Login. When you log in, the Servers page is displayed by default. If it is your first login and no servers are assigned to you, Quick Setup pages are displayed. 3. To log off, click your user name in the top right corner of the page and select Logout. When you log in for the first time, Quick Setup pages are displayed so that you can quickly configure VSP. Registering You can also register by clicking Settings. 1. On the Register product page, enter the and password associated with your Cloud Services account. 2. Click Save. Configuring You can also configure by clicking Settings. 1. On the Configure page, enter the following information: SMTP server - server for the user (for example, domain.com). SMTP port - Port used to access the server. The standard port is 25. Sender - The address that will be used to send alerts for this setup (for example, name@domain.com) Sender name - The name for the user who owns the alerts account. 2. Click Save to continue with server configuration. 10

11 Adding a Server You can also add a server from the Servers page. 1. On the Add server page, enter the following information: 2. For Select type, select one of the following: Hyper-V VMware 3. For Server name, enter a descriptive name for the server. 4. For Hostname / IP address, enter the fully qualified host name or IP address for the server. For VMware, the server can be a vcenter or a standalone ESX server. For Hyper-V, the server can be a Hyper-V cluster, a Hyper-V server in a cluster, or a standalone Hyper-V server. 5. Enter the user credentials for the server in the User name and Password fields. The server user must have administrative rights and appropriate permissions on the server. For each VMware vcenter, supply user credentials with appropriate permissions as described in Configuring User Accounts. 6. For a VMware server, select a Virtual Server Agent proxy from the Proxy list. This step is only required when adding an additional server to an existing configuration. When configuring the first server through the Quick Setup pages, the backup server is automatically enabled as a proxy. 7. For a Hyper-V server: a. Click Discover nodes. b. When the Nodes field is populated, select one or more nodes that should be configured as proxies to perform backup and restore operations. If the backup server does not have the Hyper- V role enabled, you must select at least one Hyper-V node to act as a proxy. 8. Click Save. 9. When configuring a Hyper-V server, click Go to Servers. For VMware, the Add storage page and Add collection page are presented automatically after configuring the server. For Hyper-V, you must go to the server page and wait until any requested proxy software installation is complete. After software installation, you must configure storage and a collection. Adding Storage For VMware, the Add storage page is presented automatically during Quick Setup. You can also add storage from the main Storage page. 1. Select Storage from the navigation pane. The Storage page displays the name, paths, free space, and total capacity for each storage location. 2. Click Add storage. 11

12 3. In the Add storage dialog box, select Local disk (on the backup server) or Network path, and then provide the following information: Storage name - Enter a name for the storage entry. MediaAgent - Select the media agent to be used to perform the backup. Storage path - Enter the full path name or click Browse to select a folder on the target system. User name (for network path) - Enter a user name with write access to the network-attached storage device. Password (for network path) - Enter the password for the user. 4. Click Save. 5. To add a path: a. In the main Storage page, under the Actions column, click Add path in the row for the storage name. b. Select Local disk or Network path, and then provide the following information: Storage name - Displays the storage entry. Storage path - Enter the full path name or click Browse to select a folder on the target system. User name (for network path) - Enter a user name with write access to the networkattached storage device. Password (for network path) - Enter the password for the user. c. Click Save. 6. To delete a path: a. In the main Storage page, under the Actions column, click Delete path in the row for the storage name. b. Click Yes to confirm the deletion. 7. To modify the name for a storage object or delete a storage object, click the name on the Storage page. Adding a Collection A collection identifies a specific set of virtual machines to back up. For VMware, the Add collection page is presented automatically during Quick Setup. You can also add a collection from a server page. 1. In the Servers page, click the name of the server that hosts the virtual machines. In the server page, the Collections area displays summary information for any existing collections. 2. Click Add collection. 3. In the Add collection dialog box, provide the following information: 12

13 Name - Enter a descriptive name for the collection. Browse and select VMs - Expand the tree below this field to select hosts, specific VMs, or VM storage locations for the collection. Click Select all to select all virtual machines or Clear all to remove all current selections. You can select one of the following options from the grouping list to control the browse display: Group by host - Select this option to view hosts and the VMs running on each host. Select a host entry to protect all VMs on the host, or expand the tree to select specific VMs. For Hyper-V, virtual machines are shown directly under the host. For VMware, the top level of the browse shows all accessible vcenters at the top level, ESX servers under vcenters, and virtual machines under each ESX server. VMs - Select this option to browse and select specific VMs. Storage (Hyper-V only): Select this option to view storage containing virtual machine data. Select the storage entry to protect all VMs on the storage, or expand the tree to select specific VMs. Group by datastore (VMware only) - Select this option to view datastores containing virtual machine data. The top level of the browse shows all accessible hosts at the top level, with datastores under hosts and virtual machines under each datastore. Select a datastore entry to protect all VMs on the storage, or expand the tree to select specific VMs. Retention period - Enter a value (1-90) to indicate the number of days that backup data should be retained. Storage - Select the location where backup data will be stored from the list. The list displays all storage locations that have been defined for Virtual Server Protection. No of readers - Set the number of readers to control how many parallel read operations can be launched during backups. 4. Click OK to save the collection. 5. After adding a collection using the Quick Setup pages, choose one of the following options: Click Back up Now to perform an immediate backup of the virtual machines in the collection (without requiring confirmation). The collections page displays job status information under the Backup heading. Click Do it later to save the new setup and continue to the Servers page, where you can explore further or perform additional configuration. 13

14 Performing a Backup You can run a backup from a collection of virtual machines defined for a server. The storage to be used for backups is configured as part of the collection. 1. Select Servers from the navigation pane, then select the server where the virtual machine is hosted. 2. Under Collections, click the name of the collection that contains the virtual machines to back up. 3. In the Backup section, click Back up now. 4. In the Backup options dialog box: Backup level - Select the backup type. (A full backup is always performed for the first backup of any virtual machine.) Full - Perform a full backup for virtual machines. A full backup includes virtual machine configuration files and all virtual machine data disks. Incremental - Selected by default. An incremental backup only backs up changes since the last full backup. Synthetic full - Create a synthesized backup from the most recent full backup and all subsequent incremental backups. The resulting synthetic full backup is identical to a full backup for the collection. Unlike full and incremental, a synthetic full backup does not actually transfer data from the production server to the backup media, and does not use any resources on the production server. Synthetic full backups are media-based; they read backup data from one media and simultaneously write (restore) the result to the new active media within the same media group. As a result, synthetic full backups require that at least two media drives for the same storage policy be available at the time the job is started. Synthetic full backups cannot be performed on collections where the storage policy is associated with a stand-alone drive. Enable granular recovery - Enabled by default. When this option is selected, metadata is collected during backup to enable you to browse and recover individual files or folders for a virtual machine. Clear the Enable granular recovery option to skip metadata collection; this results in a faster backup but does not enable file recovery; without metadata you can only recover full virtual machines. 5. Click OK to begin the backup operation. To schedule periodic backups, see Managing Schedules. Managing Schedules You can create a schedule for periodic backups from a collection of virtual machines for a server. 1. Select Servers from the navigation pane, and then select the server where the virtual machines to be backed up are hosted. 2. Under Collections, click the name of the collection that contains the virtual machines to back up. 3. In the Schedules section, click Manage. 4. In the Schedules dialog box, provide the following information: 14

15 Name - Enter a descriptive name for the schedule (for example, Weekly Full Backup). Backup level: Incremental - Selected by default. An incremental backup only backs up changes since the last full backup. Full - Perform a full backup for virtual machines. A full backup includes virtual machine configuration files and all virtual machine data disks. Synthetic full - Create a synthesized backup from the most recent full backup and all subsequent incremental backups. The resulting synthetic full backup is identical to a full backup for the collection. Unlike full and incremental, a synthetic full backup does not actually transfer data from the production server to the backup media, and does not use any resources on the production server. Synthetic full backups are media-based; they read backup data from one media and simultaneously write (restore) the result to the new active media within the same media group. As a result, synthetic full backups require that at least two media drives for the same storage policy be available at the time the job is started. Synthetic full backups cannot be performed on collections where the storage policy is associated with a stand-alone drive. A full backup is always performed for the first backup of any virtual machine. Enable granular recovery - Enabled by default. When this option is selected, file and folder metadata is collected during backup, enabling you to browse and recover individual files or folders for a virtual machine. Clear the Enable granular recovery option to skip metadata collection; this results in a faster backup but does not enable file recovery; without metadata you can only recover full virtual machines. Frequency: a. Select Daily or Weekly. b. Use the up and down arrows to set the time, or enter the time directly. c. Click AM or PM to toggle between morning and afternoon. d. For weekly backups, select one or more days of the week. 5. Click Save schedule. To modify an existing schedule, click the schedule on the collection page. 15

16 Restoring Virtual Machine Data You can restore virtual machines or virtual machine data from a server or collection. Recovery of files and folders is only supported if metadata was collected during the backup by selecting the Enable granular recovery option. Initiate the Restore 1. To restore virtual machine data, select Servers from the navigation pane, and then select the server where the virtual machine is hosted. 2. In the Collection section, click Restore for the collection that contains the virtual machine. 3. In the Select restore type page, select the restore type: Guest Files - Restore files or folders to the source virtual machine, to another virtual machine, or to a guest agent. Virtual Machine Files - Restore virtual machine configuration and VMDK files to the file system of the proxy. Disk Level (VMware only) - Restore individual VMDK files and attach VMDKs to an existing virtual machine. Full VM - Restore one or more full virtual machines. 4. In the Restore page, expand the tree on the left and select the objects to be restored on the right. Select an item or click on an entry in the Name column to browse within an item. For hierarchical data such as files, folders, and disks, you can click an entry in the path listing above the right pane to return to a higher level of the hierarchy. In the top right corner of the page, a "Showing" message indicates what backup data is being displayed. You can click the down arrow beside this message and select any of the following options: Show latest backups - Only display data for the most recent backups. Show backups as of a specific date - Only display data up to the date you specify. Show backups for a date range - Only display data within the data range you specify. 5. Click Restore. 6. In the Restore options dialog box, provide the requested information: Guest File Restores Virtual Machine Files Disk Level Restores (VMware only) Full VM Restores 16

17 Guest File Restores 1. Specify the destination for recovered files: For VMware: By default, files are restored to the source VM, using the same proxy as the backup. a. Optional: Change the value in the Proxy box to use a different proxy. b. Enter the username and password for the destination virtual machine. To restore to a different VM, select Other VM. By default, the same proxy that was used for the backup performs the restore. a. Optional: Change the value in the Proxy box to use a different proxy. b. If the destination VM resides on another server, select the host name of the server from the Destination server list, and then browse to select the destination VM. c. Enter the username and password for the destination virtual machine. To restore to a guest agent, click Guest agent. a. Enter the host name and credentials for the new destination server. b. By default, the Local System account on the destination client is used to perform the restore operation; but you can use the Impersonate user option to enter credentials for another user account. The user must have permissions to create files in the specified location on the destination. For Hyper-V: a. To restore to a different server, select the server name from the Destination server list. b. By default, the Local System account on the destination client is used to perform the restore operation; but you can use the Impersonate user option to enter credentials for another user account. The user must have permissions to create files in the specified location on the destination. 2. For the Path box, enter a full path or click Browse to select a destination folder. (For VMware, this value is only needed when you are restoring to a guest agent.) 3. To delete an existing file and replace it with the restored file, select Overwrite if it already exists. 4. Click Submit or Finish to run the restore job. Virtual Machine Files By default, virtual machine disk files are restored to the original server. 1. To restore to a different server, select the server name from the Destination server list. 2. By default, the Local System account on the destination client is used to perform the restore operation; but you can use the Impersonate user option to enter credentials for another user account. The user must have permissions to create files in the specified location on the destination. 3. For the Path box, enter a full path or click Browse to select a destination folder. 4. To delete an existing file and replace it with the restored file, select Overwrite if it already exists. 5. Click Submit to run the restore job. 17

18 Disk Level Restores (VMware only) By default, the virtual machine disk is restored to the source VM using the same proxy as the backup. 1. Optional: To use a different proxy, select the proxy from the Proxy list. 2. To restore to a VM on a different server, select the server name from the Destination server list. 3. To delete an existing virtual disk file and replace it with the restored file, select Overwrite if it already exists. 4. To restore to a different VM, click Browse under Destination VM and select the virtual machine. 5. To use a different datastore for the restored VM disk, select the new datastore from the Datastore list. 6. Click Submit to run the restore job. Full VM Restores By default, the virtual machine is restored to the same location as the source VM, using the same proxy as the backup. 1. To restore to a different server: For VMware: a. Optional: To use a different proxy, select the proxy from the Proxy list. b. To restore to a different vcenter, select the server for the vcenter from the Destination server list. c. Select Power on VMs after restore to start the VM automatically. d. To delete an existing virtual machine and replace it with the restored VM, select Overwrite VMs if they already exist. e. Enter a new virtual machine name in the Change VM display name to box. If an existing VM with the same name exists on the destination host and you do not select Overwrite VMs if they already exist, the restore job fails. f. To restore to a different host, click Browse next to the Destination host box and select the host. g. To use a different datastore for the restored VM, select from the Datastore list. h. To restore to a resource pool, select the destination from the Resource pool list. For Hyper-V: a. Select the target host from the Destination server list. b. Select Power on VMs after restore to start the VM automatically. c. To delete an existing virtual machine and replace it with the restored VM, select Overwrite VMs if they already exist. d. Enter a new virtual machine name in the Change VM display name to box. If an existing VM with the same name exists on the destination host and you do not select Overwrite VMs if they already exist, the restore job fails. e. Select Register virtual machine with failover cluster to enable the restored VM to migrate to another node in the cluster. 18

19 f. For Restore location, leave the default (Original folder), choose Select a folder, or select Hyper-V default folder. g. For Destination folder, click Browse to select a new folder from the list. (Only enabled if you chose Select a folder.) 2. Click Submit or Restore VMs to run the restore job. 19

20 Adding Users The Users page provides information about users and user groups who have access to Virtual Server Protection, and enables you to add, edit, or delete users. When configuring alert notifications, you can enter a user or group name to receive notifications for specific alerts. Add users to enable access to Virtual Server Protection: 1. Select Users from the navigation pane. 2. The Users page shows existing user definitions. You can click a user name to view details for the user, or click Delete in the Actions column to remove the entry for the user on the same row. You can control the columns that are displayed by clicking the icon under Add user. 3. Click Add user. 4. In the Add User dialog box, provide the following information: User name - Enter the name that will be used to log in to Virtual Server Protection. Full name - Enter the user's full name. - Enter the address for the user. Password - Enter the password with which the user can log in to Virtual Server Protection. Confirm password - Re-enter the password. User group - Select a group from the list: master - The user has full access to all Virtual Server Protection capabilities. View All - The user can view all Virtual Server Protection screens, but cannot change configuration options, perform backups, or perform restores. Restore operator - The user can view all screens and perform restores. Backup operator - The user can view all screens and perform backups. Enabled - When this option is selected (the default), the user can log in to Virtual Server Protection and perform any actions that are permitted for the user group to which the user belongs. When this option is cleared, the user cannot log in to Virtual Server Protection. 5. Click Save. 20

21 Managing Jobs Jobs can be monitored from the Jobs page, the Servers page, the summary page for a server, or the summary page for a collection. For a collection, you can view backup and restore jobs separately. Job listings can include backups and restores as well as other type of jobs for Virtual Server Protection and servers (for example, software updates or automatically generated system jobs). While a job is in progress, you can suspend, resume, or kill the job. 1. To view job information: Global - Click Jobs in the navigation pane to view all Virtual Server Protection jobs. By default, running jobs are displayed. You can choose the following options from the Showing list: Showing Running jobs or Finished jobs for Last 7 days, Last 14 days, or All days Server - Click Servers in the navigation pane. On the Servers page, under the Actions column, click... and select Jobs for a server to view all jobs for the server. Collection - Click Servers in the navigation pane, select a server, and click Jobs for a collection to view all jobs for the collection. Backup or restore jobs for a collection - Click Servers in the navigation pane, select a server, and select a collection. Click Jobs in the Backup area in the page. 2. For pending jobs, you can click the job ID to view job details, or click Pending and select any of the following actions: Suspend - Pause the job. Resume - Continue an operation that was suspended. Kill - Cancel the job. 3. From the summary page for a collection, pending jobs are shown under Backup or Restore. You can click X to kill a job, to suspend a job, or > to resume. Job Status Information The following information is displayed for jobs. (If you are viewing jobs for a server or collection, job listings would not include Server or Collection columns.) Job ID - A unique job identifier assigned by Virtual Server Protection. Click the job ID to display detailed information. Operation - The type of job: Install Client - Installed Virtual Server Protection software. Backup - Performed a backup. Synthetic Full - Performed a synthetic full backup. Restore - Restored virtual machines or data. 21

22 Pruning - Removed backup data after the retention period configured for the collection expired. Patch Update - Updated Virtual Server Protection software. CS DR Backup - Automatic database backup for disaster recovery. Report - Processed a report. Uninstall Client - Uninstalled Virtual Server Protection software. Status - The execution status of the job: Running - The job is in progress. Completed - The job completed successfully. Completed w/ one or more errors - The job completed but some error occurred and it is possible some data was not written. See the job details for more information, including the status for each virtual machine. Failed - The job encountered errors and could not be completed. Failed to Start - The job was unable to start. This status might indicate that another backup is already in progress for the same collection. Killed - The job was killed (cancelled) by a user. Pending - The job has encountered an error condition. Suspended - The job has been paused or suspended by a user. Size - The guest size of the virtual machine, or the used space for the virtual machine if guest size is not available. Server - The host for the virtual machine. Collection - The collection that includes the virtual machines for a backup job. Start time - The date and time the job was initiated. End time - The date and time the job ended. Elapsed time - The total amount of time that the job ran. JPR - A code for a Job Pending Reason (JPR) message. Click the code to view job details. Progress - The result of the job: (blank) - The job is waiting to start. (percentage value) - The job is in progress. Completed - The job completed successfully. Completed w/ one or more errors - The job completed but some error occurred and it is possible some data was not written. See the job details for more information. Failed - The job failed. Failed to Start - The job was unable to start. This status might indicate that another backup is already in progress for the same collection. Killed - The job was killed (cancelled) by a user. 22

23 Managing Alerts Alerts provide automatic notification about operations, such as failed jobs. Alerts are displayed on the Triggered Alerts page. For users that are identified by an address in the alert definition, alert notifications are also sent by . Virtual Server Protection includes preconfigured alerts that you can turn on or off; you can also specify which users or groups should receive alerts. Note: Alerts sometimes use terminology that refers to objects in the CommCell Console. For more information, see Terminology. You can view and configure alerts using the Alerts option on the navigation pane. From a server or collection summary page, you can change the user notification for any enabled alert. 1. To view all alerts for Virtual Server Protection, select Alerts from the menu bar. The Triggered Alerts page shows current notifications for any alerts that are enabled in Virtual Server Protection. See Alert Notifications. 2. To clear an alert notification, select the checkbox for the row showing the notification and click Delete. To clear all notifications, select the checkbox in the table header and click Delete. 3. To view and configure alert settings, click Alerts Definitions. 4. To enable or disable an alert, select or clear the checkbox in the Enabled column. 5. To view the definition page for an alert, click the alert name. 6. To make changes to the list of users and groups who receive notifications for an alert: a. Click Edit on the definition page for the alert. b. Enter a user or group name or an address. c. Select a value to identify the recipient type (User, Group, External group, or ). d. Click Add on the same row to add the user or group. e. Click Save on the bottom of the dialog to save changes for users and groups. You can also view alert information from the summary page for a server or collection, and make user notification changes as described here. Alert Notifications On the Triggered Alerts page, the following information is displayed for each alert: (checkbox) - Select the checkbox to apply an action for selected alerts. To select all alerts, select the checkbox in the table header. Severity - One of the following: Major - Indication that a major function is compromised and needs remediation. Critical - Indication that an error occurred and needs remediation. Information - Non-critical information that does not require immediate action. Detected criterion - Brief description of the issue. 23

24 Type - Type of event that caused the alert (for example, Data Protection or Data Recovery), as listed in the alert definition. Detected time - Date and time when Virtual Server Protection detected the alert condition. Computer name - Identifies the server, proxy, or virtual machine to which the alert applies. Alert info - Name of the alert. Click to view additional information about the alert. Pin - Click to save the alert notification and prevent it from being pruned. 24

25 Viewing Events The Events page provides information about jobs and other significant events detected by Virtual Server Protection. Note: Events sometimes use terminology that refers to objects in the CommCell Console. For more information, see Terminology. In some cases, events can trigger alerts to notify users of events (such as job failures). 1. To view event information, click Events in the navigation pane. The Events page shows summary information for each event. See Event Information. 2. Click an event ID to view details for an event. 3. To customize the columns that are displayed, click the menu icon at the top right. You can choose Toggle Filter from the menu to filter against values in the columns. Event Information The Events page shows the following summary information for each event: Severity - Info, Minor, or Major. Event ID - Automatically assigned identifier for a particular instance of an event. Click to view event details. Job ID - For job-related events, an identifier for the job in which the event was detected. Date - Date and time the event was detected. Program - The Virtual Server Protection component for which the event was detected. Computer - The host name of the computer on which the event was detected (the Virtual Server Protection server). Event code - System defined identifier for an event. Description - Brief description of the event, including identifiers for any jobs or objects associated with the event. To display the full description, mouse over the description. 25

26 Reports The summary page for a server or collection shows a VM status diagram indicating the number of protected and unprotected virtual machines. You can click the bar showing the number of VMs to view a report with additional details. Reports for protected or unprotected virtual machines show summary information for each virtual machine: Name - VM name. Backup status - Whether the VM is protected. Size (GB) - Size of the virtual machine. Backup size (GB) - The amount of data written during backup. Collection - The collection to which the VM belongs. Last backup time - The date and time when the last backup was performed. 26

27 Commvault Enterprise Software The CommCell Console (Commvault Administrative Console) is a desktop client that provides enterprise data protection and recovery capabilities, including support for additional hypervisors, advanced configuration options, and protection for other kinds of computers and applications. When you install Virtual Server Protection, the CommCell Console is also installed with support for virtual machine protection. For more information about virtualization support through the CommCell Console, see Virtualization. Terminology Backups provide full protection for virtual machines and data. Full backups are performed initially and can be scheduled on a periodic basis; incremental backups can be performed more frequently to capture changes since the last previous backup. In configuring backups, you can choose whether to enable granular recovery from backups. Commvault software provides management capabilities through the CommCell Console, including advanced administrative functions in addition to the functions that are available through Virtual Server Protection. Administrative changes and operations can be performed through Virtual Server Protection or the CommCell Console; any changes made through one interface are saved in the application database and are available from either interface. Deduplication identifies each block of data that is backed up and ensures that it is stored only once. Deduplication is automatically enabled for VSP and is managed through the storage policy and its copies. Hypervisors are platforms for hosting virtual machines, such as VMware, Microsoft Hyper-V, Citrix Xen, and Red Hat Enterprise Virtualization. Job streams move content identified in a subclient to a MediaAgent, which manages data streams to storage resources. Subclient properties can specify the optimal number of readers or streams. The actual number of job streams is determined by the associated storage policy and the available data paths. Multiple job streams can be included in each data stream. Stream data can use compression, encryption, and deduplication. MediaAgents transmit data between servers and storage media and manage backup data stored on media. Retention determines how long backed up data is retained. Retention controls are available at the subclient, job, media, and policy levels. Retention controls can be used to determine what storage media (for example, disk or tape) are used for different types of data, and when data aging can be used to remove or overwrite backed up data. Snapshots capture point-in-time state information. Hardware snapshots capture dynamic hardware mirrored volumes that can be quiesced, split apart and mounted on a proxy server, and used as a source for backup, archive, replication, or offline mining to minimize the impact on the production host. A hardware snapshot can also be used to recover a volume that is lost on the production server. Software snapshots can be used to get stable, crash-consistent backups when locked or opened files might be a concern. Subclients identify virtual machines to be backed up. They are equivalent to collections in VSP. The Virtual Server Agent is installed on computers that can perform backup and restore operations for a specific hypervisor platform such as VMware and Microsoft Hyper-V. For VMware support, the VSA is 27

28 installed on one or more physical computers or virtual machines. For Microsoft Hyper-V support, the VSA is installed on a standalone Hyper-V server or on Hyper-V servers in a cluster. Virtualization clients enable connections to hypervisors. They are equivalent to servers in VSP. The Web Console provides a self-service interface for end users of virtual machines, enabling them to recover VM data and (if configured) provision virtual machines. These components are installed automatically with Commvault software on a production server where IIS is enabled. Web Server software enables the presentation of the Virtual Server Protection interface as a web application. Storage Policies specify data retention and copy settings for storage locations. Virtual Server Protection automatically creates storage policies for disaster recovery and for backup storage. Buying VSP or Extending Your VSP License You can upgrade VSP to the full Commvault product. Contact your account team to obtain the appropriate license. You can extend your VSP license by sending an to Commvault Customer Support at prodreg@commvault.com. Include the IP address of the backup server. 28