WIXLIB

Step One – Initial application setupWhen you log into the Command Center for the first time, a wizard will guide you through theinitial application setup. After you complete this core setup, you can complete quick start setupspecific to the applications you protect (e.g. Hypervisors, Databases). See Completing the CoreSetup Wizard (Command Center) for more detail.Note: It is recommended to have a default backup library ready before commencing applicationsetup. You will need: A local drive (*attached to CommServe) -or- Network Attached Storage (NAS) share foryour backup data with no more than 15TB of client data to protect (Small environments). A dedicated local SSD drive (*attached to CommServe ) with 600GB free size for DDBand Index Cache (see Hardware Requirements )*during initial platform setup below, it is assumed that you only have one data mover orMediaAgent, which is the CommServe itself. As your platform scales the data movement functionwill normally reside on a separate server.Note: Initial setup will define a default server backup plan, this is used to protect yourCommvault infrastructure. You will configure your customer-facing backup plans separately.Performing initial Setup1.Click Let’s get started button2.Add storage by supplying the following information and clicking Save Name: SystemDefault (prefix is used to indicate system usage) MediaAgent: (select your CommServe)9

Type: Select Local or Network Backup location: select/create a folder to store data when it is backed up(e.g. G:\ SystemDefault) Deduplication DB location: select/create a folder to store the DeduplicationDatabase (e.g. F:\ SystemDefault-DDB)3. Create a default server backup plan by supplying the following information and clickingSave Plan name: Default (prefix is used to indicate system usage) Copies (backup copies that will be held)i. Primary SystemDefault 1 Months retention RPO - Runs every 1 Days Start time – 09:00 PMNote: This is a default server backup plan used to protect your Commvault infrastructure. You willconfigure your customer-facing backup plans separatelyYou have now finished initial setup – click Dashboard (left) to view your configured CommCell.Get notified of critical eventsAt a minimum, the platform administrator should be notified of any critical events requiringattention. To provide email server information for Commvault alert delivery, perform the following:1.Click Guided setup menu (left-pane)2.Click Configure email quick task (right)3. Supply your company SMTP server, port and authentication details(if required in your organization)4. Click Test email and confirm you receive the test email (see status in top of window)5. Click SaveCommvault will notify the administrator of critical and anomalous events by default.(Alerts and Notifications – Predefined Alerts )Alternatively, you can forward alerts from the Commvault system to your centralized EventManagement system using SYSLOG or SNMP .Downloading the latest softwareWhile you perform further setup, the Commvault system can download the latest software ontoyour CommServe, from your Guided setup page:1.Click Download/copy software2.Leave default as ‘Download software using – Internet’3. Leave default as ‘Latest hotfixes for the service pack’4. If you have Linux systems to protect, add Unix – Linux X86 64 to your download5. Click the Download button10

The latest software will be useful if you have a need to push application agents to clients to beprotected. This is covered below in Installing Application Agents on Clients (optional).Running your first DR backupWhile the software downloads, let’s run your first Disaster Recovery backup.1.Type Disaster into the top-bar search box, click Manage System Maintenance2.Click the DR backup (Daily) tile3. Click the icon to perform a DR backup to default location C:\DR4. Select Full (default) and Enable database backup compression (default) and click Run job5. Click view job details to monitor backup progress real-time -orType Jobs in left-pane search and select Jobs menu.Configure offsite DR backupsWhen the initial DR backup is complete, it is recommended to navigate back to Manage System Maintenance DR backup (Daily) and click theicon to configure at least one ofthe following: A network share location for the Backup metadata destination Upload backup metadata to Commvault Cloud (recommended) Upload backup metadata to a Cloud library (recommended)Commvault will retain one (1) database copy for FREE in Commvault controlled cloud (Azure).Commvault recommends configuring a Cloud library for retention of at least fourteen (14) days,this allows recovery from an event that may go unnoticed for a period of 1-2 weeks.Step Two – Configuring your Service CatalogThe next step in configuring your multi-tenanted Backup as a Service (BaaS) platform isconfiguring your Service Catalog. Commvault implements your Service Catalog as Plans. A Plandefines what to protect, how often and where to keep backup copies.The table below summarizes the Commvault recommended Data Center Backup as a Service(BaaS) plans for Essential, Standard, and Premium. Essential is the most basic offering withfeatures and monthly cost increasing with each service level.PlansService PlanPrimary copy, RetentionSecondary copyRPOEssentialPrimary-Site1, 15 days-24 HoursStandardPrimary-Site1, 30 days-24 HoursPremiumPrimary-Site1, 15 daysSecondary-Site1, 30 days8 Hours11

Premium-OffsitePrimary-Site1, 15 daysSecondary-Site1 30 days8 HoursStandard-OffsitePrimary-Site1, 30 daysSecondary-Site1, 30 days24 HoursThese Service Plans will be sufficient for protecting your Virtual Machine, Server and Applicationworkloads both on-premises and at remote sites (co-location facilities). Long Term Retentionoptions have been excluded from initial setup.Adding your StorageBefore your service plans can be created, you will need your storage locations provisioned andavailable to Commvault. You will require a Primary storage location in the same data center asthe protected workloads, and another at a Secondary or remote location.These storage locations may be – Cloud , disk , or tape.Adding Disk Storage1.Navigate to Storage Disk menu2.Click Add (right)3. Enter a Name (i.e. Primary-Site1)4. Select the CommServe as the MediaAgent5. Select a Type (Local or Network)6. Provide a Backup Location7.Provide a Deduplication DB location8. Click SaveAdding Cloud Storage1.Navigate to Storage Cloud menu2.Click Add (right)3. Enter a Name (i.e. Secondary-Site1)4. Select a Type (i.e. S3 Compatible Storage)5. Select the CommServe as the MediaAgent6. Enter S3 endpoint hostname/address7.Enter Bucket name to store backup data in8. Provide Credentials9. Provide a Deduplication DB location10. Click SaveCommvault recommends leveraging disk-based libraries for all your data-center BaaS backupcopies and cloud (or tape) libraries for long-term retention or archival data only.Follow the links above for the process to add your Disk and/or Cloud Storage.NOTE: Each Storage location will require an ideally dedicated SSD drive to locate theDeduplication DataBase (DDB) and Index cache data on. The size of the SSD drive is dependent12

on the amount of client data being sent to the Storage Pools, see Hardware Specifications forDeduplication Mode .In the example above, there is a Primary-Site1 disk backup stored locally and a Secondary-Site1cloud copy created for offsite / Disaster Recovery retention.You may now proceed to Plan creation (below).Adding your PlansYou may now configure your Service Plans by performing the following:1.Navigate to Manage Plans2.Click Create plan (right) Server backup3. Supply the Plan name (see table below)4. Click Add to add backup destination copies as required by service (see table below)a.You will need to perform an Add for both your Primary and Secondary copy.5. Set the RPO – Backup Frequency6. Click Save buttonRepeat for each Service Plan detailed (below). Other options may be left as default.Tip: Using a numeric prefix to each plan enables tracking of your services eriodSecondaryCopy1 EssentialPrimaryPrimary-Site11 Months--1 Days2 StandardPrimaryPrimary-Site11 Months--1 DaysSecondaryLocationRetentionRPOPeriod13

3 PremiumPrimaryPrimary-Site115 DaysSecondarySecondarySite11 Months8 Hours4 Standard( Offsite)PrimaryPrimary-Site11 MonthsSecondarySecondarySite11 Months1 Days5 Premium( LTR 1y)1PrimaryPrimary-Site115 DaysSecondarySecondarySite11 Months8 Hours5 Premium( LTR 7y)2PrimaryPrimary-Site115 DaysSecondarySecondarySite11 Months8 Hours1Secondary copy - Extended retention rule: Monthly Fulls, retained for 12 months2Secondary copy - Extended retention rule: Yearly Fulls, retained for 7 yearsExtended retention is configured by enabling the Extended retention rules for a backupdestination and selecting the required backup Type and Retention period (see below)See Plans for more details, including Setting Default Plans for new infrastructure.14

Step Three - Adding your HypervisorNow that you have finished the core setup it’s time to setup for Infrastructure as a Service (IaaS)platform for protection. The following stepswill enable the Virtualization solution andadd your Hypervisor hosts for protection.Note: In this setup, you will be offering FullyManaged Infrastructure, you (the MSP) areresponsible for the virtual machine OperatingSystem (OS) and hosted applications.Restore requests are expected to occur viarequests to your Service Desk, with someself-service options available.To add your Hypervisor for protection:1.Click Guided Setup (left-pane)2.Click Virtualization3. Select vendor either VMware vCenter or Microsoft Hyper-V and supply thefollowing information and click Save Server name (of hypervisor access point) Hypervisor display name (i.e. MSP.IO – Fully Managed Infrastructure) Username (of hypervisor administrator) Password (of suitable administrator account on hypervisor) Access nodes (this is CommServe for initial setup)4. Provide a VM group Name (i.e. Essential VMs) and matching Plan (i.e. 1 Essential), andclick Finish buttona.Select the specific VMs you would like to be protected on this plan(if you have VMs already provisioned)A backup will be started automatically for selected VMs, you will be redirected to the Active jobsmonitor to view the progress. Only the first VM group creation will trigger a backup.TIP: It is recommended that Infrastructure within your Hypervisor platform are grouped (byResource Group, VM Folder) or tagged to identify customer service plan (see below for VMwarevCenter tagging example).If tags or grouping are utilized, Commvault can auto-discover new Virtual Machines and protectthem with appropriate service plan. Where tags are not available, Commvault has a broadselection of metadata to map hosts to a service plan (see Add rule options above).A backup will be initiated immediately after creation of the VM group.15

While the backup is running, navigate to Protect Virtualization VM groups and create the aVM group for each service level (see below)NamePlanEssential VMs1 EssentialStandard VMs2 StandardPremium VMs3 PremiumStandard VMs (with Offsite)4 Standard ( Offsite)Premium VMs (with 1-year LTR)5 Premium ( LTR 1y)1Premium VMs (with 7-year LTR)5 Premium ( LTR 7y)2NOTE: Adding a VM Group via the Protection Virtualization menu will not initiate a backup forevery group. It is recommended a first backup is run for each VM Group once configured.Setting backup typeAfter your first backup is complete, consider reviewing the backup type configured in your VMGroups. You should now create additional VM groups for each serviceConsider a staggered approach: Essential plans receive crash consistent protection only. Standard plans receive file-system application consistent protection Premium plans receive application aware protection (needs service account on host)To configure the backup type:1.Navigate to Protect Virtualization Hypervisors VM Group Configuration TAB2.Click Edit in the Settings tile3. Choose the appropriate backup typeWARNING: Customer self-service new VM restore capability is not available for Fully Managedinfrastructure, full VM recovery to an alternate host will require a Service Desk request.Best PracticesIf utilizing storage array snapshot technology, it is recommended to place Virtual Machine (VMs)in dedicated datastores or volumes aligned to their service level.The reason for consolidating hosts on common service plans is that a storage array snapshot willcapture ALL VMs in each datastore. Co-locating all VMs with common service levels will reducethe size and overall footprint of the storage snapshot.16

Step Four – Onboarding your first tenantCommvault utilizes a virtual construct called ‘Companies’ to represent a tenant within the sharedCommvault platform. To onboard a new tenant for Backup as a Service (BaaS) you will create a‘Company’ with an associated administrator and users.Creating a companyTo onboard your first tenant, perform the following:1.Navigate to Manage Companies menu2.Click Add company (right)3. Enter the following details and click Save Company name Email (of the tenant administrator) Contact name (of the tenant administrator) Plans (select all service plans tenant can use) Company alias enter a short alias for the tenant Associated SMTP enter the email domain fortenant Send welcome email toggle, leave enabled(default) Ensure Auto discover applications is disabled(default)Application auto-discovery: Auto discover applications will run a scan on all systems within thetenant every twenty-four (24) hours. If a supported application is identified, its Commvaultsoftware agent will be pushed installed on the host. This feature should be disabled, as onlyPremium customers receive application-agent based protection.Tenants are emailed a welcome email and one-time password setup link – if welcome email isenabled. If you will be configuring Single Sign On (SSO) authentication for your tenants, it isrecommended to disable Send welcome email, as the users will use a previously suppliedpassword.You can customize the email template to customize branding and welcome information perCompany – see Adding an Email Template .Enabling tenant solutionsWhen your tenant admin logs into Command Center, they will be prompted to enable protectionfor one or many solutions. Customize which solutions will be displayed, as follows:1.Click the Company name2.Click Edit on Supported solutions General setting3. Enable File server, Virtualization and Databases17

Tailoring the user experienceIn our BaaS solution, you will offer Virtual Machine, File-server and Database backup only. Performthe following to disable the user interface options associated with other data types:1.Navigate to Manage Customization2.Click the Navigation tile, under Navigation preferences3. Uncheck the following menu items that are not required for your Fully Managed IaaSBaaS service, for the Tenant admin, Tenant user, Restricted user columns:a.Guided setupb. Protect – Virtualization – Hypervisors VM Groups, Laptops, Applications (all)c.Activated. Orchestratee.Manage – Plans, Regionsf.Networkg.Web console – My datah.My Apps4. Click the initial landing tab, select Company dashboard for the Tenant admin5. Select Virtual machines for the Tenant user.6. Select Company dashboard for Restricted user7.Click Save, click Yes to confirm save.Note: Be aware these changes affect all tenants that are consuming your service. If you would liketo make changes specific to a Company, use the Navigation preferences tile in the individualcompany.Activating an authcode for client installationCommvault recommends activating Authorization Code(s) or authcode for client registrationfor each tenant. Please see Enabling Authorization Code for a Company to complete this task.Simply toggle the Requires authcode for installation within the Company General settings.Creating a tenant userIn order to validate you company setup, it is useful to have a default company user, to test theuser experience. To create a new local user for your initial tenant:1.Type Users in top-bar search box, choose Manage Security Users shortcut2.Drop-down the Companies list and choose the Company.3. Click Add user (right)4. Leave User Type as Local user5. Enter a Full name, Username, Email6. Select company \Tenant Users as the User Group7.Enter a Password8. Click Save18

You can test this user now – Logout, Login as the new user.Your user will be logged into Protect Virtualization Virtual machines, no infrastructure will belisted as the user has not been assigned self-service privileges.Creating a custom roleIn order to restrict your users and administrators to only perform in-place recovery, you will needto create a custom role. Restricting tenants from out-of-place recovery is important to ensureyou tenants can’t provision new Virtual Machines (VMs) via restore – as this could directly affecttheir monthly invoice.To create the custom role:1.Type Roles in the top-bar search box, choose Manage Security Roles shortcut2.Click Add role (top-right)3. Type VM Owner in the Name field4. Check the Visible to all checkbox5. Select the following permissions and click Savea.Client – Agent Schedulingb. Client – Data Protection/Management Operationsc.Client – Browsed. Client – In Place Recovere.Client – Out-of-Place Recoverf.Client – In Place Full Machine RecoveryOnboarding a Virtual Machine to a tenantNow that you have one or many Companies (i.e. tenants) configured, you can assign protectedVirtual Machines to the appropriate tenant.1.Login as admin to Command Center.2.Click Dashboard (left-pane)3. Click VMs4. Click the Name of the Virtual Machine you want to assign5. Click the Configuration tab6. Click Edit in the Security tile7.Select the Associations tab anda.Assign tenant \Tenant Users group as an VM Owner .8. Select the Owners tab anda.Assign tenant \ Tenant Admins group.Note: There is no method to automatically assign VM owners or permissions. It is the duty of theMSP to perform this action after initial successful b

Virtual Server Agent (VSA): The Virtual Server Agent is a software module that is installed on a computer to protect a specific type of data (i.e. A Hypervisor). . This small bootstrap installer will be used to quickly download the latest Commvault software onto your server (sizing details for your server are included in this guide below).