Managed Private Backup

Equinix Managed Private Backup (MPB) provides a centralized service for global data protection. MPB allows you to abstract hardware and software investments and remove the need for hardware lifecycle management and complex daily operations. MPB is ordered based on the amount of data you need protected (measured in terabytes). MPB helps you keep costs under control with a baseline commitment and allows you to backup volumes above your committed baseline if needed (overage charges applies).

MPB offers:

• A scalable and secure backup platform, enabling businesses to protect their data globally without needing to invest in hardware and software or spend time on lifecycle management and complex maintenance operations.

• Self-service capabilities to select data for protection or restoration.

• Controlled costs with a baseline commitment based on protected data volume. Exceed the baseline if needed (subject to overage charges) without service interruption.

• API access to the Commvault Command Center (REST), supporting alert management, report administration, and install/upgrade operations.

• Frequent database transaction log backups (every 4 hours), enabling a recovery point objective (RPO) of up to four hours for supported databases.

Main Features

• 99.95% SLA platform installed in high availability architecture to avoid service disruptions
• Ransomware protection with immutability settings
• Self-service operational console provided for configuration and management
• Direct connectivity with access anywhere via Equinix Fabric

Concepts

Customer Portal and Managed Solutions Portal

The Customer Portal provides access to the Operational Console and the Managed Solutions Portal (MSP), where users can raise tickets, submit service requests, and view insights on MPB service usage.

The Operational Console lets you manage your MPB environment. It provides access to MPB in specific regions. MPB supports four regions: South America, North America, Europe and Asia. If you have an MPB in a specific region, you can access its Operational Console by selecting the corresponding button on the page.

Organization

An Organization (Org) defines the customer within the Operational Console. The Org can be viewed as a container that groups together all MPB resources like backup volumes and retention settings located within an MPB region. The name of the Org is needed when logging into the MPB Operational Console. Use the Org name when this guide mentions <organization name>.

When Equinix performs the initial deployment for a new MPB customer, the first user that is configured is the customer administrator account. This account is created by Equinix during the onboarding process and is based on the name and email provided by the customer.

The first customer administrator account added is automatically added to the Tenant Admin group. Being a member of this group assigns the account all the permissions in the Operational Console.

Tenant Admin — Permissions

• Access MPB Console
• Create backup routines
• Perform on‑demand backups
• Run restores
• Run Reports
• Monitor Alerts, events and Threats
• Create Tags
• Download and install backup agents

Onboarding

During the MPB onboarding process, you receive the following information:

• Organization name
• One or more customer accounts with one of the above roles assigned
• The ordered volume of resources that are provisioned by region and by retention rules
• Authentication Code for performing installations

User Management and SSO

Users of the Operational Console are managed at the Customer Portal. See User and Password management. Once users have been added, customers can raise a Service Request to assign an MPB Tenant role to the new user.

The Operational Console

When logged into the Customer Portal you navigate to the product page via Managed Solutions Portal → Services → Managed Private Cloud; from here you can login to the Operational Console in the region of your choice. When you access directly via the Operational Console URL and click Sign In, you will be redirected to the Customer Portal where you can enter your Customer Portal credentials. In the Customer Portal you can configure federation to your own identity provider so you can use your company credentials to login to the Operational Console (SAML-based federation).

The MPB Operational Console provides:

• Start dashboard: Overview of how many servers/VMs are being protected and the status of recent backup jobs.
• Protect: Map servers or instances to be protected.
  • Virtualization: Map VMs/instances for image‑level backup.
  • File Servers: Map servers for agent‑level backups.
  • Databases: Map database instances for specific database agents.
• Jobs: Active jobs, history, scheduling.
• Reports: Information generated by Commvault about reliability and effectiveness of the backup solution.
  • Note: SLA shown in Commvault reports is not the MPB service SLA.
• Monitoring:
  • Events: technical logs that can assist troubleshooting.
  • Unusual file activities: indicators of atypical behaviors possibly associated with threats. This does not replace antivirus/security software.
• Download Center: agent packages for supported workloads.

Connecting with the MPB

You need to subscribe to MPB for each location (IBX) where you need to protect data. For example, if you have ordered Managed Private Cloud in Chicago (CH3) IBX, you will need to order MPB in CH3 to protect data that resides there. This supports governance requirements such as data sovereignty*.

Image‑level Protection

Image‑level protection allows MPB to connect at the hypervisor layer of Managed Private Cloud or a hypervisor (currently VMware and Hyper‑V, with other technologies in the future) and execute snapshot backups. This allows quicker restores of complete virtual machines for Disaster Recovery purposes. If you are an MPC customer, all connectivity needed for image‑level protection has already been deployed by Equinix.

Agent‑level Protection

Some workloads have specific agents for more granular protection and restore.

Available agent‑level protection on MPB:

• File server agents (Windows, Linux and AIX): select folders/files for granular backup/restore.
• Database agents: Microsoft SQL Server, Oracle, MySQL, PostgreSQL, IBM DB2.

Ports used by MPB

Specific TCP ports should be open from each target (server) to the MPB Service:

• TCP 443 (from customer to backup infrastructure — use the endpoint provided during fulfillment)
• TCP 8400 to 8499 (bi‑directional)
• Fabric connection for colocation customers

Authenticate / log in to MPB

Use the same credentials as the Customer Portal. If someone does not have access, request access via your primary Equinix contact. Do not share personal credentials. This violates the Acceptable Use Code and creates security risks. To find the current Operational Console URL address, use the product page inside the Managed Services Portal. Bookmarking older URLs may cause access issues if the URL changes.

Giving someone else access to the Operational Console

Request Customer Portal access for the user, then open a ticket to assign the appropriate MPB permissions. Use the service catalog option Create user in Operational Console.

Configure image‑level protection for MPC

Connectivity required to protect MPC at image‑level should already be in place. You will see Virtual Machine Groups on the VM Groups tab. VM Groups have specific backup policies (e.g., 30 days retention without offsite).

Configure image‑level protection for Colocation (on‑premises) — VMware and Nutanix

Install a VSA Commvault (version 11.36)

• Download the .ova from Download Center in MPB Console and deploy in vCenter.
• Deploy OVF Template → select files → choose VM name/location.
• Select compute resource and size per backend TB.
• Select storage (thin provisioning).
• Configure networking for MPB assets and vCenter; set disks size, gateway IP, client name; IP address, netmask, gateway, DNS; leave username blank (use AuthCode).
• Set root password; leave password blank to use AuthCode.
• After installation, login to the proxy server and edit the hosts file to configure name entries (addresses provided during onboarding).

Deploy VMware vCenter Hypervisor Agent

• In MPB Console, Protect → Virtualization → Add Hypervisor → VMware vCenter.
• Provide vCenter FQDN reachable by VSA proxy, display name, admin credentials, and Access Node(s) (the VSA proxy from 5.5.1).
• Create a VM Group (by rule or content) and Plan (retention).
• Review summary and finish.

Deploy Nutanix AHV Hypervisor Agent

• In MPB Console, Protect → Virtualization → Add Hypervisor → Nutanix AHV.
• Provide Prism Central IP reachable by VSA proxy, display name, admin credentials, and Access Node(s) (VSA proxy).
• Create a VM Group (by rule or content) and Plan.
• Review summary and finish.

Deploy agent‑level backups

Add naming entries manually: On each server/VM, configure name entries (addresses provided during onboarding):

• Windows: add entry in hosts file.
• GNU/Linux/AIX: add entry in /etc/hosts.

Package download: Download required packages from Download Center in MPB Console and install on target servers. Database packages are included in OS‑specific packages (e.g., Oracle on RHEL → Linux package). For MPC VMs, you may mount the installation ISO from the VCD content hub.

Agent installation steps:

Windows (File System or MS‑SQL Server agents)

• Run the .exe, extract, choose language, accept license.
• Install packages on this computer → Advanced selection → choose components:
  • File System Core + File System (file system backups)
  • VSS Provider + VSS Hardware Provider + Virtual Server (VSA Proxy or Hyper‑V)
  • MS‑SQL Server (databases)
• Choose install path (default C:\Program Files\Commvault\ContentStore).
• Select Client Name (displayed in MPB Console) and IP interface (Host Name).
• Enter Network Gateway Proxy Address (as configured in naming entries).
• When prompted, enter AuthCode provided during onboarding.
• Optionally select protection plan.

GNU/Linux/AIX

• Extract .tar, run ./cvpkgadd.
• Install packages on this machine → Advanced Selection:
  • File System Core + File System
  • Virtual Server (VSA Proxy or Kubernetes)
  • Oracle, Oracle RAC, SAP for Oracle, MySQL, DB2, PostgreSQL (databases)
• Do not install “restore‑only” agents.
• Install path (default /opt), log directory (default /var/log).
• Unix group assignment as needed (recommended for DB agents).
• Enter the agent IP address.
• Specify Client Display name (shown in MPB Console).
• Enter MPB Network Gateway (from onboarding) and do not check “CommServe will connect to this computer to finish registration.”
• HTTP proxy: No.
• Enter AuthCode (leave username/password blank).

MySQL Agent steps:

• After installation, in MPB Console → Protect → Databases.
• Select Database → Overview → edit and set Binary Directory, Log Directory, Configuration File.

IBM DB2 Agent steps:

Clustered DB2:

• Use shared directories for Archive, Retrieve, Audit error paths.
• Set DB2 input path.

Standalone DB2:

• Do not use shared directories; set Archive, Audit Error, Retrieve directories.

• In MPB Console → Protect → Databases:

  • In Overview, add admin user (SYSADM/SYSCTRL/SYSMAINT and DBADM), assign Plan, set DB Home.
  • In Databases tab, configure target database.
  • Configure Subclient content and backup type (online/offline).

Online DB2 backup — server steps:

• Run script (as DB2 instance user; user must be in Commvault Unix group) to set:

  • LOGARCHMETH1, LOGARCHOPT1, VENDOROPT
    Example:
    /opt/commvault/Base/Db2_config.sh -d <database_name> -i <Commvault_instance>

• Before starting online backup, perform one offline backup.

PostgreSQL Agent steps:

• In MPB Console → Protect → Databases → Instances.
• In Overview, set:
  • Server Plan
  • Connection details: DB user/password, Unix username, maintenance DB, port
  • DB Home
• Set Binary directory, Library directory, Archive log directory.
• Choose DumpBasedBackupSet or FSBasedBackupSet. For FS‑based, verify archiving works.
• In Database Groups, select plan and run backup.
• If pg_hba.conf uses peer, adjust authentication (e.g., md5 for password prompts).

Oracle RAC Agent steps:

• Install Oracle Agent on all RAC nodes using steps in 5.6.3.
• In MPB Console → Protect → Databases → Add Instance → Database Server → Oracle RAC:
  • Enter RAC Cluster Name, Database Name, Plan, RAC database instances.
• Check instance status.
• In Subclient views, configure backups. Create a separate subclient for archive logs if you need a different RPO than 24 hours, and assign the desired plan.

Active Directory Agent steps:

• Install agent (Windows) selecting Application Package → Active Directory.
• In MPB Console → Protect → Active Directory → Apps → Active Directory server → Settings:
  • Configure a domain user with backup/restore permissions.

note

• Agent installation requires administrator privileges (Domain Administrator group).
• Backup user must be a domain user (default read). DNS Zones are not backed up with a normal domain user.
• Restore user requires Read, Change, and Create Child Objects (Domain Admins, Enterprise Admins, or Administrators group typically suffice).
• To back up LAPS password attribute ms-Mcs-AdmPwd, backup user must be a Domain Admins member.

Kubernetes Agent steps:

• Install Virtual Server Package agent on all Access Nodes required by Kubernetes.
• In Command Center: Protect → Kubernetes → Clusters → Add Cluster:
  • Select Access Nodes
  • Select Plan
  • Provide Kubernetes API Server, display name, Authentication Type = Service Account, Service Account, Service Token
  • Optional: enable etcd database backup
• Create an Application Group with content/rules and add Kubernetes applications.
• Review and complete the backup.

Add paths to the agent backup policy

• In MPB Console → Protect → File Servers → select the file server.
• Go to Subclients; use default subclient or create new.
• Set Plan and Content.
• Click Add to browse/select or manually enter paths; define exclusions if needed; save.

note

Subclients organize backup content (e.g., C:, D:, Managers, Analysts). At least one subclient is required (default can be renamed).

Include targets on the VM backup policy

• Go to Virtualization → Hypervisor (MPC, VMware, Hyper‑V).
• Explore and select VMs to protect.
• Use Add rule to auto‑protect VMs or Content to manually specify targets.

Check if the backup job finished successfully

• Go to Jobs → Job history.
• Use Failed in last 24 hours for a focused view.

Troubleshoot failed backup jobs

• In Jobs, open job log from Actions.
• Use Job details for an overall view, targets protected, and MPB attempts.
• If failures are due to MPB platform reasons, raise a ticket.

Check how much data has been protected from one specific server/instance

• Check the Application size column in the server/instance view.
• For global usage reporting, open a request ticket (new report coming).

Run backup on demand

• Find the server/VM in Protect.
• Open the server page → click Backup (top-right).
• Select backup type → Submit.

Run restore on demand

• On the server/VM page, select desired date → pick available restore point → Restore.
• Choose Guest files or Full virtual machine.

Guest files:

• Presents a list of files; select destination and Submit.
• If Guest Files fails, select an alternative restore method.
• Requires connectivity and a File System Agent on the destination for best results.

Guest Files limitations:

• Image Level on Unix i_DataAgent can perform file-level restore only when the OS and version on client and MediaAgent are the same. Different OS/versions → job may pend.
• On Windows MediaAgent, Index Cache must be on NTFS.
• If metadata was not collected (e.g., Skip Metafile Creation), file-level restore cannot be performed.
• Do not restore hidden objects, system files, recycler files.
• Image Browse is not supported; no-image browse returns newest version since last full backup. For point‑in‑time file restore, browse back to that date.
• If disk cluster size (allocation unit) was < 1024 bytes, file-level restore may fail.

Full Virtual Machine restore:

• Select In place (overwrite) or Out of place (new VM).
• Set new name (optional), destination host/datastore, options → review → Submit.

Service Description

Managed Private Backup currently has one service variant, MPB Flex. The Flex service variant grants access to a standard platform managed by Equinix, with daily backup jobs executed at pre-scheduled times (outside business hours).

All the features below are covered by this option:

• Access to operational console
• Self-service features that allow for resource allocation, assigning backup policies, and execution of on-demand backups and restores
• Protection for physical servers and virtual machines
• Protection for databases
• Access to the MPB product page, including online documentation
• Backup platform managed by Equinix

Product Information

Protected Resources

Protected Resources are measured by:

• Volume (when protecting file system, database and image-level targets). Measured by frontend terabytes.
• Retention period
• Onsite versus Offsite protection

Retention and offsite protection option combinations

There are multiple combinations of retention and offsite protection options for each protected resource. Once ordered, this policy will be available for use on the operational console. Retention options define how long backup data will be stored at the source IBX (location), while Offsite options define for how long backup data will be stored at an alternative IBX (location). The following combinations are available to be ordered on Flex:

Local Retention	Offsite Protection	Job Details
30 days	Without	One backup per day (first one is full, then incremental for six days)
30 days	30 days	One backup per day (first one is full, then incremental for six days)
30 days	1 year	One backup per day (first one is full, then incremental for six days)
30 days	3 years	One backup per day (first one is full, then incremental for six days)
30 days	5 years	One backup per day (first one is full, then incremental for six days)
30 days	7 years	One backup per day (first one is full, then incremental for six days)
1 year	Without	All backups of the current month + last full backup from past 12 months
1 year	1 year	All backups of the current month + last full backup from past 12 months
3 years	Without	All backups of the current month + last full backup from past 12 months + last full backup from past 3 years
3 years	3 years	All backups of the current month + last full backup from past 12 months + last full backup from past 3 years
5 years	Without	All backups of the current month + last full backup from past 12 months + last full backup from past 5 years
5 years	5 years	All backups of the current month + last full backup from past 12 months + last full backup from past 5 years
7 years	Without	All backups of the current month + last full backup from past 12 months + last full backup from past 7 years
7 years	7 years	All backups of the current month + last full backup from past 12 months + last full backup from past 7 years
10 years	Without	All backups of the current month + last full backup from past 12 months + last full backup from past 10 years
10 years	10 years	All backups of the current month + last full backup from past 12 months + last full backup from past 10 years

Database Log Files

This service includes frequent transaction log backups taken every four hours. This enables a Recovery Point Objective (RPO) of up to four hours.

API Access

This service allows API access to the Commvault Command Center which enables users to create a new user from the REST API request. API commands include tasks related to Alert Management, Report Management and Install/Upgrade packages.

Service Demarcation and Enabling Services

With MPB, Equinix offers a backup as a Service where Equinix provides and manages a platform (operational console, backup servers and storage components). Equinix provides the licensing and support for the MPB platform. Equinix is not responsible for any client software or Internet connectivity to either manage or use the Service.

MPB is set with the default backup job scheduling to run on the IBX time zone. So, if MPB is ordered in two different IBXs located in different time zones, each job's start time will differ.

The customer is responsible to define which data should be protected by each backup policy and for installing the backup agents, discovering instances, and assigning backup policies to them. The customer is also responsible for identifying and correcting failed backup jobs, except when an MPB service/component unavailability causes the failure. The compute and network resources to allow backups to run are the responsibility of the customer. As a guide, instances should have at least 10% of free processing time and memory capacity plus 1 GB of free disk space to allow regular backup operation during backup window.

Limitations

• MPB is available in combination with Managed Private Cloud and for customer workloads that are colocated within an Equinix IBX. It acts as the protection component in this solution.

• MPB offers immutability protection by default in the Offsite Protection location. If Offsite Protection is not ordered, this feature will not be included.

• The baseline volume can be exceeded by 25%, but will incur overage charges (e.g., 10 TB ordered in baseline, 12.5 TB in use). After reaching this limit, the service may be disrupted until the baseline volume is increased through a Service Order change.

• Data can only be protected at the IBX location where the MPB service has been ordered.

• MPB supports the following operating systems, databases, and virtualization technologies. Support is limited to current and previous versions still supported by the original vendors in their regular lifecycle (extended support does not apply).

Supported Agents

Operating Systems

• Microsoft — Windows Server
• Red Hat — Enterprise Linux
• SUSE — Linux Enterprise Server
• Ubuntu — Server
• Debian — Stable
• CentOS — Stream

Hypervisors

• VMware — vSphere
• VMware — vCloud Director
• Microsoft — Hyper‑V
• Nutanix — Acropolis

Additional Agents

• Microsoft — SQL Server
• MySQL — Database
• Oracle — Database
• Microsoft — Active Directory
• Open Source — Kubernetes
• SAP — SAP Oracle

When vendors launch new versions, the backup technology vendor and the MPB service may take some time to support them. Due to technology restrictions in virtualized environments, MPB cannot protect instances with a vHBA device using image-level backup (only agent-level backups are allowed).

Purchase Units

The MPB Service is charged based on Baseline values or Baseline with Overage charge types.

Charge types

• Baseline — the specific volume of Unit of Measure of the Service as defined in the Order.
• Overage — the quantity of the Service consumed by Customer that exceeds the contracted Baseline Volume.

When ordering the MPB service, choose the variant that best suits the requirements. MPB is billed per Frontend terabyte protected. This configuration will allow protection up to baseline ordered. If the frontend data grows above the committed amount, the backup will not be disrupted. Instead, an overage charge will be generated based on the overage price defined on the quote.

These are the Units of Measure (UoM) for each variant available and the applicable fees:

Protected Resource	UoM	Installation Fee	NRC	MRC	Overage
Volume	TB	No	No	Yes	Yes

Calculation of Overage values

When the frontend TB protection ordered is exceeded, an overage charge will be generated based on the overage price defined on the quote. For example, the customer ordered 100 TB of Frontend data protection. Here is a measure of how much data is protected on a daily basis (measured by the biggest backup size of each day in the month):

Day of the month	1	2	3	4	5	6	…	29	30
Usage	70 TB	75 TB	85 TB	105 TB	110 TB	90 TB	…	98 TB	98 TB

During the period (month), the biggest full backup size was 110 TB, and since there is a baseline ordered of 100 TB, billing will generate a 10 TB overage charge for this period.

Roles and Responsibilities

Once the MPB order arrives for the Equinix fulfilment team, some tasks will be executed.

Activities	Equinix	Customer
Schedule / execute project kickoff meeting	RA	CI
Schedule / execute customer onboarding	RA	CI
Buy/Setup connectivity solution between MPB and customer protection targets	CI	RA
Check for connectivity requirements between MPB and protection targets	RA	CI
Customer tenant enablement on MPB infrastructure	RA	I
Make backup policies ordered available to customer	RA	I
Guide customer on shadow session in how to deploy backup agents	RA	CI
Insert environment credentials to allow backup agent deployment	-	RA

Once onboarding activities have been finished, testing activities will confirm if the product was delivered successfully and it is ready to be billed.

Activities	Equinix	Customer
Test access to MPB Product page on Managed Solutions Portal	CI	RA
Test access to MPB documentation on docs.equinix.com	CI	RA
Test access to MPB operational console	CI	RA
Test one backup job finish for each protection target	RA	CI
Confirm MPB fulfillment based on preview evidence	CI	RA
Set product as enabled for customer on internal systems	RA	I

Once the MPB service is enabled to customers, some operational items will be addressed.

Activities	Equinix	Customer
Install backup agents and keep protections targets mapped		RA
Start and manage any restore activity		RA
Check and troubleshoot backup/restore jobs failing	CI	RA
Meet product availability SLA	RA	I
Troubleshoot MPB platform issues	RA	I
MPB infrastructure monitoring and maintenance	RA	I

Service Requests

Service Requests are used to report an issue with the service or when there is a need to implement or assist with the implementation of a change. Customers can raise a Service Request for configuration changes that cannot be implemented through Self Service in the Operational Console, or if they require assistance with implementation of changes via the Operational Console. Round-the-clock support for the MPB Service is available, including these two types of service requests:

• Included: Service Requests which are in scope of the Service, and as such, no additional charges apply.
• Additional: Service Requests which are out of scope of the Service, and therefore additional charges apply.

Guidance is available for all Service Requests that can be completed through self-service, including procedural instructions and oversight of the customer’s task execution.

Type of Change	Self‑Service	Type
Investigate and resolve issue	No	Included
Ask information about the product	No	Included
Guided Assistance – To install backup agents	Yes	Additional
Guided Assistance – Manual backup operation	Yes	Additional
Guided Assistance – To restore protected data	Yes	Additional

Customers can select changes which are not listed in the table above by selecting “Change” at the service request module in the Managed Solutions Portal. Equinix will perform an impact analysis to determine whether the change can be implemented, to determine associated costs and lead time.

Any charges related to Service Requests will be deducted from the Premier Support Plan Balance, or in case of insufficient balance invoiced in arrears based on the prevailing rate. Changes in the baseline capacity, amount ordered or any other change that will have an impact on the monthly service fee can be requested via the Sales team.

Reporting

Functional Reporting

The MPB operational console provides information regarding the service delivery.

• Dashboard: Overall information about the backup health
• Protection targets: Items that can be configured to be protected (virtualization platforms, databases, file servers, etc.)
• Jobs: Backup and restore listing, execution history and scheduling
• Reports: Detailed information about product configuration

SLA Reporting

Customers may ask for SLA reporting via Service Request at any time without incurring additional charges.

Service Levels

The purpose of the Service Level Agreement (SLA) is to define the measurable performance levels associated with the MPB service and specify remedies available to Customer if Equinix fails to achieve these levels. The service credits listed below are the sole and exclusive remedy for any failure to meet the service level thresholds stated herein.

The SLA on support applies to the incident registration and resolution.

Priority	Response Time	Resolution Time	Execution of Work	SLA
P1	< 30 min	< 4 hours	24 × 7	95%
P2	< 60 min	< 24 hours	24 × 7	95%
P3	< 120 min	< 5 days	24 × 7	95%

Response time is from submitting the Trouble tickets and an Equinix Managed Solutions specialist sending a formal response. Resolution time of a case is from registering to closing or cancelling the Trouble Ticket in the ITSM Tool or the hand over to IBX Support. SLA applies to the response time, details on the SLA can be found in the Product Policy.

The MPB service SLA is:

Service Option	Availability
Managed Private Backup – Flex	99.95%

Useful Resources

Managed Private Backup User Guide v1.1 Service Description - Managed Private Backup