Ca Olp As Backup Client Agent For Mac



Glp arcserve backup 16.5 client agent for mac os x comp upgrade w 1yr enterprise maint: networking: Avl: RFQ: BABWCU1650W22C4: ca corp. Olp arcserve backup 16.5 client agent for windows competitive upg w 1yr enterprise maintenance: networking: Avl: RFQ: BABWCU1650W20C4.

-->

Important

  1. Apache/2.4.6 (CentOS) Server at www.softmagazin.ru Port 443.
  2. Most Mac users rely on Apple’s backup solution, Time Machine.As useful and generally reliable as it is, Time Machine doesn’t support the essential “3-2-1” backup rule: to have three copies of your data — one in production and two copies — across two different types of media, with one copy stored offsite.

This version of Data Protection Manager (DPM) has reached the end of support, we recommend you to upgrade to DPM 2019.

This article details the workloads that DPM can back up.

Client

Use the following matrix for DPM 2016 and Semi-Annual Channel releases: 1801 and 1807:

  • Workloads – The workload type of technology.

  • Version – Supported VMM version for the workloads.

  • DPM installation – The computer/location where you wish to install DPM.

  • Protection and recovery – List the detailed information about the workloads such as supported storage container or supported deployment.

Use the following matrix for DPM 2019:

  • Workloads – The workload type of technology.

  • Version – Supported DPM version for the workloads.

  • DPM installation – The computer/location where you wish to install DPM.

  • Protection and recovery – List the detailed information about the workloads such as supported storage container or supported deployment.

Protection support matrix

The following sections details the protection support matrix for DPM:

Applications Backup

WorkloadVersionDPM installationProtection and recovery
Client computers (64-bit)Windows 10Physical server
Hyper-V virtual machine
VMware virtual machine
Volume, share, folder, files, deduped volumes
Protected volumes must be NTFS. FAT and FAT32 aren't supported.
Volumes must be at least 1 GB. DPM uses Volume Shadow Copy Service (VSS) to take the data snapshot and the snapshot only works if the volume is at least 1 GB.
Servers (64-bit)Windows Server 2019, 2016, 2012 R2, 2012Azure virtual machine (when workload is running as Azure virtual machine)
Physical server
Hyper-V virtual machine
VMware virtual machine
Volume, share, folder, file, deduped volumes.
System state and bare metal (not supported for Azure virtual machine).
DPM 2019 UR1 and later supports the protection of ReFS volumes and ReFS deduped volume.
System Center VMMVMM 2019, 2016Physical server
Hyper-V virtual machine
VMware virtual machine
All deployment scenarios: Database
SQL ServerSQL Server 2019, SQL Server 2017, 2016 and supported SPs, 2014 and supported SPsPhysical server
Hyper-V virtual machine
VMware virtual machine
Azure virtual machine
All deployment scenarios: database
DPM 2019 UR1 and later supports the backup of SQL over ReFS.
DPM 2019 UR2 and later supports the backup of SQL database, stored on the Cluster Shared Volume.
ExchangeExchange 2019, 2016Physical server
Hyper-V virtual machine
VMware virtual machine
Protect (all deployment scenarios): Standalone Exchange server, database under a database availability group (DAG)
Recover (all deployment scenarios): Mailbox, mailbox databases under a DAG
DPM 2019 does not support the backup of Exchange over ReFS
DPM 2019 UR1 and later supports the backup of Exchange over ReFS
SharePointSharePoint 2019, 2016 with latest SPsPhysical server
Hyper-V virtual machine
VMware virtual machine
Azure virtual machine (when workload is running as Azure virtual machine)
Protect (all deployment scenarios): Farm, frontend web server content
Recover (all deployment scenarios): Farm, database, web application, file or list item, SharePoint search, frontend web server
DPM 2019 UR1 and later supports the backup of SharePoint over ReFS

Ca Olp As Backup Client Agent For Mac Download

VM Backup

Agent
WorkloadVersionDPM installationProtection and recovery
Hyper-V host - DPM protection agent on Hyper-V host server, cluster, or VMWindows Server 2019, 2016, 2012 R2, 2012Physical server
Hyper-V virtual machine
VMware virtual machine
Protect: Hyper-V computers, Hyper-V VMs hosted on (cluster shared volumes) CSVs
Recover: Virtual machine, Item-level recovery of files and folder, volumes, virtual hard drives
VMware VMsVMware server 6.0, or 6.5, 6.7Physical server
Hyper-V virtual machine
VMware virtual machine
Protect: VMware VMs on cluster-shared volumes (CSVs), NFS, and SAN storage.
Recover: Virtual machine, Item-level recovery of files and folder available only for Windows, volumes, virtual hard drives.
VMware vApps are not supported.

Linux

WorkloadVersionDPM installationProtection and recovery
LinuxLinux running as Hyper-V guest (Hyper-V running on Windows Server 2016/2019/2012 R2/2012)
Linux virtual machines running on the versions 5.5, 6.0, 6.5 or 6.7 of VMware vCenter and vSphere Hypervisor (ESXi).
Hyper-V virtual machine
VMware virtual machine
Hyper-V must be running on Windows Server 2019, Windows Server 2016, Windows Server 2012 R2 or Windows Server 2012.
Protect: Entire virtual machine
Recover: Entire virtual machine
Only file-consistent snapshots are supported.
For a complete list of supported Linux distributions and versions, see the article, Linux on distributions endorsed by Azure.

Protection support matrix

WorkloadVersionDPM installationDPM - System Center SACDPM - System Center 2016Protection and recovery
System Center VMMVMM 2016,
VMM 2012, SP1, R2
Physical server
Hyper-V virtual machine
YYAll deployment scenarios: Database
Client computers (64-bit and 32-bit)Windows 10Physical server
Hyper-V virtual machine
VMware virtual machine
YYVolume, share, folder, files, deduped volumes
Protected volumes must be NTFS. FAT and FAT32 aren't supported.
Volumes must be at least 1 GB. DPM uses Volume Shadow Copy Service (VSS) to take the data snapshot and the snapshot only works if the volume is at least 1 GB.
Client computers (64-bit and 32-bit)Windows 8.1Physical server
Hyper-V virtual machine
YYVolume, share, folder, files, deduped volumes
Protected volumes must be NTFS. FAT and FAT32 aren't supported.
Volumes must be at least 1 GB. DPM uses Volume Shadow Copy Service (VSS) to take the data snapshot and the snapshot only works if the volume is at least 1 GB.
Client computers (64-bit and 32-bit)Windows 8.1Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)YY
From Update Rollup 5 onwards
Volume, share, folder, files, deduped volumes
Protected volumes must be NTFS. FAT and FAT32 aren't supported.
Volumes must be at least 1 GB. DPM uses Volume Shadow Copy Service (VSS) to take the data snapshot and the snapshot only works if the volume is at least 1 GB.
Client computers (64-bit and 32-bit)Windows 8Physical server
On-premises Hyper-V virtual machine
YYVolume, share, folder, files, deduped volumes
Protected volumes must be NTFS and at least 1 GB.
Client computers (64-bit and 32-bit)Windows 8Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)YYVolume, share, folder, files, deduped volumes
Protected volumes must be NTFS. FAT and FAT32 aren't supported.
Volumes must be at least 1 GB. DPM uses Volume Shadow Copy Service (VSS) to take the data snapshot and the snapshot only works if the volume is at least 1 GB.
Client computers (64-bit and 32-bit)Windows 7Physical server
On-premises Hyper-V virtual machine
YYVolume, share, folder, files, deduped volumes
Protected volumes must be NTFS and at least 1 GB.
Client computers (64-bit and 32-bit)Windows 7Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)YYVolume, share, folder, files, deduped volumes
Protected volumes must be NTFS. FAT and FAT32 aren't supported.
Volumes must be at least 1 GB. DPM uses Volume Shadow Copy Service (VSS) to take the data snapshot and the snapshot only works if the volume is at least 1 GB.
Servers (32-bit and 64-bit)Windows Server 2016Azure virtual machine (when workload is running as Azure virtual machine)
Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)
Physical server
On-premises Hyper-V virtual machine
Y
Not Nano server
Y
Not Nano server
Volume, share, folder, file, system state/bare metal), deduped volumes
Servers (32-bit and 64-bit)Windows Server 2012 R2 - Datacenter and StandardAzure virtual machine (when workload is running as Azure virtual machine)YYVolume, share, folder, file
DPM must be running on at least Windows Server 2012 R2 to protect Windows Server 2012 deduped volumes.
Servers (32-bit and 64-bit)Windows Server 2012 R2 - Datacenter and StandardWindows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)YYVolume, share, folder, file, system state/bare metal)
DPM must be running on Windows Server 2012 or 2012 R2 to protect Windows Server 2012 deduped volumes.
Servers (32-bit and 64-bit)Windows Server 2012/2012 with SP1 - Datacenter and StandardPhysical server
On-premises Hyper-V virtual machine
YYVolume, share, folder, file, system state/bare metal
DPM must be running on at least Windows Server 2012 R2 to protect Windows Server 2012 deduped volumes.
Servers (32-bit and 64-bit)Windows Server 2012/2012 with SP1 - Datacenter and StandardAzure virtual machine (when workload is running as Azure virtual machine)YYVolume, share, folder, file
DPM must be running on at least Windows Server 2012 R2 to protect Windows Server 2012 deduped volumes.
Servers (32-bit and 64-bit)Windows Server 2012/2012 with SP1 - Datacenter and StandardWindows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)YYVolume, share, folder, file, system state/bare metal
DPM must be running on at least Windows Server 2012 R2 to protect Windows Server 2012 deduped volumes.
Servers (32-bit and 64-bit)Windows Server 2008 R2 SP1 - Standard and EnterprisePhysical server
On-premises Hyper-V virtual machine
Y
You need to be running SP1 and install Windows Management Frame 5.1
Y
You need to install Windows Management Frame 5.1
Volume, share, folder, file, system state/bare metal
Servers (32-bit and 64-bit)Windows Server 2008 R2 SP1 - Standard and EnterpriseAzure virtual machine (when workload is running as Azure virtual machine)Y
You need to install Windows Management Frame 5.1
Y
You need to be running SP1 and install Windows Management Frame 5.1
Volume, share, folder, file
Servers (32-bit and 64-bit)Windows Server 2008 R2 SP1 - Standard and EnterpriseWindows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)Y
You need to install Windows Management Frame 5.1
Y
You need to be running SP1 and install Windows Management Frame 5.1
Volume, share, folder, file, system state/bare metal
Servers (32-bit and 64-bit)Windows Server 2008 R2Physical server
On-premises Hyper-V virtual machine
YYVolume, share, folder, file, system state/bare metal
Servers (32-bit and 64-bit)Windows Server 2008 R2Azure virtual machine (when workload is running as Azure virtual machine)NNVolume, share, folder, file
Servers (32-bit and 64-bit)Windows Server 2008 R2Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)NNVolume, share, folder, file, system state/bare metal
Servers (32-bit and 64-bit)Windows Server 2008 SP2Physical server
On-premises Hyper-V virtual machine
NNVolume, share, folder, file, system state/bare metal
Servers (32-bit and 64-bit)Windows Server 2008 SP2Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)YYVolume, share, folder, file, system state/bare metal
Servers (32-bit and 64-bit)Windows Storage Server 2008 SP2Physical server
On-premises Hyper-V virtual machine
YYVolume, share, folder, file, system state/bare metal
SQL ServerSQL Server 2017Physical server
On-premises Hyper-V virtual machine
Azure virtual machine
Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)
YY (UR5 Onwards)All deployment scenarios: database
SQL ServerSQL Server 2016 SP1Physical server
On-premises Hyper-V virtual machine
Azure virtual machine
Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)
YY (UR4 onwards)All deployment scenarios: database
SQL ServerSQL Server 2016Physical server
On-premises Hyper-V virtual machine
Azure virtual machine
Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)
YY (UR2 Onwards)All deployment scenarios: database
SQL ServerSQL Server 2014Azure virtual machine (when workload is running as Azure virtual machine)YYAll deployment scenarios: database
SQL ServerSQL Server 2014Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)YYAll deployment scenarios: database
SQL ServerSQL Server 2012 with SP2Physical server
On-premises Hyper-V virtual machine
YYAll deployment scenarios: database
SQL ServerSQL Server 2012 with SP2Azure virtual machine (when workload is running as Azure virtual machine)YYAll deployment scenarios: database
SQL ServerSQL Server 2012 with SP2Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)YYAll deployment scenarios: database
SQL ServerSQL Server 2012, SQL Server 2012 with SP1Physical server
On-premises Hyper-V virtual machine
YYAll deployment scenarios: database
SQL ServerSQL Server 2012, SQL Server 2012 with SP1Azure virtual machine (when workload is running as Azure virtual machine)YYAll deployment scenarios: database
SQL ServerSQL Server 2012, SQL Server 2012 with SP1Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)YYAll deployment scenarios: database
SQL ServerSQL Server 2008 R2Physical server
On-premises Hyper-V virtual machine
YYAll deployment scenarios: database
SQL ServerSQL Server 2008 R2Azure virtual machine (when workload is running as Azure virtual machine)YYAll deployment scenarios: database
SQL ServerSQL Server 2008 R2Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)YYAll deployment scenarios: database
SQL ServerSQL Server 2008Physical server
On-premises Hyper-V virtual machine
YYAll deployment scenarios: database
SQL ServerSQL Server 2008Azure virtual machine (when workload is running as Azure virtual machine)YYAll deployment scenarios: database
SQL ServerSQL Server 2008Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)YYAll deployment scenarios: database
ExchangeExchange 2016Physical server
On-premises Hyper-V virtual machine
YYProtect (all deployment scenarios): Standalone Exchange server, database under a database availability group (DAG)
Recover (all deployment scenarios): Mailbox, mailbox databases under a DAG
Backup of Exchange over ReFS not supported
ExchangeExchange 2016Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)YYProtect (all deployment scenarios): Standalone Exchange server, database under a database availability group (DAG)
Recover (all deployment scenarios): Mailbox, mailbox databases under a DAG
Backup of Exchange over ReFS not supported
ExchangeExchange 2013Physical server
On-premises Hyper-V virtual machine
YYProtect (all deployment scenarios): Standalone Exchange server, database under a database availability group (DAG)
Recover (all deployment scenarios): Mailbox, mailbox databases under a DAG
Backup of Exchange over ReFS not supported
ExchangeExchange 2013Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)YYProtect (all deployment scenarios): Standalone Exchange server, database under a database availability group (DAG)
Recover (all deployment scenarios): Mailbox, mailbox databases under a DAG
Backup of Exchange over ReFS not supported
ExchangeExchange 2010Physical server
On-premises Hyper-V virtual machine
YYProtect (all deployment scenarios): Standalone Exchange server, database under a database availability group (DAG)
Recover (all deployment scenarios): Mailbox, mailbox databases under a DAG
Backup of Exchange over ReFS not supported
ExchangeExchange 2010Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)YYProtect (all deployment scenarios): Standalone Exchange server, database under a database availability group (DAG)
Recover (all deployment scenarios): Mailbox, mailbox databases under a DAG
Backup of Exchange over ReFS not supported
SharePointSharePoint 2016Physical server
On-premises Hyper-V virtual machine
Azure virtual machine (when workload is running as Azure virtual machine)
Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)
YY (UR2 Onwards)Protect (all deployment scenarios): Farm, frontend web server content
Recover (all deployment scenarios): Farm, database, web application, file or list item, SharePoint search, frontend web server
SharePointSharePoint 2013Physical server
On-premises Hyper-V virtual machine
YYProtect (all deployment scenarios): Farm, frontend web server content
Recover (all deployment scenarios): Farm, database, web application, file or list item, SharePoint search, frontend web server
SharePointSharePoint 2013Azure virtual machine (when workload is running as Azure virtual machine) - DPM 2012 R2 Update Rollup 3 onwardsYYProtect (all deployment scenarios): Farm, SharePoint search, frontend web server content
Recover (all deployment scenarios): Farm, database, web application, file or list item, SharePoint search, frontend web server
SharePointSharePoint 2013Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)YYProtect (all deployment scenarios): Farm, SharePoint search, frontend web server content
Recover (all deployment scenarios): Farm, database, web application, file or list item, SharePoint search, frontend web server
SharePointSharePoint 2010Physical server
On-premises Hyper-V virtual machine
YYProtect (all deployment scenarios): Farm, SharePoint search, frontend web server content
Recover (all deployment scenarios): Farm, database, web application, file or list item, SharePoint search, frontend web server
SharePointSharePoint 2010Azure virtual machine (when workload is running as Azure virtual machine)YYProtect (all deployment scenarios): Farm, SharePoint search, frontend web server content
Recover (all deployment scenarios): Farm, database, web application, file or list item, SharePoint search, frontend web server
SharePointSharePoint 2010Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware)YYProtect (all deployment scenarios): Farm, SharePoint search, frontend web server content
Recover (all deployment scenarios): Farm, database, web application, file or list item, SharePoint search, frontend web server
Hyper-V host - DPM protection agent on Hyper-V host server, cluster, or VMWindows Server 2016Physical server
On-premises Hyper-V virtual machine
YYProtect: Hyper-V computers, Hyper-V VMs hosted on (cluster shared volumes) CSVs
Recover: Virtual machine, Item-level recovery of files and folder, volumes, virtual hard drives
Hyper-V host - DPM protection agent on Hyper-V host server, cluster, or VMWindows Server 2012 R2 - Datacenter and StandardPhysical server
On-premises Hyper-V virtual machine
YYProtect: Hyper-V computers, Hyper-V VMs hosted on (cluster shared volumes) CSVs
Recover: Virtual machine, Item-level recovery of files and folder, volumes, virtual hard drives
Hyper-V host - DPM protection agent on Hyper-V host server, cluster, or VMWindows Server 2012 - Datacenter and StandardPhysical server
On-premises Hyper-V virtual machine
YYProtect: Hyper-V computers, Hyper-V VMs hosted on (cluster shared volumes) CSVs
Recover: Virtual machine, Item-level recovery of files and folder, volumes, virtual hard drives
Hyper-V host - DPM protection agent on Hyper-V host server, cluster, or VMWindows Server 2008 R2 SP1 - Enterprise and StandardPhysical server
On-premises Hyper-V virtual machine
YYProtect: Hyper-V computers, Hyper-V VMs hosted on (cluster shared volumes) CSVs
Recover: Virtual machine, Item-level recovery of files and folder, volumes, virtual hard drives
Hyper-V host - DPM protection agent on Hyper-V host server, cluster, or VMWindows Server 2008 SP2Physical server
On-premises Hyper-V virtual machine
NNProtect: Hyper-V computers, Hyper-V VMs hosted on (cluster shared volumes) CSVs
Recover: Virtual machine, Item-level recovery of files and folder, volumes, virtual hard drives
LinuxLinux running as Hyper-V guestOn-premises Hyper-V virtual machineYYHyper-V must be running on Windows Server 2012 R2 or Windows Server 2016. Protect: Entire virtual machine
Recover: Entire virtual machine
For a complete list of supported Linux distributions and versions, see the article, Linux on distributions endorsed by Azure.
VMware VMsVMware server 5.5, 6.0, or 6.5On-premises Hyper-V virtual machineYNVMware VMs on cluster-shared volumes (CSVs), NFS, and SAN storage.
Item-level recovery of files and folders available only for Windows. VMware vApps not supported.
VMware VMsVMware vSphere 6.7On-premises Hyper-V virtual machineY (Applicable for DPM 1807 and later)NVMware VMs on cluster-shared volumes (CSVs), NFS, and SAN storage.
Item-level recovery of files and folders available only for Windows. VMware vApps not supported.

Cluster support

DPM can protect data in the following clustered applications:

  • File servers

  • SQL Server

  • Hyper-V

    Note

    If you're protecting a Hyper-V cluster using scaled-out DPM protection, you can't add secondary protection for the protected Hyper-V workloads.

  • Exchange Server - DPM can protect non-shared disk clusters for supported Exchange Server versions (cluster continuous replication), and can also protect Exchange Server configured for local continuous replication.

  • SQL Server

    Note

    DPM doesn't support the protection of SQL Server databases hosted on cluster-shared volumes (CSVs).

DPM can protect cluster workloads that are located in the same domain as the DPM server, and in a child or trusted domain. If you want to protect data source in untrusted domains or workgroups you'll need to use NTLM or certificate authentication for a single server, or certificate authentication only for a cluster.

Next steps

UNIX, Linux, and Mac OS X Client Agent Control Files

The UNIX, Linux, and Mac OS X client agent control files specify which directories, file systems, or file system types are to be excluded from backup operations on a specific workstation. In particular, the following packages must be installed with the UNIX, Linux, and Mac OS X client agents:

  • The Common Agent
  • The Universal Agent (uagent)

Note: You must install the Common Agent before you install the uagent.

The control files installed for both packages include:

  • Directory Control file

    Use the Directory Control file, uag.cntl, to list all directories or file systems (or both) that you want to exclude from backup operations on a workstation. To specify directories and file systems in this file, enter a slash (/) followed by a one line, complete path name. For example:

    Note: The Directory Control file is stored on the client agent workstation in the uagent home directory.

  • File System Control file

    The File System Control file, fs.cntl lists the file system types on a particular workstation that are to be excluded from backup operations. To exclude a particular file system type, enter the type on a separate line in the fs.cntl file.

    Note: The File System file is stored on the client agent workstation in the uagent home directory.

  • Browser Configuration File

    The Browser Configuration file, cabr.cfg, enables raw devices to be viewed with the browser. You must ensure that you have entered the absolute name of the raw device on a separate line in the cabr.cfg file.

  • Common Agent Configuration File

    The Common Agent configuration file, agent.cfg, keeps track of each UNIX, Linux, or Mac OS X client agent installed on your system. This script is run automatically after the uagent is installed.

Ca Olp As Backup Client Agent For Mac Os

Note: Only a system administrator can edit the Directory and File System control files. However, other users may be able to append the files, depending on the file access rights the system administrator has assigned to the file.

ClientCa Olp As Backup Client Agent For Mac
Copyright © 2015 Arcserve. All rights reserved.