EMC® Avamar® Compatibility and Interoperability Matrix

EMC® Avamar® Compatibility and Interoperability Matrix EMC® Avamar® Compatibility and Interoperability Matrix

25.02.2013 Views

EMC Avamar Compatibility and Interoperability Matrix Contact your EMC Sales or EMC Customer Service representative for updates or information not included in this document. EMC maintains a large collection of the products as well as third-party application software for qualification with EMC backup and recovery systems and to simulate customer environments, but you must consult the vendors for information about their systems. Policy for future qualification of software releases The information in this document is maintained by EMC, and EMC strives to update this document with new releases of hardware, operating systems, firmware, BIOS, applications, and so on, as they become available from the vendors. EMC works with the vendors during their development and release processes in order to be fully informed at the time the vendors release new versions. EMC does not announce qualification prior to vendors’ general availability; in these cases and in cases where advance preparation is not possible, EMC may test and qualify vendors’ products as appropriate after they have been released. For early support of such products including vendor beta participation, contact your EMC Sales or EMC Customer Service representative. Policy for end-of-life support EMC strives to continue support for any installed platforms, but may remove support from this matrix for new installations within three months after the vendor has announced that this platform has reached the end of life. EMC will continue support for existing installations of hardware, operating systems, and components that the vendor has officially declared to have reached end of life as long as support is available from the vendor. EMC 6 Avamar Compatibility and Interoperability Matrix

EMC Avamar client-server interoperability Table 1 lists the Avamar client-server interoperability support matrix. Table 1: EMC Avamar client-server interoperability Avamar Server Version EMC Avamar Compatibility and Interoperability Matrix Avamar client version 3.7.X 4.0.X 4.1 5.0.x 6.0 3.7.X X X X 4.0.X X X X X 4.1.X X X X X X 5.0.X X X X X 6.0.x X X X For the latest Avamar Client Package, there is no need to perform a server upgrade to get the latest client enhancements, as an existing Avamar v4.x or v5.x server can be upgraded with the new client code. There are a few exceptions to this for the following items: • VMware vSphere support requires the Avamar 5.0 GA server (build 5.0.0-407 or greater) or later • VMWare vSphere 4.1 ESX and ESXi support integration requires the Avamar v5.0 SP3 server and the updated VMware proxy client included in the Avamar v5.0SP3 release or later • NAT support requires the Avamar 5.0 GA server (build 5.0.0-407 or greater) or later • Windows and Mac Desktop and Laptop support requires the Avamar 5.0 GA server (build 5.0.0-407 or greater) or later • Windows and Mac Desktop/Laptop support requires Avamar server & client 5.0 or later. • Localization updates for Desktop/Laptop requires the Avamar v5.0 SP3 server and the updated Desktop/Laptop client(s) included in the Avamar v5.0SP3 release or later • The following SQL Plugin features requires Avamar 5.0 Service Pack 1 server (build 5.0.1-32 or greater) or later o SQL automated log tail backups, SQL point in time recovery, SQL forced incremental backups • The Exchange VSS Plug-in Granular Level Recovery (GLR) feature requires Avamar 6.0 server or later • The SharePoint VSS Plug-in requires Avamar 6.0 server or later • Data Domain integration requires Avamar 6.0 server or later EMC Avamar Compatibility and Interoperability Matrix 7

EMC Avamar client-server interoperability<br />

Table 1 lists the Avamar client-server interoperability support matrix.<br />

Table 1: EMC Avamar client-server interoperability<br />

Avamar Server Version<br />

EMC Avamar <strong>Compatibility</strong> <strong>and</strong> <strong>Interoperability</strong> <strong>Matrix</strong><br />

Avamar client version 3.7.X 4.0.X 4.1 5.0.x 6.0<br />

3.7.X X X X<br />

4.0.X X X X X<br />

4.1.X X X X X X<br />

5.0.X X X X X<br />

6.0.x X X X<br />

For the latest Avamar Client Package, there is no need to perform a server upgrade to get the latest client<br />

enhancements, as an existing Avamar v4.x or v5.x server can be upgraded with the new client code. There<br />

are a few exceptions to this for the following items:<br />

• VMware vSphere support requires the Avamar 5.0 GA server (build 5.0.0-407 or greater) or later<br />

• VMWare vSphere 4.1 ESX <strong>and</strong> ESXi support integration requires the Avamar v5.0 SP3 server <strong>and</strong> the<br />

updated VMware proxy client included in the Avamar v5.0SP3 release or later<br />

• NAT support requires the Avamar 5.0 GA server (build 5.0.0-407 or greater) or later<br />

• Windows <strong>and</strong> Mac Desktop <strong>and</strong> Laptop support requires the Avamar 5.0 GA server (build 5.0.0-407<br />

or greater) or later<br />

• Windows <strong>and</strong> Mac Desktop/Laptop support requires Avamar server & client 5.0 or later.<br />

• Localization updates for Desktop/Laptop requires the Avamar v5.0 SP3 server <strong>and</strong> the updated<br />

Desktop/Laptop client(s) included in the Avamar v5.0SP3 release or later<br />

• The following SQL Plugin features requires Avamar 5.0 Service Pack 1 server (build 5.0.1-32 or<br />

greater) or later<br />

o SQL automated log tail backups, SQL point in time recovery, SQL forced incremental<br />

backups<br />

• The Exchange VSS Plug-in Granular Level Recovery (GLR) feature requires Avamar 6.0 server or later<br />

• The SharePoint VSS Plug-in requires Avamar 6.0 server or later<br />

• Data Domain integration requires Avamar 6.0 server or later<br />

EMC Avamar <strong>Compatibility</strong> <strong>and</strong> <strong>Interoperability</strong> <strong>Matrix</strong><br />

7

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!