The Agent for VMware Virtual Infrastructure (AVVI) and Microsoft Hyper-V (MSHV) Application GRT does not work for all supported applications (Exchange, SQL and Active Directory) unless all of the applications (Exchange, SQL, and/or Active Directory) installed on the Virtual Machine are licensed in Backup Exec for Windows 2010.
This issue occurs when one of the three above mentioned applications is not licensed in Backup Exec when using the Application GRT functionality with the AVVI or MSHV agents.
This issue is most likely to mainly occurs with virtual machines running Small Business Server (SBS), but is not limited to such a setup. This is due to the fact that an SBS server is a DC (Domain Controller) but the SBS license for Backup Exec doesn not include licensing for Active Directory GRT backupsthem. Table 1 shows a list of environments the issue can occur in.
|Applications installed on the VM||Applications NOT licensed in Backup Exec|
|Microsoft Exchange and Microsoft SQL||Microsoft SQL|
|Microsoft Exchange and Microsoft SQL||Microsoft Exchange|
|Microsoft Exchange and Active Directory||Active Directory|
|Microsoft Exchange and Active Directory||Microsoft Exchange|
|Microsoft SQL and Active Directory||Active Directory|
|Microsoft SQL and Active Directory||Microsoft SQL|
|Microsoft SQL, Microsoft Exchange and Active Directory||Active Directory|
|Microsoft SQL, Microsoft Exchange and Active Directory||Microsoft SQL|
|Microsoft SQL, Microsoft Exchange and Active Directory||Microsoft Exchange|
The AVVI and MSHV agents have the option to turn off specific Application GRT agents in the back up jobs, SQL, Exchange and Active Directory. Even if any of these options are turned off in the Backup job, users may still have the issue outlined above.
The VM is still completely protected when either of these issues occur. Only Application GRT is affected, Customers experiencing this issue will still be able to recover the VM.
A hotfix (TECH146017) is now available for this issue in Backup Exec 2010 R2. Refer to the Hotfix link under Related Documents at the end of this article to obtain the hotfix needed to resolve the issue