I have made some changes on configurations on mcserver.xml files /usr/local/avamar/var/mc/server_data/prefs/mcserver.xml and after the changes i'll need to restart MCS to make sure it takes affect.Īs usual, you will need to login as ADMIN, or in my case i login as root and then change to Admin - ssh-add ~admin/.ssh/admin_key The MCS contacts the client’s avagent process and starts an avtar to perform a backup or recovery.
Avamar agents are platform-specific software processes that run on the client and communicate with the Management Console Server (MCS) and any plug-ins installed on The MCS interacts with the client avagent to start backup and recovery. When you start the Avamar GUI you are interacting with the MCS The MCS also runs the server-side processes used by the Avamar Administrator graphical management console which is serviced by JAVA. The Management Console Server (MCS) provides centralized administration (scheduling, monitoring, and management) for the Avamar server. System State backups exclude Windows Server 2012 deduplicated volumes. Windows Server Core 2012 backup completes with exceptions. System State backups of dynamic critical volumes on storage spaces are not supported.
System State backups of offline dynamic critical disks fail in Windows Server 2008. Performing BMR backups of Windows Server 2003 or Windows XP clients.
Performing BMR backups of Windows Server 2012, Windows Server 2008, Windows 8, or Windows 7 clients. Performing file system backups in a Windows Server 2008 or Windows Server 2003 cluster. Performing file system backups in a Windows Server 2012 cluster. Performing file system backups on a stand-alone server. Restoring SIS volumes on Windows Server 2008. Uninstalling the Avamar Client for Windows. Uninstalling the federated cluster client in a Windows Server 2008 or Windows Server 2003 cluster. Upgrading the Avamar client in a Windows Server 2008 or Windows Server 2003 cluster. Upgrading the Avamar client in a Windows Server 2012 cluster. Upgrading the Avamar client on a stand-alone server. Changing the Backup Agent service account in Windows Server 2012 clusters.
Viewing the cluster client configuration. EMC Avamar 7.0 for Windows Server User Guide Configuring the federated cluster client on Windows Server 2008 or Windows Server 2003. Configuring the proxy cluster client on Windows Server 2012. Installing the Avamar Client for Windows.
Installation Preparing to install the Avamar client software. Data Domain system support for file system backups. Cluster Configuration Tool for configuring the cluster client.
Windows Server 2012 and Windows 8 support. Considerations for critical disks and dynamic disks. BMR of Windows Server 2003 and Windows XP. BMR of Windows Server 2012, Windows Server 2008, Windows 8, and Windows 7. How Avamar works in a Windows Server 2008 and Windows Server 2003 cluster. How Avamar works in a Windows Server 2012 cluster. For the most up-to-date regulatory document for your product line, go to the technical documentation and advisories section on the EMC online support website.ĮMC Avamar 7.0 for Windows Server User Guide All other trademarks used herein are the property of their respective owners. EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. The information in this publication is provided as is. The information is subject to change without notice. Published May, 2014 EMC believes the information in this publication is accurate as of its publication date. EMC® Avamar® 7.0 for Windows Server User Guide P/N 300-015-229 REV 04Ĭopyright © 2001- 2014 EMC Corporation.