Resources

Metallic Documentation

No matter where your data is or where you want to store it, Metallic has a solution. 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.

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

Getting Started

To start backing up your data, see Going to the Hub.

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
    • Endpoint
  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.

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, network, and disk requirements

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

Hardware 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
Network requirements
Requirements 1TB/10VMs 3TB/30VMs 10TB/100VMs 30TB/300VMs
Network interface card 1 Gbps NIC 1 Gbps NIC 1 Gbps NIC 2 10 Gbps NIC
Available internet bandwidth requirements 30 Mbps 100 Mbps 1 Gbps 3 Gbps
Network access to backup service hosts and storage services (*.metallic.io) TCP 443 outbound TCP 443 outbound TCP 443 outbound TCP 443 outbound
Disk requirements
Requirements 1TB/10VMs 3TB/30VMs 10TB/100VMs 30TB/300VMs
Operating system and program files 300 GB, 200 IOPS 500 GB, 250 IOPS 1 TB, 250 IOPS 3 TB, 500 IOPS
On-premises copy (30 days retention maximum) 2 TB, any IOPS 6 TB, any IOPS 20 TB, any IOPS 60 TB, any IOPS

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

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

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

Endpoint actions

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.