Backup-as-a-Service with HP Helion CloudSystem Enterprise

Transcription

1 Technical white paper Backup-as-a-Service with HP Helion CloudSystem Enterprise Integrating HP LiveVault Service with OpenStack technology Table of contents Executive summary... 3 HP Helion CloudSystem 9.0 overview... 3 Introducing HP Helion CloudSystem... 3 HP Helion CloudSystem Foundation... 3 HP Helion CloudSystem Enterprise... 4 HP LiveVault overview... 4 Background assumptions... 5 Overview: HP LiveVault solution for CloudSystem... 6 Deploying HP LiveVault service on OpenStack virtual machine... 6 Integrating HP LiveVault Backup Service into HP Helion CloudSystem Enterprise... 7 Configuring HP Helion CloudSystem Enterprise... 7 Networking... 7 Creating the virtual machine image required for HP LiveVault deployment... 9 Uploading the image to Glance repository... 9 Staging the required software package... 9 Importing software and creating HP Server Automation policies Configure Server Automation provider for CSA Creating HP LiveVault Topology Service Design for adding and provisioning a computer to LiveVault Service Publish and create the service offering Creating and using the application service HP LiveVault Management portal Backup and restore using HP LiveVault Server Templates Returning the resource Remove computer from LiveVault Web Management Portal Monitoring and troubleshooting a deployment Summary... 35

2 Appendix A: Creating a CloudSystem Template with the HP SA Agent Appendix B: Software packages and policies Appendix B1: Software Policy to provision a computer to LiveVault Service Appendix B2: Software Policy to provision a computer to LiveVault Service using Server Templates Appendix C: Monitoring and troubleshooting a deployment For more information... 45

3 Executive summary Increasingly, organizations are choosing cloud-based backup to lower costs and reduce the administrative overhead of managing the server backup process. With an automated, secure cloud-based service, you can meet recovery point and recovery time objectives as well as business continuity requirements while allowing your IT staff to focus on strategic projects. This document describes how to use HP Cloud Service Automation (CSA), a component of HP CloudSystem Enterprise, to configure a service that can provide continuous data protection for customer s critical server environments by electronically vaulting their data to two geographically separated, secure off-site facilities. HP LiveVault 1 completely manages and pro-actively monitors deployed services. This solution leverages HP Server Automation to automate deployment of the HP LiveVault agent and provisioning the computer to the LiveVault service. Target audience: The intended audience of this white paper is system integrators, installers, and administrators who want to deploy Backup as a Service (BaaS) using HP Helion CloudSystem Enterprise, HP Server Automation, and HP Cloud Service Automation. This white paper describes testing performed in September HP Helion CloudSystem 9.0 overview Introducing HP Helion CloudSystem HP Helion CloudSystem is the industry s most complete, fully-integrated, end-to-end private cloud solution, delivering automation, orchestration and control, across multiple clouds. Over 3,000 customers, worldwide, are using HP Helion CloudSystem today for quickly deploying IT services, managing or developing applications, streamlining operations, and more. From basic infrastructure cloud services to the most advanced application cloud services, HP Helion CloudSystem 9.0 offers enterprises and service providers a clear path to hybrid cloud. With the incorporation of HP Helion OpenStack and the HP Helion Development Platform (HDP) into the new HP Helion CloudSystem 9.0 offering, we ve integrated a more complete OpenStack -based software offering directly into the product and added Cloud Foundry technology allowing you to create a modern developer environment in which to develop and deploy cloud native applications. HP Helion CloudSystem works in a heterogeneous environment and includes hybrid cloud management software, and based on the customer s unique needs may also include servers, storage and networking, combined with installation services, making it even more efficient to deploy a private cloud. HP Helion CloudSystem comes in two editions: HP Helion CloudSystem Foundation and HP Helion CloudSystem Enterprise. HP Helion CloudSystem Foundation If your organization needs a platform that supports basic cloud infrastructure services then you will need the easy-todeploy HP Helion CloudSystem Foundation, which targets simple IaaS and is delivered in the form of a virtual appliance. In addition to being a strong choice when simple infrastructure service delivery is the primary cloud objective, the small network footprint, and lower price of HP Helion CloudSystem Foundation software make it useful as a door opening offer for customers just getting started with cloud. It is built on HP Helion OpenStack and includes the HP Helion Development Platform (HDP) to enable the development of cloud-native applications. With HP Helion CloudSystem Foundation you benefit from: Open APIs for both administrative and cloud service functions, including OpenStack-based APIs, enabling highly automated cloud delivery Added support for OpenStack Swift object storage expands the scope of storage-centric use cases and environments to provision Includes the HP Helion Development Platform (HDP), which leverages leading open source technologies such as Cloud Foundry, Docker, and OpenStack providing greater support for cloud native application development Easier installation via a software appliance delivery model Support for deployment of services to VMware, Red Hat KVM and Microsoft Hyper-V host environments provides a more enterprise-friendly tool to provision virtualized environments in the cloud 1 This white paper was written before HP divested the LiveVault business. LiveVault is now part of j2 Global, a global provider of cloud and internet services. HP will continue to partner with LiveVault. For information on HP s announcement, visit: 3

4 Enhanced networking with support for DVR and VXLAN for improved multi-tenancy Intelligently target workload to infrastructure through support of availability zones and host aggregates improves separation of usage by different groups and services HP Helion CloudSystem Enterprise If you need a more robust, advanced cloud solution, then you are ready for HP Helion CloudSystem Enterprise. HP Helion CloudSystem Enterprise enables the broadest range of use cases and supports delivery of IaaS, PaaS, and SaaS models. These services are delivered through the inclusion of software such as HP Cloud Service Automation (CSA) and HP Operations Orchestration (OO). In addition, it includes HP Helion CloudSystem Foundation as well as HP Matrix Operating Environment (OE) as an alternate infrastructure provider that enables the delivery of a broad range of cloud services. HP Helion CloudSystem Enterprise is also delivered in the form of a virtual appliance. HP Helion CloudSystem Enterprise provides all the capabilities and value of HP Helion CloudSystem Foundation plus: Advanced infrastructure and application service delivery in minutes Support for public cloud resource providers through CSA enable enterprise-class lifecycle management for hybrid cloud services Expanded support of physical server provisioning via HP OneView integration allows you to leverage HP OneView profiles to create physical service designs in CSA CSA adds the ability to orchestrate through a self-service marketplace portal, allows both easier service lifecycle management and for IT consumers to request cloud services Investment protection for HP Matrix OE users; manage new OpenStack-based resource pools alongside your existing HP Matrix OE resource pools Enhanced drag-and-drop topology designer allows for rapid definition and orchestration of new multi-tier cloud services Improved Amazon Web Services (AWS) provider to support repatriating workload to HP Helion Eucalyptus private cloud HP LiveVault overview HP LiveVault allows businesses to protect their critical application data in the cloud, and manage the long-term retention needs addressing both of these concerns in a secure multi-tenant global, geographically dispersed cloud storage grid. The LiveVault agent encrypts all data before transferring it from the customer s servers. All data remains encrypted at secure, offsite, underground data centers, as well as on the optional TurboRestore Appliance (TRA) (which resides in the customer data center). To ensure the physical security and availability of stored data, the LiveVault service mirrors all data to a second, geographically dispersed data center, for full failover and redundancy Figure 1. Online Backup and Restore using HP LiveVault Client Location Data is replicated to two geographically separated mirrored HP data vaults online Backup Online Restore Internet Physical & Virtual Servers TurboRestore running Appliance LiveVault agent Backup to TRA Have Media Restore Device shipped to you HP Cloud Restore from TRA Secure Sockets Layer (SSL) protocol to establish a secure, resilient communication tunnel to offsite HP LiveVault data centers 4

5 Product features Easy-to-use, automatic, continuous, secure, and reliable online server backup in the cloud Proactive administration, monitoring, and notification Native, embedded data deduplication, providing maximum storage efficiency in the cloud Advanced encryption in transit and in storage, providing maximum protection for all data Recovery is fast and easy with LiveVault s patented Delta Restore capability, restoring only the data that has been changed, saving storage space, and recovery time LiveVault s Turbo Restore Appliance (TRA) provides an onsite optional appliance for rapid restores over local area network LiveVault s Data Shuttle enables customers with a service that provides the initial seeding and recovery of larger restores, expediting the backup/recovery process Extensive application and operating system support apply the value of Meaning Based Data Protection (MBDP) to both physical and virtual servers Product benefits Provides real-time meaningful capture of server data for use in backup and recovery, Legal Hold, ediscovery, and data analytics Achieves cloud data protection and long term offsite long-term retention Removes the burden of complex, daily backup administration Delivers point-in-time recovery of server data through continuous backup in the cloud and locally in the data center Provides data security data is secure and protected data, stored in mirrored, geographically dispersed data centers, with coveted certifications such as PCI DSS and ISO / Product differentiators Offers Meaning Based Data Protection in the cloud Massive scalability to meet the data protection demands of the largest customers, regardless of location or size Understands the meaning of server data for intelligent policy management and long term retention in the cloud Provides the ability to collect server data for any purpose or requirement, to aid in compliance and litigation related requests Built-in protection of open files and databases, without complex plugins or additional third-party tools/add-ons Background assumptions This implementation assumes that the reader has a general understanding of the HP Helion CloudSystem Enterprise environment and is capable of creating and deploying subscription services, is comfortable with Red Hat Enterprise Linux (RHEL) 6 distributions, and able to administer these environments. The reader should have basic knowledge about HP Helion CloudSystem Enterprise components including HP Helion CloudSystem Foundation, HP Cloud Service Automation, and HP Operations Orchestration as well as HP Server Automation. It is assumed that an HP Helion CloudSystem Enterprise solution has been successfully deployed and configured. Also that HP Server Automation has been installed and configured before attempting to deploy this implementation. The HP LiveVault software and license must be acquired through the appropriate channels. Links to the documentation for installing, configuring, and verifying these components and their interoperability can be found in the For more information section at the end of this document. Table 1 lists the versions used in this reference implementation. Table 1. Software components versions used for this implementation Component Version HP Helion CloudSystem Enterprise HP Helion CloudSystem 9 HP Cloud Service Automation 4.50 HP Operations Orchestration HP Server Automation HP SA HP LiveVault HP LiveVault

6 Determine if there is a firewall. If so, open ports 80, 443, 2144, and 2145 for LiveVault service communication. Overview: HP LiveVault solution for CloudSystem HP Helion CloudSystem Enterprise is the integrated bundle of HP Helion CloudSystem Foundation, HP Cloud Service Automation, and HP Operations Orchestration. HP Server Automation is included in HP Helion CloudSystem Enterprise PAA (Platform, Applications, and Analytics) add-on software. This document describes how to deploy HP LiveVault using HP Cloud Service Automation with VMware vsphere. This reference implementation utilizes the Topology Service Designer feature included in CSA to create a service which automatically deploys HP LiveVault Agent and provisions (or registers) the server to HP LiveVault Service. The service design deploys a VMware virtual machine instance which is enabled to use the HP LiveVault Service for online backup and recovery. Two CSA Topology Service designs are provided as examples in this document. 1. CSA Topology Service Design to install the LiveVault agent and provision the computer to LiveVault service. Once the computer is provisioned to LiveVault Service, provides an option for the user to decide which data to protect on individual servers, how to configure the backup policy through LiveVault web interface and how to restore the backed up data. 2. CSA Topology Service Design to install the LiveVault agent and provision the computer to LiveVault service using the Server Templates. In order to create this service design, we first have to create a Server template. Server templates let users configure and manage common agent settings and backup policies and apply them to multiple servers. All computers associated with a selected server template are protected in exactly the same way, with the same backup rule sets of included or excluded directories and files. Deploying HP LiveVault service on OpenStack virtual machine Deploying a service that uses HP LiveVault for online backup and restore using OpenStack as a provider in HP Cloud Service Automation is described in the steps below. Figure 2 gives a pictorial representation of the steps. 1. Create a service offering from the CSA Management Portal. 2. Publish the service offering. HP CSA is installed with a default global catalog. When a service offering is published in this global catalog, the service offering will be visible in the Cloud Subscriber Portal for every organization. 3. The User requests a service through the HP Cloud Service Automation Marketplace Portal. 4. HP CSA calls an OO workflow to deploy a VM from a specified glance image on to a Nova compute host. 5. The virtual machine is deployed on a Nova compute host. 6. An Operations Orchestration workflow deploys the HP LiveVault agent to the OpenStack virtual machine using Server Automation. 7. Once the LiveVault agent deployment successfully completes and registers with the HP LiveVault service, users can backup and restore necessary applications, folders, and databases using a web browser to log in to HP LiveVault Web Management Portal thereby managing the virtual machine. 6

7 Figure 2. Deployment of HP LiveVault service on VMware VM providing online backup and recovery Deploying HP LiveVault (providing automated and continuous backup) through HP Helion CloudSystem Enterprise HP Helion CloudSystem Enterprise HP Cloud Service Automation OpenStack Admin Management Console HP Operations Orchestration HP BladeSystem Marketplace Portal VMware vcenter Users ESXi ESXi ESXi VM VM VM HP LiveVault Web Management Portal HP Server Automation Deployed VM running HP LiveVault Agent HP LiveVault protects critical application data in the cloud and manages long-term retention needs Integrating HP LiveVault Backup Service into HP Helion CloudSystem Enterprise This reference implementation details the major steps required to create a HP Cloud Service Automation (CSA) service which deploys the HP LiveVault agent on the virtual machine which registers with the HP LiveVault service to provide backup and restore services for the virtual machine. They include the following: 1. Staging the HP LiveVault agent binary required for the reference implementation. 2. Create a Red Hat Enterprise Linux (RHEL) 6 VMware Virtual Machine image required for Virtual Machine deployments where the HP LiveVault agent will be installed to provision the computer to LiveVault Service. 3. Upload the image to the OpenStack Glance repository. The image will be used to create instances. 4. Importing and customizing the HP Server Automation software policies used to install and configure the LiveVault agent. 5. Creating Topology Service Designs and publishing Service Offerings in CSA. After these steps are complete, the Service Offering will be available for business users to automatically deploy using the CSA Marketplace Portal (MPP). A final step is also included that will decommission the service and return the resources to the HP Helion CloudSystem Enterprise environment. Configuring HP Helion CloudSystem Enterprise This reference implementation provides the steps required to create the necessary components for deploying HP LiveVault Online backup and recovery service that provides secure server cloud-based data protection into virtual machine instances deployed to HP Helion CloudSystem Foundation using HP Helion CloudSystem Enterprise. Networking For this implementation, OpenStack virtual machines are deployed with the Provider and Tenant network interfaces. The provider network is used for communication to Server Automation. An external router is used to communicate between the deployed VM, HP Helion CloudSystem Enterprise and Server Automation. The Tenant network is associated with a floating IP as shown in Figure 3. 7

8 Figure 3. Servers and Network layout External Network Tenant Network Provider Network DataCenter Management Network OpenStack Virtual Router Deployed VM External Router HP Helion CloudSystem 9 Foundation Deployed VM Server Automation HP Helion CloudSystem 9 Enterprise From the HP Helion CloudSystem Portal, click on Routers under Project and then Network section. Create a virtual router to the external network and add the tenant network as an interface to this router. The tenant network is associated with a floating IP. Communication to the HP LiveVault service is over the floating IP on the external network. The HP Helion OpenStack networking topology diagram for the solution is shown in Figure 4. Figure 4. HP Helion OpenStack Networking Topology 8

9 Creating the virtual machine image required for HP LiveVault deployment For this implementation we will demonstrate how to install the HP LiveVault agent on the Red Hat Linux Enterprise (RHEL) virtual machine. To accomplish this, a VMware virtual machine template with RHEL 6 needs to be created with two networks configured for DHCP. The information below describes the operating system and virtual machine specifications for deploying a Linux server running HP LiveVault used in this reference implementation. If you plan to use a different version, refer to the HP online help for the supported OS types and system configurations of the version of HP LiveVault agent you need to deploy. The storage and server requirements depend on your applications and database requirements. 1. Operating system: Red Hat Enterprise Linux (RHEL) version CPU, memory, and disk space: A. CPU: 1 or 2 x Intel Xeon Quad Core or equivalent B. Memory: 8 GB C. Minimum disk space: 10GB See Appendix A: Creating a CloudSystem Template with the HP SA Agent for details and instructions on how to create a RHEL 6.4x86 template for VMware that can be used in a CloudSystem Topology Design for VM instance deployments. Uploading the image to Glance repository 1. Launch HP Helion OpenStack user portal and log in as an administrative user. 2. From the Admin tab, select Images. 3. Click + Create image and provide the entries for the required fields: A. Name = Name for the OpenStack image B. Description = (optional) C. Image Source = Image File D. Image File = choose the file location E. Format = VMDK F. OS Type = Linux G. Public = Yes 4. Click Add to finish adding the image to Glance repository. Staging the required software package The required software package used in this implementation is LiveVault Linux agent software shown in Table 2. At the time of writing this document the current version was 7.80Build Newer versions may be available. An HP LiveVault account is required to download the agent software kit from HP LiveVault Web Management Portal and must be acquired through the appropriate channels. Table 2. HP LiveVault Software package Software 7.80Build12759.tar.gz Internet Location Access to this package requires an HP LiveVault account. Log on to your HP LiveVault account, On the Downloads tab, select the Agent as shown in Figure 5 and download the LiveVault Agent. The agent installation file, in this case 7.80Build12759.tar.gz, is downloaded to your computer. Create a temporary folder on your workstation that is running the Server Automation client and copy the agent installation file to the temporary folder. Newer versions of the package listed in Table 2 may be available but verify that any new versions are compatible. 9

10 Figure 5. Download Agent for HP LiveVault Importing software and creating HP Server Automation policies HP Server Automation software delivers automated server management for both your physical and virtual servers. It provides server lifecycle management from discovery to provisioning, patching to configuration management, and script execution to compliance assurance. HP Server Automation policies are used to deploy and configure the HP LiveVault agent on the virtual machines. The required file (7.80Build12759.tar.gz) staged in the previous section will be imported into HP Server Automation and used in software policies. ZIP packages will need to be imported into HP Server Automation and stored in the /Package Repository/All Red Hat Linux/Red Hat Enterprise Linux Server 6 X86_64 folder. Verify the OS type selected for the imported software is Red Hat Enterprise Linux Server 6 X86_64. This implementation will show how to create two types of Server Automation policies. Server Automation policy for provisioning a computer to LiveVault Service Server Automation policy for provisioning a computer to LiveVault Service using the Server template First we will create the server automation software policy named AutonomyLV_SAPolicy for installing LiveVault agent and provisioning the server to HP LiveVault for online backup and restore service. Later we will create the Server Automation policy named AutonomyLVTemplate for installing LiveVault agent and provisioning the server to HP LiveVault using the Server Template. For detailed instructions to create the HP Server Automation software packages and polices used in this service design refer to Appendix B1: Software Policy to provision a computer to LiveVault Service. Configure Server Automation provider for CSA Providers are management platforms that offer centralized control over the infrastructure and resources used in a cloud computing environment. The Helion OpenStack provider is automatically configured during CloudSystem 9 installation. The following steps configure the Server Automation provider: 1. Launch Cloud Service Management Console (HP CSA): A. Enter the URL for the HP CSA Console in a web browser and log in as an administrative user. B. The default URL is C. Select the Providers tile. 2. Create the provider for the HP Server Automation provider: A. Select HP Server Automation on the list of providers on the left panel. B. Click the Create button on the main panel. 10

11 C. Provide the entries for the required fields: i. Display Name = SA for HP CloudSystem ii. iii. iv. User ID = hpsa_admin (user having permissions to deploy SA software policies) Password = hpsa_admin user password Service Access Point = server IP address>:443 (Provider network) D. Click Create to save the settings. 3. Go to the Components tab. Import the SA software policy created in the previous section as a component. A. Click the Manage button to go to the Topology Components list. B. Click the Import button. C. Select HP Server Automation for the Import Source and leave Source Type as Live instance then click Next. D. Select AutonomyLV_SAPolicy from the list of HP SA Software Policies and click Next and then click Import. E. Click OK on the Success prompt. Creating HP LiveVault Topology Service Design for adding and provisioning a computer to LiveVault Service The following are the steps to create a service design that will deploy a virtual machine using the HP Helion OpenStack provider, install HP LiveVault agent and provision the virtual machine to LiveVault Service. 1. Log on to the HP Cloud Service Management Console (HP CSA) Console using an account with administrator privileges if you are not logged in. 2. Go to Designs Topology Designer. 3. Click the Create button. 4. On the Create Design General dialog enter the following field values then click next as shown in Figure 6: A. Palette = none B. Name = Sample HP LiveVault Design (specify a unique name for the service design) C. Description = [OPTIONAL] D. Version = Figure 6. Create CSA Design 5. Click Create. 6. Select the Designer tab. 7. On the left pane, at the bottom Search area, type OpenStack to filter OpenStack components. 11

12 8. Drag and drop the OpenStack Server and OpenStack Network Interface components on to the canvas as shown in Figure 7. Figure 7. OpenStack Components 9. Relationships in topology design define dependencies between two components. Connect the OpenStack Server and the OpenStack Network Interface as shown in Figure 8. You can click on the red warning icon on the left of each component to see the mandatory and required relationships. For example, the OpenStack Server requires a relationship to OpenStack Network Interface. Figure 8. OpenStack Component Relationship 10. Similarly drag and drop OpenStack Private Network on to the canvas and connect OpenStack Network Interface to OpenStack Private Network. 11. Drag and drop OpenStack Floating IP. Connect OpenStack Network Interface to OpenStack Floating IP. 12. Drag and drop OpenStack Router on to the canvas and connect the OpenStack Router to OpenStack Private Network. 13. Connect OpenStack Floating IP to OpenStack Router. 14. Drag and drop OpenStack External Network on to the Canvas and connect the OpenStack Router to OpenStack External Network. 15. Drag and drop a second OpenStack Network Interface on to the Canvas. Connect the OpenStack Server to the second OpenStack Network Interface. 16. Connect the second OpenStack Network Interface to OpenStack Security Group. 17. Drag and drop a second OpenStack Private Network on to the canvas. Connect the second OpenStack Network Interface to the second OpenStack Private Network. 18. Connect the OpenStack Private Network to the OpenStack Router. 19. Finally drag and drop AutonomyLV_SAPolicy component on to the canvas and connect the component to the OpenStack Server. Connecting these components according to their expected relationships is shown in Figure 9. You might want to place components on the canvas in a different way than shown here. 12

13 Figure 9. Connecting OpenStack components in CSA Designer 20. Select each component that has a red warning icon and type a value for the required property; then save the configuration for each property. Enter the values as in Table 3. Double check the values in Horizon Portal. Values must match the exact name of elements defined in HP Helion OpenStack portal. For this implementation, we have used the following and left the rest as defaults. Note A keypair for the enterpriseinternaluser account is required. Log in to the HP Helion OpenStack portal with the enterpriseinternaluser account and create a keypair. To get the password for the enterpriseinternaluser log in to the management appliance (ma1) and view the /etc/cloudsystem/keystone_credentials.json file. The enterpriseinternaluser password is stored in this file. A sample keystone_credentials file is shown below: root@ma1:/etc/cloudsystem# cat keystone_credentials.json { "user": "enterpriseinternaluser", "password": "14e06a6c0df588c3e4200f747795b3e0" } Table 3. OpenStack Components Properties Component Property Value OpenStack Server flavorname String (e.g.: m1.medium) imagename keypairname servernameprefix String (Name of the image in OpenStack) String (Keypair created for enterpriseinternaluser) String OpenStack Network Interface enableusercontext Boolean (leave the default value, i.e., false) OpenStack Security Group SecurityGroupNames String (name of the Security Group, e.g.: SG1) 13

14 Component Property Value OpenStack Private Network (Tenant network) networkname String (tenant network, e.g.: demo_net1 OpenStack Private Network (Provider Network for Server Automation connectivity) subnetname networkname subnetname String (subnet of tenant network, e.g.: demo_subnet1) String (Provider network, e.g.: Provider810) String (subnet of Provider network, e.g.: Provider810-Subnet) OpenStack Router routername String (Router name, e.g.: demo_router) OpenStack External Network externalnetworkname String (Name of the external network, e.g.: ext-net) OpenStack Floating IP (no property) There are no properties for the AutonomyLV_SAPolicy Policy component. Click Save. Make sure there are no red warning icons to indicate that your design is valid. 21. It is a best practice to perform a Test Run of the newly created Topology Design before publishing: A. Go to the Overview tab of the Design Details page. B. Click the Test Run button. C. Provide the Name of the Test Run. The rest of the fields are optional. Click Finish. D. Click View to check the status. You may need to refresh the page to reflect the current status. You should see the status as online as shown in Figure 10. Figure 10. Test run status E. Launch the HP Server Automation Java Client. Select the Devices tab Servers All Managed Servers and the newly deployed VM should be listed. Publish and create the service offering A service offering must be published and created in HP Cloud Service Automation before subscribers can request services based on this service design. To publish a service offering, complete the following steps: 1. Log on to the HP Cloud Service Management Console (HP CSA) using an account with administrator privileges. 2. Go to Designs Topology Designer. 3. Select the service design: Sample HP Autonomy LiveVault. 4. On the Overview tab, click the Publish button. 5. Click Yes to the Confirm Publishing pop-up. 6. Click on the Cloud Service Automation link in the title bar next to the HP icon to get back to the main page. 14

15 To create a service offering in the default catalog, complete the following steps: 1. Go to Offerings. 2. In the All Offerings panel, click Create. 3. On the Create Offering dialog: A. Leave the Offering Type set to Standard. B. Select the Service Design by clicking the ellipsis button. C. Select the Topology Design named Sample HP Autonomy LiveVault then click the Select button. D. Enter Sample HP Autonomy LiveVault on the Display Name. E. [OPTIONAL] Enter Description and Image for the offering. F. Click the Create button. HP Cloud Service Automation is installed with a default global catalog named Global Shared Catalog. When you publish a service offering in this global catalog, that service offering will be visible in every organization s Marketplace Portal. 1. On the Offerings details page: A. Go to the Publishing tab. B. Click Publish to launch the Publish Service Offering dialog. C. Select Global Shared Catalog. D. Expand the In Category dropdown and select a category, i.e., Application Services or Backup Services. E. Click Publish on the Publish Service Offering dialog. F. Click Close on the Success message box. Verify the published service offering: 1. Go back to the main page of HP Cloud Service Automation. 2. Go to Catalogs. 3. Select the Global Shared Catalog. 4. Go to the Offerings tab and you should see the offering for Sample HP Autonomy LiveVault as shown in Figure 11. Figure 11. Global Shared Catalog 15

16 Creating and using the application service A new request is created when an order for a subscription is submit from HP CSA Marketplace Portal. When the request for a new subscription is approved, an OpenStack virtual machine is provisioned and the HP LiveVault agent will be installed, configured and provisioned to LiveVault Service. Once the virtual machine is provisioned to HP LiveVault Service, the LiveVault Web Management Portal guides through the initial backup configuration process, and then LiveVault continuously backs up the data and applications. Below is an example of how a subscriber can order the HP LiveVault service from HP Cloud Service Automation Marketplace Portal (MPP) using the default consumer portal. Creating a subscription in HP Cloud Service Automation You can order the HP LiveVault service from the HP Cloud Service Automation Marketplace Portal. 1. Launch HP Cloud Service Automation Marketplace Portal: A. Enter the URL for the HP Marketplace Portal in a web browser. B. The default URL is 2. Click Log In and enter the following information: A. Username: Your HP Cloud Service Automation Marketplace Portal user name, i.e., consumer. B. Password: Your HP Cloud Service Automation Marketplace Portal password. 3. Expand the Sidebar Menu by clicking on the icon shortcut and select Browse Catalog. 4. Select the service offering called Sample HP LiveVault as shown in Figure 12. Figure 12. Browse Catalog 5. Click the Checkout button. 6. Provide a Subscription Name of your choice. Description is optional. 7. Click the Submit Request button to deploy the service offering request. 8. You can monitor the progress of the request by clicking the View Requests button on the Request Confirmation details. 9. The status of your subscription can be monitored on the subscriptions panel by clicking Subscriptions on the Sidebar Menu. A typical end to end deployment takes 5 to 8 minutes to complete. Note This reference implementation uses the default Marketplace Portal. If your environment is set up for a different consumer organization, the unique URL for the Marketplace Portal organization can be found on the organization page in the CSA Administrator portal. 16

17 Accessing the subscribed HP LiveVault service 1. Log on to the HP Cloud Service Automation Marketplace Portal (MPP) using your consumer user account (or the same account you used to deploy the service). 2. On the main page of the MPP, expand the Sidebar Menu and select My Services. 3. Select the service name Sample HP Autonomy LiveVault. If it successfully deployed from the previous step, the service will have a green Online Services banner. 4. On the My Service Details for the deployed service, scroll down to the HP LiveVault Server. Take note of the External IP Address value and hostname as shown in Figure 13. Figure 13. Marketplace Portal Service Details 17

18 18

19 HP LiveVault Management portal Log in to HP LiveVault Management Portal, using your account credentials. Verify that your computer has been registered with the service. As shown in Figure 14, the computer registered to LiveVault service is LV-8fac3bed d1-ba11-1dbc5434e8c5. This is the same hostname that you noted from Figure 13 in the previous section. Figure 14. HP LiveVault Management Portal Configure a new computer 1. On the LiveVault Web Management Portal navigation pane, select the new computer you added from the Computers section. 2. The New Computer Wizard opens as shown in Figure 15. Figure 15. New Computer Wizard 19

20 3. Review the Computer information summary, which includes the agent software versions on the computer and the operating system on the computer. 4. The system names your computer when you install the agent software. This is the default hostname. However, you can change this name to a user friendly name in the computer Name field, i.e., RHELServer Select a Subscription for this computer from the list of available plans. The above screenshot in Figure 15 shows two possible options Backup and Restore data and Only Restore data to this computer. For this implementation we used the Backup and Restore data option. 6. Click Save to complete configuring the backup for this computer. You should see the name of the computer server being renamed, as shown in Figure 16, to the server name assigned on Step 4 above, i.e., "RHEL Server 1". Figure 16. Computer Servers Backing up your data The LiveVault Web Management Portal guides you through the initial backup configuration process. LiveVault backup features are: LiveVault continuously backs up your data and applications. LiveVault backs up the files while they are open and in use by other applications. LiveVault backs up all types of files (databases and applications, documents and spreadsheets, Windows System State, including Active Directory, etc.) Set up a Backup Policy A policy can back up an entire computer or selected files, applications, and databases. However, it will not back up those files and directories that you specifically exclude from backup. You can create multiple policies. There are some files that LiveVault automatically excludes from backup. For a list of these files and items, see Automatic and Recommended Backup Exclusions and Backup Restrictions and Limitations. When you create policies, verify that the clock time and time zone designation on the deployed VM (HP LiveVault agent machine) is correct. If the time or time zone is incorrect, in rare cases it can cause restorations from the initial backup to fail. 20

21 To start using LiveVault to back up the selected server, you first need to create a policy. For this deployment we are creating a Standard Policy. 1. Select the computer to create the backup policy. In this implementation select RHEL Server 1. (Figure 17, left pane.) 2. Click the add new Standard Policy for backing up selected files, directories or drives. Figure 17. Add new Standard Policy 3. You may replace the Backup Configuration name from its default New Backup Policy. For this solution, we are backing up /etc, /home and /var. Select folders as per your production environment backup requirements. Figure 18. Backup Configuration 21

22 4. Select the Schedule tab to specify when you would like to have your backup for this policy executed. The backup will automatically execute during the time period specified in your backup schedule as shown in Figure 19. Figure 19. Schedule backup 5. Select the Options tab and select the Retention policy to provide the information for the duration of the backup on this policy as shown in Figure 20. Figure 20. Retention Policy 22

23 6. One you have the completed setting the backup configuration settings, click Next; then review the backup configuration as in Figure 21. Figure 21. Review backup configuration 7. Click Done and you should see the Standard Policy Backup Summary as in Figure 22. You can choose to edit the policy or add a new Standard Policy at any time. Figure 22. Backup Summary 8. Install your applications, database, etc. as per your production server requirements on the server. In this solution, for testing we are going to create the HPLiveVault folder consisting of the three files DataProtection, LiveVault and ServerSupport on the server that will be targeted for backup and restore as shown in Figure 23. Figure 23. Folders and Files in /home 23

24 Initial backup The first time you configure backup for a computer, an initial backup runs. During this initial backup, a copy of each file and directory selected to be backed up is transferred to a backup server, creating an image of the files and directory structure in encrypted and compressed format. The initial backup runs until the first copy of all data selected for backup has been sent to the backup servers. The time required to complete the backup depends on the amount of data you are protecting and the available bandwidth. As the initial backup is running, you can track the progress on the Backup tab of the computer agent Home page. After the initial backup completes, the computer is protected. You cannot perform restores until the initial backup is complete. Back up changed data After the initial backup of a file, LiveVault transfers only the changes, or deltas, that are made to the files under protection. This allows LiveVault to continuously back up your data while minimizing the network bandwidth it consumes. When the LiveVault agent performs a backup, a snapshot utility takes a point-in-time picture of the file system. Between snapshots, LiveVault monitors the file system for changes, maintaining a map of changes since the last backup. The LiveVault agent accesses information in this point-in-time snapshot to determine what has changed. After the agent identifies the changed data, the agent sends the changes to the backup servers. This delta backup method ensures that your backed up data is up-to-date without having to scan the file system for changes. This lets backup occur more efficiently while minimizing bandwidth usage and system resource usage. It is a good idea to test the backup and ensure that data can be restored. The folder HP LiveVault and the files in the folder have been deleted as shown in Figure 24. The will allow us to test the restore procedure. Figure 24. Deleted HPLiveVault folder from /home 24

25 Restoring your data The Restore Wizard guides you through requesting a restore. You can restore files over the Internet or have a restore device sent to you. After you determine the restore method, select files and options on the Restore Request page. For this implementation we will be restoring files over the Internet. To restore data from a standard backup policy 1. In the Home page, select the Server as shown in Figure 25. Figure 25. Select the server for restoring data 2. Select the Restore tab. The Restore tab displays any previously submitted restore requests. Figure 26. Restore summary 3. Click New Restore. The Restore Wizard page opens. 25

26 4. Select one of the following two options as in Figure 27. A. Restore data over the Internet. The Restore Request page opens, letting you select the files you want to restore over the Internet. In this implementation we will restore over the Internet as detailed in Step 5. B. Have Media Restore Device shipped to you. The system displays a page for you to select the version of data to restore, and the shipping method. When you click Next, the Restore Wizard Shipping Information page opens, requesting the address for shipment of the restore device. When the restore device arrives, you attach it to your network. You can then restore the backed-up files. Figure 27. Restore Request options 5. The Restore Request page has two tabs: A. The Selection tab lets you browse to select the directories and files you want to restore, or click Advanced to use rules as filters for directory and file selection. Figure 28. Restore Request page 26

27 B. The Options tab lets you handle file overwrite situations, restore to a different computer than the files were backed up from, specify system state restore, and schedule the restore. Figure 29. Restore Options 6. Provide a Name to use for this restore request then click Next. The Restore Wizard Confirmation page opens. 7. Review the information as shown in Figure 30. Figure 30. Review restore selections 27

28 8. Click Done. Once the restore is completed, the status is displayed as shown in Figure 31. Figure 31. Restore Job status 9. After the restore you should see the folders and files that have been deleted being restored as shown in Figure 32. Figure 32. Restored folder and files 10. You will also receive an notification regarding the restore status. 28

29 Backup and restore using HP LiveVault Server Templates Server templates let you configure and manage backup policies and apply them to multiple servers in your organization. You use server templates during the software distribution, installation and provisioning of multiple servers in your organization to HP LiveVault Service. Create a server template 1. In the navigation pane, click Account at the top of the page. The Customer Properties page opens as in Figure 33. Figure 33. Customer Property Page 2. Click the Server Template Management link at the bottom of the page. The Server Template Management page opens as in Figure 34. Figure 34. Server Template Management 3. Click Add server template. The Add server template page opens. 4. Enter a name in the Name field. 5. Enter a description in the Description field. [Optional] 6. Select either Windows or Linux OS type. 7. Select a Computer subscription from the list. 8. Select a Primary technical contact from the list. 9. Optionally, select a Secondary technical contact from the list. 29

30 10. Select an option for managing software updates: A. Install newly available updates only after approval: Select if you want the system to inform you when an update is available so you can opt whether to perform the update. B. Install newly available updates automatically: Select if you want updates to occur automatically. If you select this option, you can enter the day and hour for when to permit installation, as follows: Day and hour when installing updates is permitted: Because an installation can require the computer to restart, use this option to specify a day and hour for when to permit update installation. Figure 35. Add server template Create a standard backup template associated with a server template 1. Click to define a backup template based on volume, directory or file rules. The Add standard backup template page opens. 2. Enter a name in the Name field. This name becomes the backup policy name for each protected computer. 3. Select a retention policy from the Retention policy list. 4. Select a schedule for backup from the Backup schedule list. 5. To create a backup rule, complete the following steps: A. Select Include or Exclude to specify what you select in a backup policy. Note: You cannot create a rule to exclude items unless you create an associated rule to include items. B. Create file-matching criteria to identify files to which the rule applies: In the Rule Type box, select one of the following to determine how the rule treats the expression in the File box: All in directory: Include/exclude all the files in the directory path specified in the Directory box. Beginning with: Include/exclude files and directories whose name begins with the expression in the File box. Ending with: Include/exclude files and directories whose name ends with the expression in the File box. Containing: Include/exclude files and directories whose name starts with, ends with, or contains the expression in the File box. Matching wildcards: Include/exclude files and directories whose name includes the expression in the File box. Use this option when the expression in the File box uses a wild card. Exactly matching file: Include/exclude files and directories whose name matches the expression in the File box. C. In the Directory box, type the path of the files that you want to include or exclude from backup. You must type a full path. For example: In Linux use /etc D. In the File box, enter characters to identify which files you want to apply the rule to. If Matching wildcards is selected in the Rule Type box, the file pattern can include wildcard characters. If All in directory is selected in the Rule Type box, the File box is not available to enter text. 30

31 E. If you want the rule to apply to files located within the specified directory and to files within all subdirectories below it, set the Subdirectories box to Yes. Set this box to No if the rule is to apply only to files in the directory specified. 6. Click to add a rule. A table of rules is created, displaying your selections. In this deployment we have created rules to include /etc, /home and /var as shown in Figure 36. Figure 36. Backup rule 7. Repeat Step 5 (a through f) to create as many additional rules as needed. 8. Optionally, delete a rule from the rules list by clicking the delete button for a selected rule. 9. Optionally, change the order of a selected rule within the rules list, by clicking the up or down arrow. 10. Click Save to save, or Cancel to discard the changes to the standard backup template. Once it is saved you should see the backup template in the list of backup templates as shown in Figure 37. Figure 37. List of Backup templates 31

32 11. Click Save on the Add server template dialog and the Server template is saved with an ID as shown in Figure 38. Figure 38. Server template ID 12. Now you can configure and manage common agent settings and backup policies and apply them to multiple servers in your organization by using the Server Template ID, i.e., 217 in the above figure. Note: Server Template Considerations You must define server templates with at least one backup policy template. Once you assign a template to the servers in your organization, you cannot reassign them to another server template. You cannot assign server templates to computers already protected by LiveVault. You associate a server template with one or more agents during command line installation and provisioning of the agent software; it cannot be done from the Web UI. Importing software and creating HP Server Automation policy for provisioning a computer to LiveVault service using Server Template At this point you are ready to import the package LiveVault.zip and create the Server Automation Software policy AutonomyLVTemplate. The software policy is used for installing LiveVault agent and provisioning the server to HP LiveVault online backup and restore service using LiveVault Server template. For detailed instructions to create the HP Server Automation software packages and polices used in this service design refer to Appendix B2: Software Policy to provision a computer to LiveVault Service using Server Templates. Configure Cloud Service Automation SA Provider 1. Log on to the HP Cloud Service Management Console (HP CSA) using an account with administrator privileges if you are not logged in. 2. Go to the Providers Tile. 3. Click HP Server Automation provider. 4. Go to the Components tab. Import the SA software policy created in the previous section as a component. A. Click the Manage button to go to the Topology Components list. B. Click the Import button. C. Select HP Server Automation for the Import Source and click Next. D. Select AutonomyLVTemplate from the list of HP SA Software Policies then click Next, Next and Import. 32

33 Creating CSA Topology Service Design for adding and provisioning a computer to LiveVault Service using LiveVault Server Template The following are the steps to create a service design that will deploy a LiveVault Agent in a virtual machine using the OpenStack provider and provision the virtual machine to LiveVault Service 1. Log on to the HP CSA Management Console using an account with administrator privileges if you are not logged in. 2. Go to Designs Topology Designer. 3. Select Sample HP LiveVault Design. 4. Click on New Version and provide a new Version number as shown in Figure 39 and provide Version number and Description (optional). Figure 39. Create new version for the design 5. Click Create. 6. Delete the OpenStack component AutonomyLV_SAPolicy. 7. Drag and drop the AutonomyLVTemplate OpenStack component on to the canvas. 33

34 8. Connect the Autonomy_LVTemplate component to the OpenStack Server components shown in Figure 40. You might want to place components on the canvas in a different way than shown here. Figure 40. Connecting OpenStack components in CSA Designer 9. Click Save. 10. It is a best practice to perform a Test Run of the newly created Topology Design before publishing: A. Go to the Overview tab of the Design Details page. B. Click the Test Run button. C. Provide the Name of the Test Run. The rest of the fields are optional. Click Finish. D. Click View to check the status. You may need to refresh the page to reflect the current status. You should see the status as Active. E. Launch the HP Server Automation Java Client. Select Devices tab Servers All Managed Servers and the newly deployed VM should be listed. Publish and create the service offering using LiveVault Server Templates Follow the steps in Backup and Restore using LiveVault Server Templates Publish and creating the service offering Once the subscription is completed log in to LiveVault Service and check if the computer is associated with the server template that was defined. 34

35 Returning the resource If you no longer need the deployed HP LiveVault service, this section describes the steps to return the resources used. 1. Log on to the HP Cloud Service Automation Marketplace Portal using your consumer user account (or the same account you used to deploy the service). 2. On the main page of the Marketplace Portal, expand the Sidebar Menu and select My Services. 3. Select the HP Autonomy LiveVault service subscription. 4. On the My Service Details view, click the grey Manage Subscription button. 5. Click on the red Cancel Subscription button. 6. Click Yes on the message box pop-up. 7. The Subscription Status is updated to Cancelled Subscription. Note Your cancellation time may vary depending on the hardware in your environment. If notification is configured, you will be notified by that the service has been cancelled. When a subscription is cancelled from the MPP, The cancellation will not remove the computer from the LiveVault service or delete the previous backups. Remove computer from LiveVault Web Management Portal 1. In the navigation pane, select the name of the computer you want to delete. 2. The Summary tab for the computer opens. 3. Click Delete. This button is not available if the agent software is still on the computer. 4. Click Delete again on the confirmation. Note When you delete a computer, you also delete all historic backed up information for that computer. Do not delete a computer if you want access to any historic backed up information. Instead, disable the computer. Monitoring and troubleshooting a deployment If you wish to follow the service deployment process more closely, you can do so through the various provider interfaces. Refer to Appendix C: Monitoring and troubleshooting a deployment. Summary Cloud server backup solutions automatically protect mission-critical data from natural and human-made disasters, virus attacks, human error, equipment failures, and other disruptions. HP LiveVault is a fully managed cloud data protection service that automates, streamlines, and reduces the complexity of server data protection. It provides continuous backup, with protection intervals as low as every 15 minutes, to ensure data is protected as it is created. LiveVault helps you achieve speed, flexibility, and cost-effectiveness so that you can focus on your strategic goals and be more competitive. Recovery is simple and straightforward. Organizations can select the data to recover from a catalog of archived file versions, and LiveVault automatically restores the data to the location of your choice. LiveVault leverages the cloud to automatically transfer data offsite for disaster recovery. Data is backed up off-premise shortly after being updated, allowing organizations to restore data from moments before a disaster occurs. Adding the HP LiveVault agent to your CSA service designs provides an online backup service to CSA subscribers. This backup service can also be pre-configured to use a template that targets specific files and folders for backup. The LiveVault agent will automatically register the virtual machine with the LiveVault backup service and initiate a backup of files and folders defined in the template. Alternatively, the virtual machines deployed from the CSA service design can be provisioned with the LiveVault agent and registered with LiveVault Service. With this solution the backup configuration is defined manually with the LiveVault Management Portal. 35

36 The two CSA Service Designs demonstrated in this document are provided as an example of how to automate the installation of the LiveVault agent and provision the computer to HP LiveVault Service. These service designs demonstrate how to configure the LiveVault agent with and without using LiveVault Server templates. Additionally, this document demonstrated how to use HP LiveVault using LiveVault Web Management Portal for managing computers that are provisioned to LiveVault service. This includes using the Web Management Interface to manage backup and restore processes from a single Web management interface from any location to perform operations for adding and managing user accounts, adding computers and appliances, creating backup and restore policies, creating and assign roles and groups. DISCLAIMER OF WARRANTY This document may contain the following HP or other software: XML, CLI statements, scripts, parameter files. These are provided as a courtesy, free of charge, AS-IS by Hewlett-Packard Company ( HP ). HP shall have no obligation to maintain or support this software. HP MAKES NO EXPRESS OR IMPLIED WARRANTY OF ANY KIND REGARDING THIS SOFTWARE INCLUDING ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE OR NON-INFRINGEMENT. HP SHALL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES, WHETHER BASED ON CONTRACT, TORT OR ANY OTHER LEGAL THEORY, IN CONNECTION WITH OR ARISING OUT OF THE FURNISHING, PERFORMANCE OR USE OF THIS SOFTWARE. Appendix A: Creating a CloudSystem Template with the HP SA Agent These instructions require that you have access to the RHEL 6.4 ISO image. 1. Create a base Red Hat Enterprise Linux 6.4 Virtual Machine from the VMware vsphere client. A. Configure RHEL as a Basic Server, using DHCP network and include two networks. B. Install RHEL 6.4. C. Install VMware Tools on the VM and reboot the VM. D. Obtain the IP address of the virtual machine. 2. Configure the RHEL VM network and security settings for eth0 and eth1. A. Set up ethx networking. Remove the HWADDR= line. Verify the setting onboot=yes The /etc/sysconfig/network-scripts/ifcfg-eth0 and ifcfg-eth1 files should be similar to: DEVICE="eth0" TYPE="Ethernet" ONBOOT="yes" NM_CONTROLLED="no" BOOTPROTO="dhcp" IPV6INIT="no" B. Disable SELinux in your VM template. Edit /etc/selinux/config. Change SELINUX=enforcing to SELINUX=disabled. C. Disable Firewall. D. Remove the /etc/udev/rules.d/70-persistent-net.rules file. E. Disable IPv6 by editing /etc/sysctl.conf and adding net.ipv6.conf.all.disable_ipv6 = 1 to the end of the file. 3. Cloud-Init Install the cloud-init RPM package, cloud-init el6.noarch.rpm. If this package and its dependencies as listed in Table 4 have been loaded into a local repository server, then cloud-init can be loaded with the yum command: yum install cloud-init If not, then all of the RPM packages will have to be installed with the rpm command: rpm ivh cloud-init el6.noarch.rpm Many of the RPM packages needed for cloud-init may already be installed in a repository that you can access, be part of the Red Hat Enterprise Linux OS media, or available to you from the Red Hat Network (RHN). If you do not have access to a repository, OS media, or RHN, then you can manually download the individual RPM packages from one of several sites, including: or 36

37 Table 4. Cloud-Init RPM packages Software Packages cloud-init el6.noarch.rpm libselinux-python el6.x86_64.rpm policycoreutils-python el6.x86_64.rpm python-argparse el6.noarch.rpm python-boto el6.noarch.rpm python-cheetah el6.x86_64.rpm python-configobj el6.noarch.rpm python-jsonpatch el6.noarch.rpm python-prettytable el6.noarch.rpm python-requests el6.noarch.rpm PyYAML el6.x86_64.rpm audit-libs-python el6.x86_64.rpm libsemanage-python el6.x86_64.rpm python-chardet el6.noarch.rpm python-jsonpointer el6.noarch.rpm python-markdown el6.noarch.rpm python-ordereddict el6.noarch.rpm python-pygments el6.noarch.rpm python-urllib el6.noarch.rpm setools-libs-python el6.x86_64.rpm crontabs el6.noarch.rpm libcgroup el6.x86_64.rpm libyaml el6.x86_64.rpm python-backports-ssl_match_hostname el6.noarch.rpm python-setuptools el6.noarch.rpm python-six el6.noarch.rpm setools-libs el6.x86_64.rpm cronie el6.x86_64.rpm python-backports el6.x86_64.rpm sendmail el6.x86_64.rpm cronie-anacron el6.x86_64.rpm hesiod el6.x86_64.rpm procmail el6.x86_64.rpm Configure the /etc/cloud/cloud.cfg file so that the cloud-user account will have sudo privileges as shown here: system_info: distro: rhel default_user: name: cloud-user sudo: ALL=(ALL) NOPASSWD:ALL paths: cloud_dir: /var/lib/cloud template_dir: /etc/cloud/templates ssh_svcname: sshd 4. The resolv.conf file is not properly set to resolve external name spaces in deployed OpenStack virtual machines. This is needed to be able to access the HP LiveVault service. Modify the /etc/rc.local file to overwrite resolv.conf to include your required name server. Set nameserver to point at your local DNS server. Below is an example used in the test environment. # cat /etc/rc.local. echo "search openstacklocal novalocal" > /etc/resolv.conf echo "nameserver " >> /etc/resolv.conf 37

38 5. Install the HP SA Agent on a virtual machine: The HP Cloud Service Automation Installation Guide details the procedure to prepare a VM template with the HP SA Agent already installed. A. Log in to HP Server Automation Java Client as an administrative user. Note: You can download the Server Automation Java client from the Server Automation web client accessible at Core IP address>. The link to download the Java client is on the login page. Click on Download Hewlett-Packard Launcher to install the application. The installer has an option to create a shortcut on your desktop. You don t need to log in to the web client. B. Make sure the VM is connected to the network and the HP Server Automation (HP SA) system can be reached. C. From Server Automation Java Client, choose the Devices tab, then Servers SA Agent Installation. D. In the dropdown box, select Explicit IPs/Hostnames. Enter the IP address of your virtual machine and click on the Scan button. Click OK on the Scan Completed prompt. E. Right-click on the discovered server and select Install SA Agent option. Enter the Username and password. Under Actions select Verify prerequisites, copy installer and install agent. F. Click on Start Job to copy the agent files to the VM. Click Close once the job is completed. G. Click on the All Managed Servers option to open the All Managed Servers window. H. Click on the View dropdown menu and select Properties. I. Click on the virtual machine on which the agent was installed. J. Record the Object ID of the virtual machine, which can be found in the Management Information section of the Properties panel. 6. Sanitize the SA Agent installed on the VM: A. In the HP Server Automation client, select the Library tab and then By Type. B. Expand the Extensions folder. C. Select Program. D. Locate the BRDC HP SA agent sanitizer. E. Execute the BRDC HP SA agent sanitizer APX: Right-click the APX and select Run. F. Select the Options tab in the Run Program Extensions dialog. G. In the Specify any needed parameters for this program execution field, enter the Object ID, which you previously obtained for the virtual server template. H. Click Start Job when the sanitation completes, click Close. I. Gracefully shut down the virtual machine (shutdown h now) after the job completes successfully. Note: Do not reboot this virtual machine. J. Convert the image to a VMware VM template. In the vsphere Client, right-click the VM and from the Template dropdown select Convert to Template. 7. Remove the server entry in SA. A. Go to Devices Servers All Managed Servers. B. Locate the server whose SA agent you just sanitized on step 6. C. Right-click on the server and select Deactivate SA Agent. D. Click the Deactivate confirm button. E. Right-click on the server again and select Remove from SA. F. Click the Remove from SA button. 8. Verify if the SA agent installs. A. Deploy a VM from the template. B. If the SA agent and changes were done correctly, the VM should automatically register its SA agent after boot up. C. You can verify it from the Devices tab of SA. Go to Servers All Managed Servers. On the toolbar, click View Refresh. It takes about 3 to 5 minutes after booting for the server to show up. If the server does not automatically register after 5 minutes, verify above steps 6 and 7. D. Once verified, delete the test VM and remove the device from SA. 38

39 9. In vsphere client, browse the datastore where the template resides. Go to the templates home directory, select the virtual disk file (.vmdk), right-click and select Download as shown in Figure 41. You can select a folder on the server running the vsphere client to download the files to. Figure 41. Datastore Browser 10. Upload the image to Glance Repository as shown in the section Uploading the image to Glance repository. Appendix B: Software packages and policies Software packages (ZIP files) are imported into HP Server Automation. Software policies are collections of software packages or other software policies. For this deployment we have just a ZIP file to be imported. Appendix B1: Software Policy to provision a computer to LiveVault Service This Software Policy will be used in creating HP LiveVault OpenStack Topology Service Design for adding and provisioning a computer to LiveVault Service. Importing the packages To import software into HP Server Automation, complete the following steps: 1. Create the AutomomyLiveVault file install bundle: A. Create the staging folder under c:\temp and place the files downloaded in the section Staging the required software package into their respective folders as specified in Table 2. B. Compress the folder containing the LiveVault agent file into a ZIP archive file as specified in Table 5. You can do this with programs like WinZip or 7-Zip on Windows, or using the zip command on a Linux system. Table 5. ZIP archives Zip Archive Folder and Files Post-Install Script AutonomyLV.zip C:\temp\AutonomyLV 7.80Build12759.tar.gz chmod -R 777 /tmp/autonomylv cd /tmp/autonomylv /bin/tar -xzvf 7.80Build12759.tar.gz LANG=en_US../install.sh -S -I /usr/livevault -D /usr/livevault cd /usr/livevault/bin./lvregister.sh -s -u <username> -p <password> -k <keypassword> -i -E -S /etc/init.d/lvbackup start reboot 2. Log in to HP Server Automation Java Client as an administrative user. 3. Select Library from the button on the bottom left. Click on the By Folder tab and Right-click on the Library folder then select Import Software. 39