Resources

Metallic Documentation

No matter where your data is or where you want to store it, Metallic has a solution.

Going to the Hub

Go to the Hub for an overall picture of the health of your Metallic environment. The Hub is also the place to configure new data sources to back up.

Procedure

  1. Go to hub.metallic.io and log in. The Hub appears.
  2. To determine the health of the environment, select from the following tabs, and then review the information in the tiles:
    • Metallic Core
    • Office 365
    • Endpoints
  3. To back up a new data source, in the upper-right corner of the page, from the New Configuration list, click the type of data that you want to back up, and then follow the instructions in the guided setup.

Use cases

Data source Data source location Backup storage location
  • File servers
  • SQL servers
Cloud Cloud
  • File servers
  • Endpoints
  • SQL servers
  • Virtual machines
On-premises
  • Cloud
  • On-premises
  • On-premises and cloud
Office 365:
  • Exchange
  • OneDrive
  • SharePoint
Cloud Cloud

To learn more about choosing a storage option, see All about storage.

Video Resouces

Metallic Core Backup & Recovery
Metallic Office 365 Backup & Recovery
Metallic Endpoint Backup & Recovery

Security and compliance

Metallic is committed to ensuring the security of your data at every level. Metallic is built on Microsoft Azure, the cloud platform leading the industry in compliance with over 90 certifications.

Commvault Systems, Inc. is also an ISO.IEC 27001:2013 certified provider whose Information Security Management System (ISMS) has received third-party accreditation from the International Standards Organization. The scope of our ISO/IEC 27001:2013 certification includes the Commvault offering Metallic.

A-lign, an independent, third-party auditor, found Metallic to have technical controls in place and formalized IT Security policies and procedures. A-lign is an ISO / IEC 27001 certification body accredited by the ANSI-ASQ National Accreditation Board (ANAB) to perform ISMS 27001 certifications.

Core

To store data in a cloud, use your own cloud or use the Metallic cloud. To store data on-premises, configure a backup gateway. Data can be stored directly on the backup gateway, or you can access other resources by using a UNC path.

Data flow

All about storage

Deciding where to store your data doesn't have to be hard. You can choose to back up to an on-premises server, to the cloud, or to a combination of both.

Let's look at the benefits and considerations for all of the options.

On-premises storage

Restoring data from an on-premises server is as fast as your own network.

Benefits of on-premises storage:

  • Fast recovery
  • No charge for moving data
  • You know exactly where your data is

Considerations for on-premises storage:

  • You must manage your storage infrastructure
  • Adding or upgrading storage requires planning and money

Cloud storage

Storing data in the cloud gives you the flexibility to scale up or down depending on your storage needs.

Benefits of cloud storage:

  • Easy to scale
  • No infrastructure management

Considerations for cloud storage:

  • Slower recovery
  • Depending on the agreement with the cloud provider, there could be charges associated with restoring data

Related topics

Backup gateway requirements

The on-premises backup gateway functions as a proxy between the on-premises data source and the cloud backup service. If you want to use on-premises backup storage, you can store a copy of your data on the on-premises backup gateway.

Important: The on-premises backup gateway must be able to connect to the Metallic Backup Service and must be able to access the servers that need to be backed up.

Data flow

Hardware requirements

Install the backup gateway package on a server that meets the following minimum requirements.

Requirements 1TB/10VMs 3TB/30VMs 10TB/100VMs 30TB/300VMs
CPU 2 vCPUs 2 vCPUs 2 vCPUs 4 vCPUs
RAM 8 GB 16 GB 16 GB 32 GB
Disk: Operating system and program files 300 GB, 200 IOPS 500 GB, 250 IOPS 1 TB, 250 IOPS 3 TB, 500 IOPS
Disk: On-premises copy (30 days retention maximum) 2 TB, any IOPS 6 TB, any IOPS 20 TB, any IOPS 60 TB, any IOPS

Network requirements

  • TCP 443 outbound must be open for network access to backup service hosts and storage services (*.metallic.io).
  • To back up VMware servers, the backup gateway must be able to access the VMware environment and components:
    • vCenter: Port for web service (default: 443) must be opened. If vCenter is configured to use non-default ports, the non-default ports must also be opened.
    • ESX Server: Ports for web service (default: 443) and TCP/IP (default: 902) must be opened for the vStorage APIs for data protection.

Sizing

Requirements 1TB/10VMs 3TB/30VMs 10TB/100VMs 30TB/300VMs
Network interface card 1 Gbps NIC 1 Gbps NIC 10 Gbps NIC 2 10 Gbps NIC
Available internet bandwidth requirements 30 Mbps 100 Mbps 1 Gbps 3 Gbps

Supported operating systems

The following operating systems are supported:

  • Microsoft Windows Server 2019 Editions
  • Microsoft Windows Server 2012 R2 Editions
  • Microsoft Windows Server 2012 Editions
  • Microsoft Windows Server 2016 Editions
  • Microsoft Windows Client 10 Editions

Cloud storage requirements

To store data in a cloud, use your own cloud or use the Metallic cloud.

Data flow

Supported providers

The following clouds are supported:

  • AWS
  • Azure

Requirements for backing up VMware servers

Review the following requirements if you want to back up on-premises VMware servers.

To backup on-premises data, a backup gateway is required. To review the requirements for the backup gateway, see Backup gateway requirements.

VMware vCenter Server Support

The following versions are supported for vCenter Server and vCenter Server Appliance. vCenter Server support includes support for vSphere, Virtual Disk Development Kit (VDDK), ESX or ESXi, and file system versions as provided by the vCenter version.

For more information, see Correlating build numbers and versions of VMware products (1014508).

As a general rule of thumb, each version of the VDDK supports vCenter Server for the two previous major versions and for the next minor version. For example, VDDK 6.0.0 can be used with vCenter Server 5.5, 5.1, or 6.0 Update 1.

When VMware issues new versions or updates, Metallic tests against the current service pack before announcing support. For new VMware versions or updates released between Metallic service packs, and for earlier supported versions or service packs, Metallic provides continuing support, including Hot Fixes as needed to address VMware changes to functions that affect backup and recovery.

vCenter Server Version

  • 6.7 Update 3 (all minor updates)
  • 6.7 Update 2 (all minor updates)
  • 6.7 Update 1 (all minor updates)
  • 6.7 (all minor updates)
  • 6.5 Update 3 (all minor updates)
  • 6.5 Update 2 (all minor updates)
  • 6.5 Update 1 (all minor updates)
  • 6.5 GA (all minor updates)
  • 6.0 Update 3 (all minor updates)
  • 6.0 Update 2 (all minor updates)
  • 6.0 Update 1 (all minor updates)
  • 6.0 GA (all minor updates)
  • 5.5 Update 3 (all minor updates)
  • 5.5 Update 2 (all minor updates)
  • 5.5 Update 1 (all minor updates)
  • 5.5 GA (all minor updates)
  • 5.1 (all updates)
  • 5.0 (all updates)
  • 4.1 (all updates)

Note: If VMs are part of ESX 4.1, then streaming and IntelliSnap backups are supported only through the vCenter. You cannot use a standalone ESX 4.1 server.

ESX Host Support

Before configuring backup of any ESXi servers, ensure that you are using Essentials licensing level or higher. The vStorage APIs for Data Protection (VADP) are not provided with the free version of ESXi.

VDDK Support

Metallic includes the latest supported VDDK. Multiple versions of the VDDK are included, and the appropriate VDDK for the vSphere version is loaded automatically when required.

vCenter Server Versions Required for Specific Features

Some features are supported only for more recent versions of vCenter Server. The following table shows the required versions for features that are dependent on the version of vCenter Server and associated software. Support includes all updates for each major version unless an update is specifically excluded.

Feature Required Version of vCenterServer
Agentless file restores 5.1, 5.5, 6.0, 6.5, 6.7
File Recovery Enabler for Linux 4.1, 5.1, 5.5, 6.0, 6.5, 6.7

Virtual Machine Hardware

Version 4.0, 7.0, 8.0, 9.0, 10.0, 11.0, 13.0, 14.0, 15.0

Virtual Machine Operating Systems

All Guest Operating Systems supported by VADP.

Datastore Support

  • Network File System (NFS)
  • Virtual Machine File System (VMFS)
  • Virtual storage area network (vSAN)
  • VMware Virtual Volume (VVol)

VMware Tools on Virtual Machines

The latest version of VMware Tools supported by the host should be installed on each virtual machine. At a minimum, the version of VMware tools on virtual machines must be supported on the host; unsupported versions must be upgraded. For more information about VMware Tools support for Windows and Linux guest VMs, see the VMware Compatibility Guide.

open-vm-tools

For UNIX guest VMs running the following operating system releases, open-vm-tools can be used:

  • Fedora 19 and later
  • Debian 7.x and later
  • openSUSE 11.x and later
  • Recent Ubuntu (12.04 LTS, 13.10 and later)
  • Red Hat Enterprise Linux 7.0 and later
  • CentOS 7.0 and later
  • Oracle Linux 7.0 and later
  • SUSE Linux Enterprise 12 and later

For more information, see VMware support for open-vm-tools (2073803).

Allocation Unit Size of NTFS Volumes

The cluster size or the allocation unit size of an NTFS volume in a virtual machine must be multiple of 1024 bytes per cluster. You can set the cluster size before formatting a volume. The default cluster size is 4096 bytes per cluster.

Disclaimer

Third-party maintenance (minor) releases or service packs that are supported by the Commvault software may not be listed in our System Requirements. When possible, Commvault provides information on any known issues related to these minor releases or service packs. In some cases, these minor releases or service packs affect how the Commvault software works. Commvault software may experience changes in functionality as the result of the third-party minor release or service pack. These changes are beyond the control of Commvault. Platforms that are supported in the current version of Commvault software may not be supported in earlier versions of the software. Contact your software provider to ensure that third-party minor releases or service packs are compatible with the Commvault software.

Additional considerations regarding minimum requirements and End-of-Life policies from third-party vendors also apply.

Transport Modes for VMware

By default, the transport mode is selected automatically for backups and restores, based on the gateway used and the virtual machines being backed up or restored. You can force a specific transport mode by configuring it.

The following transport modes are available in VMware. Advanced transport methods (HotAdd) replace the proxy-based VMware Consolidated Backup (VCB) solution.

  • SAN (storage area network) - SAN mode is supported for directly connected storage using Fibre Channel (FC) or Internet SCSI (iSCSI) protocols. With automatic transport mode selection, SAN mode is selected if SAN storage is connected to the ESX host. The Virtual Server Agent must have access to the datastore LUNs (logical drives) that provide storage for virtual machine disks. Data is read directly from the storage where virtual machines reside, without going through the ESX host or transferring data over the local area network (LAN). The ESX host is contacted only to coordinate access to the LUN.
  • HotAdd - In HotAdd mode, software is installed on a virtual machine residing on an ESX Server. The term HotAdd refers to the way the backups are completed. In HotAdd mode, virtual disks from the virtual machines being backed up are automatically mounted to the gateway, so they can be accessed by the gateway as local disks. The ESX host the gateway is running on must have access to all datastores for the virtual machine. If the virtual machine and the gateway are not on the same host, all datastores must be shared between the hosts.

    In vSphere 5.0, the SCSI HotAdd feature is enabled only for vSphere editions Enterprise and higher, which have Hot Add licensing enabled. No separate Hot Add license is available for purchase as an add-on. In vSphere 4.1, Hot Add was also enabled in the Advanced edition. Customers with vSphere Essentials or Standard editions are not able to perform proxy-based backup, which relies on SCSI HotAdd. Those customers must use alternate transport modes.

  • Local Area Network (NBD and NBDSSL) - NBD (network block device) and NBDSSL (encrypted NBD) transmit data over the TCP/IP connection between the ESX server and the gateway computer. NBD serves as a fallback when other transport modes are not available. The local area network (LAN) can be the production network or a dedicated backup network.

    NBDSSL is similar to NBD mode, but data transfer between the gateway computer and the ESX server is encrypted. Encryption should be used for sensitive information, even within a private network.

SAN and HotAdd transport can enable LAN-free backups and restores. In most scenarios, backups and restores using SAN and HotAdd transport are faster than local area network (LAN) operations using network block device (NBD) or secure NBD (NBDSSL).

SAN restores using thin disk provisioning can be slower than LAN restores; performance can be improved by using NBD or by setting the transport mode to SAN and forcing the disk type to thick, which uses eager zero provisioning.

The following table summarizes the configurations based on the storage type.

Mode Datastore Storage Type VM Data Protected by Single Node Additional Comments
LAN Free SAN mode VMFS using Fibre Channel or iSCSI Up to 40 TB Software installed on the same physical computer with direct connection to datastore.

Eliminates data transfer over network during backup and restore. Provides best backup and restore performance.
LAN Free HotAdd mode VMFS, NFS, vSAN, VVol Up to 30 TB Software installed on virtual machine running on host with access to datastore.

Eliminates data transfer over network during backup and restore.
Network based (NBD, HotAdd, NAS) VMFS, NFS, vSAN, VVol, direct attached storage Software installed on different computers. The software writes over the network to a remote computer.

Depends on infrastructure.

Connectivity

Configure DNS on the backup gateway, ESX hosts, and vCenter Server. For any transport mode, missing or incorrect DNS configuration produces nslookup errors during fully qualified domain name (FQDN) resolution.

Office 365

You can configure Office 365 applications to back up directly to the Metallic cloud without installing additional hardware or software. Protect data in the following Office 365 applications from accidental deletions, ransomware scenarios, and data corruption:

  • Exchange Online
  • SharePoint Online
  • OneDrive

When it is time to recover data, you can find and recover as many files as you need, or you can restore an entire folder or mailbox to a point in time. Metallic eliminates "dumpster diving" or rummaging through the Office 365 recycle bin.

Data flow

Configurations performed in Office 365

In your Office 365 applications, check the following configurations.

Exchange Online and OneDrive

  • You must have an Azure global administrator account. The global administrator account has access to management features and data across Microsoft online services. The global access is needed to back up Office 365 data.
  • Basic authentication must be enabled for the global administrator account.
  • Multi-factor Factor Authentication (MFA) must be turned off.

SharePoint Online

  • You must have a SharePoint service account with the SharePoint administrator role
  • You must have a SharePoint administrator site URL

Configuring connection details

Applies to: Office 365 with Exchange, User Mailbox

In an Office 365 with Exchange environment, you must configure the following service accounts to discover, archive, cleanup and restore data for user mailboxes, group mailboxes and all public folders.

  • Exchange Online Service Account

Important: Metallic software supports Microsoft Azure for public clouds only. Sovereign clouds, such as in Germany or China, are not supported. For more information, consult Microsoft documentation. For example, “App Service Regional Details.”

Before You Begin

The Office 365 with Exchange (Exchange Online) Administrator Account must have the Exchange Online Service Account configured. The account must be an online mailbox.

Procedure

  1. Open Windows PowerShell and create a remote PowerShell session to Office 365 with Exchange.
  2. To assign impersonation and view-only recipient permissions, type the following command:

    New-RoleGroup -Name "ExchangeonlinebackupGrp" -Roles "ApplicationImpersonation", "View-Only Recipients" -Members serviceaccount1,serviceaccount2

    where:

    • ExchangeonlinebackupGrp is a unique name of the new role group.
    • serviceaccount1 and serviceaccount2 are Exchange Online service accounts.
  3. Access the Azure portal (https://portal.azure.com/) using your global admin user account.
  4. In the Microsoft Azure dashboard, in the left navigation pane, go to Azure Active Directory > App registrations, and then click New Registration.
  5. On the Register an application blade, do the following:

    1. In the Name box, type a name for your application.
    2. Under Supported account types, select the accounts that you want to give access to this application API.
    3. The Redirect URI (optional) box, enter the URL.

      For most authentication scenarios, you need to enter this value. However, in some cases, you do not need to enter a value. Also, you can change this value later.

    4. Click Register.

      The Overview screen appears.

  6. On the Overview tab, go to View API Permissions > Add a permission > Microsoft Graph, and then click Application Permissions.

    The permissions screen appears.

  7. Expand Directory, and then select the Directory. Read. All permission.
  8. Click Add Permission.
  9. On the API Permissions tab, under Grant consent, click Grant admin consent for tenant name.

    A confirmation dialog box appears.

  10. Click Yes.

    A message states that admin consent is granted for the requested permissions.

  11. On the preview screen, click Overview, and then record the application ID and the directory ID.
  12. Click Certificates and secrets, and then complete the following steps:

    1. Click New client secret.
    2. To add an application key value, type a description, and then select Never Expires.
    3. Click Add.
    4. Record the client secret key value.

Restoring Mailboxes, Mailbox Items, or Messages for Exchange Online

You can restore a mailbox, a mailbox item (such as a folder, a contact, or a calendar entry), or a message.

Procedure

  1. From the navigation pane, go to Solutions > Office 365.

    The list of all Exchange clients appears.

  2. Click the Exchange client that contains the mailbox that you want to restore.

    The mailboxes page appears.

  3. Select the mailbox that you want to restore, and then click Restore.

    The page with the mailbox display name appears in the folder view.

  4. Do one of the following:
    • To restore a mailbox, select a mailbox in the left pane.
    • To restore a folder, expand the mailbox, and then select the folder.
    • To restore a message, in the right pane, select the appropriate message.
  5. Click Selected items.

    The Restore Options dialog box appears.

  6. From the Restore to list, select Mailbox.
  7. From the Destination host list, select the name of the Exchange server computer.
  8. To restore the data to the same path from which it was backed up, select the Restore to original folder check box.
  9. In the When message exists area, do either of the following:
    • To overwrite any existing messages, select Overwrite unconditionally.
    • To prevent an item that already exists from being overwritten, select Skip.
  10. Click Submit.

Restoring Mailboxes, Mailbox Items, or Messages to a Different Place for Exchange Online

You can restore a mailbox, a mailbox item (such as a folder, a contact, or a calendar entry), or a message to different folder on the same client or to a different Exchange client.

Procedure

  1. From the navigation pane, go to Solutions > Office 365.

    The list of all Exchange clients appears.

  2. Click the Exchange client that contains the mailbox that you want to restore.

    The mailboxes page appears.

  3. Select the mailbox that you want to restore, and then click Restore.

    The page with the mailbox display name appears in the folder view.

  4. Do one of the following:
    • To restore a mailbox, select a mailbox in the left pane.
    • To restore a folder, expand the mailbox, and then select the folder.
    • To restore a message, in the right pane, select the appropriate message.
  5. Click Selected items.

    The Restore Options dialog box appears.

  6. From the Restore to list, select Mailbox.
  7. Define where the messages are restored by doing one of the following:
    • If you want to restore to a different folder on the same client, clear the Restore to Original Folder check box, and then type the destination path.
    • If you want to restore to a different Exchange client, from the Destination client list, select the name of the appropriate client.
  8. Click Submit.

Restoring Office 365 SharePoint Sites

You can restore Office 365 SharePoint sites to the same site collection or to a different site collection.

Before You Begin

If you are restoring a deleted site, you must manually create the destination top-level site before performing the restore operation. Deleted subsites are automatically created under the destination top-level site during the restore operation.

Procedure

  1. From the navigation pane, go to Solutions > Office 365.

    The Office 365 apps page appears.

  2. Click a SharePoint server.

    The selected SharePoint server page appears.

  3. In the Contents section, click the Office 365 backup set.

    The Office 365 backup set properties page appears.

  4. In the Subclient section, click the subclient that you want to restore.

    The subclient properties page appears.

  5. In the Subclients table, in the subclient row, in the Restore column, click Restore.

    The Backup content page appears.

  6. In the upper-right corner of the page, select a backup to restore:
    • To use the most recent backup, click Show latest backups.
    • To use a backup from a specific date, click Show backups as of a specific date, select a date, and then select the backup.
  7. Select the sites that you want to restore, and then click Restore.

    Note: If you select multiple, related sites, the top-most selected site in the source hierarchy is restored to the destination site. The subsites are restored in the same hierarchical order as seen in the source.

    The Restore options dialog box appears.

  8. Clear the Restore to original folder check box.
  9. Next to Destination path, click Browse.

    Important: Do not copy and paste the URL from a web browser into the Destination path box.

    The Browse destination dialog box appears.

  10. Next to the destination site, click the check box, and then click OK.
  11. Click Submit.

Restoring OneDrive for Business Data

You can restore Microsoft OneDrive for Business data.

Procedure

  1. From the navigation pane, go to Solutions > Office 365.

    The Office 365 apps page appears.

  2. On the Apps page, click the OneDrive for Business app.

    The app page appears.

  3. On the Subclients tab, select the subclients that you want to restore, and then click Restore.

    The Backup content page appears.

  4. From the upper-right of the page, select the backups to restore:
    • To restore the most recent backup, click Show latest backups.
    • To restore a backup from a specific date, click Show backups as of a specific date, select a date, and then select the backup.
    • To restore a backup from a date range, click Show backups for a date range, select a date range, and then select the backup.
  5. Select the subclients you want to restore, and then click Restore.

    The Restore options dialog box appears.

  6. From the Restore to list, select OneDrive.
  7. To restore the data, follow one of the methods in the table below:
    • Restore to original folder: Select this check box to restore data to the folder from which the data was backed up.
    • Destination server: The data is restored to the server.
    • Unconditionally overwrite if it already exists: To overwrite files and folders that are in the destination and have the same names as files and folders that you are restoring, select this check box.
  8. Click Submit.

Endpoint

If you are using the Endpoint solution to back up user laptops and desktops, you can manage your endpoints by using the Hub.

Setup considerations

Add an antivirus exclusion for the installation path: Metallic_installation_directory\Metallic\Contentstore. For example, add c:\Program Files\Metallic\ContentStore.

If outbound traffic to TCP 80/443 is restricted, add these entries to your whitelist:

  • p000002ue2v.eastus2.cloudapp.azure.com IP: 52.252.15.17 (TCP port 443)

    Note: If you connect through a VPN, access to p000002ue2v.eastus2.cloudapp.azure.com 52.252.15.17 (TCP port 443) must be allowed through the VPN and on the application access layer for the VPN.

  • e000002ue2v.eastus2.cloudapp.azure.com IP: 52.251.7.76 (TCP 80,443)
  • e010002ue2v.eastus2.cloudapp.azure.com IP: 40.70.200.213 (TCP 80,443)

Endpoint hub

Download packages

To backup and monitor endpoint data, the Endpoint package must be installed on your users' laptops and desktops. You can ask your users to download and to install the laptop package, or you can perform a silent installation of the laptop package. For more information about these methods, see Install software and authenticate users.

The Endpoint package is available for the following operating systems:

Linux

  • Debian 9.x to Debian 10.x
  • Fedora release 29 with glibc 2.28.x to Fedora release 30 with glibc 2.29.x
  • Red Hat Enterprise Linux 7.x to Red Hat Enterprise Linux 8.x
  • Ubuntu 8.04 to Ubuntu 18.10

Macintosh

  • macOS Mojave (v10.14.x)
  • macOS High Sierra (v10.13.x)

Add Users Manually

To authenticate users with credentials stored in the Metallic backup service, manually add users. When you manually add users, you have the option to automatically send the users email invitations to download and install the Endpoint package on their laptops or desktops. The email invitation contains a link for to the Endpoint package and user credentials.

Note: If you configure an identity provider, you do not need to create users local to the Metallic backup service.

Configure Identity Provider

To authenticate users with an Active Directory (AD) identity server or SAML, configure an identity provider. Common SAML identity providers include AD FS, Azure, and Okta. For information about configuring an AD identity server or SAML, see Identity Provider Configuration for Endpoint.

Manage Backup Content

You can change what is backed up on user laptops and desktops. By default, the following content is included or excluded when a laptop or desktop is backed up:

Included Excluded
  • Desktop folder
  • Documents folder
  • Office file extenstions
  • Pictures folder
  • Image file extenstions
  • Temporary Files (Windows, Mac, Linux)
  • C:\Program Files
  • C:\Program Files (x86)
  • C:\Windows

Install software and authenticate users

To backup and monitor endpoint data, the Endpoint package must be installed on your users' laptops and desktops. You can ask your users to download and to install the laptop package, or you can perform a silent installation of the laptop package. To decide which method to use in your environment, review the details of each method.

Interactive installations
User authentication Tenant administrator action User action
Active Directory
  • Configure an Active Directory identity server.
  • Distribute the link for the laptop package and the auth code to users. Users can also use their email addresses to register their laptops.
Download and install the laptop package, and then register the laptop or desktop with the auth code provided by the tenant administrator or your email address.
SAML
  • Configure an identity provider that supports SAML.
  • Distribute the link for the laptop package and the auth code to users.
Download and install the laptop package, and then register the laptop or desktop with the auth code provided by the tenant administrator.
Local Create users and automatically send the users email invitations. The email invitation contains a link for the laptop package and user credentials. Download and install the laptop package, and then register the laptop or desktop with the credentials in the invitation email.
Silent installations
User authentication Tenant administrator action User action
Active Directory
  • Configure an Active Directory identity server.
  • Install the laptop package by using a third-party tool and the auth code.
None
SAML
  • Configure an identity provider that supports SAML.
  • Install the laptop package by using a third-party tool and the auth code.
None

Installing software by using a third-party tool

The Endpoint package can be pushed and installed using third-party software such as Microsoft System Center Configuration Manager (SCCM) or Jamf software.

Before you begin

Obtain the authorization code by going to the Hub, and then on the Endpoint tab, click Download Packages.

Procedure

Configure the third-party software to run the following command from the folder containing the laptop package contents.

  • Windows

    Windows packages use a self-extracting executable that can be launched using a deployment tool with command line. The package must be pushed to the machine locally before running the command line. Running the package remotely over the network is not supported.

    Win32_Client.exe /silent /install /silent /authcode authcode
    WinX64_Client.exe /silent /install /silent /authcode authcode

    Where authcode is the authorization code. The authorization code is required if the package does not contain user credentials for an installation user.

  • Macintosh Operating System (macOS)

    Silent macOS packages use the macOS pkg framework. These can be directly placed into the Jamf Casper software to run anytime. The package does not take arguments on command line, so you need to create a text file with the arguments, on the local macOS computer.

    On the local macOS computer, create an "install.ini" file in the global application support directory:

    • Path to the ini file: /Library/Application Support/Commvault/install.ini
    • Parameter inside the ini file: AUTH_CODE="######" After creating the text file, you can push the macOS.pkg package to the client.
    • sudo installer -pkg path_to_pkg -target /
  • UNIX Operating System

    For silent install on a UNIX machine, use the following:

    ./silent_install –authcode authcode

    Where authcode is the authorization code. The authorization code is required if the package does not contain user credentials for an installation user.

  • For interactive or semi-silent install on a UNIX machine, use the following:
    ./cvpkgadd –authcode authcode

    Where authcode is the authorization code. The authorization code is required if the package does not contain user credentials for an installation user.

Supported platforms and applications

You can back up data sources that meet the following requirements.

Applications

The following applications are supported.

Linux

  • Microsoft SQL Server 2017 Editions up to the latest Service Pack

Windows

  • Microsoft SQL Server 2017 Editions up to the latest Service Pack
  • Microsoft SQL Server 2016 Editions up to the latest Service Pack
  • Microsoft SQL Server 2014 Editions up to the latest Service Pack
  • Microsoft SQL Server 2012 Editions up to the latest Service Pack
  • Microsoft SQL Server 2008 R2 Editions up to the latest Service Pack
  • Microsoft SQL Server 2008 Editions up to the latest Service Pack
  • Microsoft SQL Server 2005 Editions up to the latest Service Pack

Endpoints

The following operating systems are supported for laptops and desktops.

Linux

  • Debian 9.x to Debian 10.x
  • Fedora release 29 with glibc 2.28.x to Fedora release 30 with glibc 2.29.x
  • Red Hat Enterprise Linux 7.x to Red Hat Enterprise Linux 8.x
  • Ubuntu 8.04 to Ubuntu 18.10

Macintosh

  • macOS Mojave (v10.14.x)
  • macOS High Sierra (v10.13.x)
  • macOS Sierra (v10.12.x)

Windows

  • Microsoft Windows 7 Editions to Microsoft Windows Client 10

File Servers

The following operating systems are supported.

Linux

  • Debian 9.x
  • Fedora release 29 with glibc 2.28.x
  • Red Hat Enterprise Linux/CentOS 7.x with glibc 2.17.x and Red Hat Enterprise Linux/CentOS 8.x with glibc 2.28.x
  • SuSE Linux (SLES) 11 to 15
  • Ubuntu 8.04 to Ubuntu 18.10

Windows

  • Microsoft Windows Server 2003 Editions to Microsoft Windows Server 2019 Editions: All editions except Nano Server

Hypervisors

The following hypervisors are supported.

VMware

  • Streaming backups using vCenter Server versions 4.1 – 6.7 Update 2