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
- Apache/2.4.6 (CentOS) Server at www.softmagazin.ru Port 443.
- 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.
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
Workload | Version | DPM installation | Protection and recovery |
---|---|---|---|
Client computers (64-bit) | Windows 10 | Physical 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, 2012 | Azure 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 VMM | VMM 2019, 2016 | Physical server Hyper-V virtual machine VMware virtual machine | All deployment scenarios: Database |
SQL Server | SQL Server 2019, SQL Server 2017, 2016 and supported SPs, 2014 and supported SPs | Physical 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. |
Exchange | Exchange 2019, 2016 | Physical 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 |
SharePoint | SharePoint 2019, 2016 with latest SPs | Physical 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
Workload | Version | DPM installation | Protection and recovery |
---|---|---|---|
Hyper-V host - DPM protection agent on Hyper-V host server, cluster, or VM | Windows Server 2019, 2016, 2012 R2, 2012 | Physical 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 VMs | VMware server 6.0, or 6.5, 6.7 | Physical 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
Workload | Version | DPM installation | Protection and recovery |
---|---|---|---|
Linux | Linux 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
Workload | Version | DPM installation | DPM - System Center SAC | DPM - System Center 2016 | Protection and recovery |
---|---|---|---|---|---|
System Center VMM | VMM 2016, VMM 2012, SP1, R2 | Physical server Hyper-V virtual machine | Y | Y | All deployment scenarios: Database |
Client computers (64-bit and 32-bit) | Windows 10 | Physical server Hyper-V virtual machine VMware virtual machine | Y | Y | 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 8.1 | Physical server Hyper-V virtual machine | Y | Y | 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 8.1 | Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware) | Y | Y 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 8 | Physical server On-premises Hyper-V virtual machine | Y | Y | Volume, share, folder, files, deduped volumes Protected volumes must be NTFS and at least 1 GB. |
Client computers (64-bit and 32-bit) | Windows 8 | Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware) | Y | Y | 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 7 | Physical server On-premises Hyper-V virtual machine | Y | Y | Volume, share, folder, files, deduped volumes Protected volumes must be NTFS and at least 1 GB. |
Client computers (64-bit and 32-bit) | Windows 7 | Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware) | Y | Y | 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 (32-bit and 64-bit) | Windows Server 2016 | 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) 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 Standard | Azure virtual machine (when workload is running as Azure virtual machine) | Y | Y | Volume, 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 Standard | Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware) | Y | Y | Volume, 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 Standard | Physical server On-premises Hyper-V virtual machine | Y | Y | Volume, 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 Standard | Azure virtual machine (when workload is running as Azure virtual machine) | Y | Y | Volume, 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 Standard | Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware) | Y | Y | Volume, 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 Enterprise | Physical 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 Enterprise | Azure 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 Enterprise | Windows 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 R2 | Physical server On-premises Hyper-V virtual machine | Y | Y | Volume, share, folder, file, system state/bare metal |
Servers (32-bit and 64-bit) | Windows Server 2008 R2 | Azure virtual machine (when workload is running as Azure virtual machine) | N | N | Volume, share, folder, file |
Servers (32-bit and 64-bit) | Windows Server 2008 R2 | Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware) | N | N | Volume, share, folder, file, system state/bare metal |
Servers (32-bit and 64-bit) | Windows Server 2008 SP2 | Physical server On-premises Hyper-V virtual machine | N | N | Volume, share, folder, file, system state/bare metal |
Servers (32-bit and 64-bit) | Windows Server 2008 SP2 | Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware) | Y | Y | Volume, share, folder, file, system state/bare metal |
Servers (32-bit and 64-bit) | Windows Storage Server 2008 SP2 | Physical server On-premises Hyper-V virtual machine | Y | Y | Volume, share, folder, file, system state/bare metal |
SQL Server | SQL Server 2017 | Physical server On-premises Hyper-V virtual machine Azure virtual machine Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware) | Y | Y (UR5 Onwards) | All deployment scenarios: database |
SQL Server | SQL Server 2016 SP1 | Physical server On-premises Hyper-V virtual machine Azure virtual machine Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware) | Y | Y (UR4 onwards) | All deployment scenarios: database |
SQL Server | SQL Server 2016 | Physical server On-premises Hyper-V virtual machine Azure virtual machine Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware) | Y | Y (UR2 Onwards) | All deployment scenarios: database |
SQL Server | SQL Server 2014 | Azure virtual machine (when workload is running as Azure virtual machine) | Y | Y | All deployment scenarios: database |
SQL Server | SQL Server 2014 | Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware) | Y | Y | All deployment scenarios: database |
SQL Server | SQL Server 2012 with SP2 | Physical server On-premises Hyper-V virtual machine | Y | Y | All deployment scenarios: database |
SQL Server | SQL Server 2012 with SP2 | Azure virtual machine (when workload is running as Azure virtual machine) | Y | Y | All deployment scenarios: database |
SQL Server | SQL Server 2012 with SP2 | Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware) | Y | Y | All deployment scenarios: database |
SQL Server | SQL Server 2012, SQL Server 2012 with SP1 | Physical server On-premises Hyper-V virtual machine | Y | Y | All deployment scenarios: database |
SQL Server | SQL Server 2012, SQL Server 2012 with SP1 | Azure virtual machine (when workload is running as Azure virtual machine) | Y | Y | All deployment scenarios: database |
SQL Server | SQL Server 2012, SQL Server 2012 with SP1 | Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware) | Y | Y | All deployment scenarios: database |
SQL Server | SQL Server 2008 R2 | Physical server On-premises Hyper-V virtual machine | Y | Y | All deployment scenarios: database |
SQL Server | SQL Server 2008 R2 | Azure virtual machine (when workload is running as Azure virtual machine) | Y | Y | All deployment scenarios: database |
SQL Server | SQL Server 2008 R2 | Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware) | Y | Y | All deployment scenarios: database |
SQL Server | SQL Server 2008 | Physical server On-premises Hyper-V virtual machine | Y | Y | All deployment scenarios: database |
SQL Server | SQL Server 2008 | Azure virtual machine (when workload is running as Azure virtual machine) | Y | Y | All deployment scenarios: database |
SQL Server | SQL Server 2008 | Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware) | Y | Y | All deployment scenarios: database |
Exchange | Exchange 2016 | Physical server On-premises Hyper-V virtual machine | Y | Y | Protect (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 |
Exchange | Exchange 2016 | Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware) | Y | Y | Protect (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 |
Exchange | Exchange 2013 | Physical server On-premises Hyper-V virtual machine | Y | Y | Protect (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 |
Exchange | Exchange 2013 | Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware) | Y | Y | Protect (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 |
Exchange | Exchange 2010 | Physical server On-premises Hyper-V virtual machine | Y | Y | Protect (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 |
Exchange | Exchange 2010 | Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware) | Y | Y | Protect (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 |
SharePoint | SharePoint 2016 | Physical 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) | Y | Y (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 |
SharePoint | SharePoint 2013 | Physical server On-premises Hyper-V virtual machine | Y | Y | 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 |
SharePoint | SharePoint 2013 | Azure virtual machine (when workload is running as Azure virtual machine) - DPM 2012 R2 Update Rollup 3 onwards | Y | Y | Protect (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 |
SharePoint | SharePoint 2013 | Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware) | Y | Y | Protect (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 |
SharePoint | SharePoint 2010 | Physical server On-premises Hyper-V virtual machine | Y | Y | Protect (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 |
SharePoint | SharePoint 2010 | Azure virtual machine (when workload is running as Azure virtual machine) | Y | Y | Protect (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 |
SharePoint | SharePoint 2010 | Windows virtual machine in VMware (protects workloads running in Windows virtual machine in VMware) | Y | Y | Protect (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 VM | Windows Server 2016 | Physical server On-premises Hyper-V virtual machine | Y | Y | 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 |
Hyper-V host - DPM protection agent on Hyper-V host server, cluster, or VM | Windows Server 2012 R2 - Datacenter and Standard | Physical server On-premises Hyper-V virtual machine | Y | Y | 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 |
Hyper-V host - DPM protection agent on Hyper-V host server, cluster, or VM | Windows Server 2012 - Datacenter and Standard | Physical server On-premises Hyper-V virtual machine | Y | Y | 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 |
Hyper-V host - DPM protection agent on Hyper-V host server, cluster, or VM | Windows Server 2008 R2 SP1 - Enterprise and Standard | Physical server On-premises Hyper-V virtual machine | Y | Y | 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 |
Hyper-V host - DPM protection agent on Hyper-V host server, cluster, or VM | Windows Server 2008 SP2 | Physical server On-premises Hyper-V virtual machine | N | N | 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 |
Linux | Linux running as Hyper-V guest | On-premises Hyper-V virtual machine | Y | Y | Hyper-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 VMs | VMware server 5.5, 6.0, or 6.5 | On-premises Hyper-V virtual machine | Y | N | VMware 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 VMs | VMware vSphere 6.7 | On-premises Hyper-V virtual machine | Y (Applicable for DPM 1807 and later) | N | VMware 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.
Copyright © 2015 Arcserve. All rights reserved. |