Backup and Recovery: Recommended Procedure for Symantec Mobile Security 7.2 Servers

book

Article ID: 158165

calendar_today

Updated On:

Products

Mobile Security

Issue/Introduction

What is required to recover from a disaster involving the device-facing Symantec Mobile Security 7.2 server?  What backup and recovery activities are needed to help minimize downtime and loss of services for Mobile Security? 

Resolution

Important note: These instructions are provided "as is" and as general guidelines for backup and recovery of a Mobile Security server.  Symantec is not responsible for loss or damage in any part due to these guidelines.  Each customer environment can potentially be configured differently, thus altering the validity of these instructions.  It assumes you have implemented regular backup processes on other vital parts of your organizations infrastructure.  This includes, but is not limited to, backup of Active Directory, DNS, Certificate Authority, reverse proxy hosts, Exchange, and SQL servers.  It also assumes you run regular backup and recovery drills, validating your organization's business continuity and disaster recovery procedures.

 

Backup and Restore the Full Server  

At the present time, the only supported method for restoring a SMS 7.2 server is to configure a backup / recovery solution to backup full server disk volume contents.  This full disk backup will include all Windows OS files, configurations, Windows registry, IIS certificates and settings, licenses and all content related to the Symantec Management Platform (SMP) and Symantec Mobile Security.  In the event that Disaster recovery is necessary, restore this full image / contents on to the same hardware or an identical system.

 

About Recovery and Mobile Security Gateways

The managed Android clients communicate with the SMP through a Mobile Security Gateway (MSG).  By default, a MSG is installed on the SMP during the installation of Symantec Mobile Security 7.2.  Additional MSGs can be installed in environment if it is desirable to have groups of Androids communicating though a different address.  

Should a server which is acting as a MSG be lost, a new Symantec Management Agent (Altiris client) and MSG can be deployed to a recovered server with that same IP address.  Mobile devices configured to use that MSG should then resume communicating with the management server.

Should the SMP be lost but the server acting as MSG remain undamaged, it will continue to act as a MSG as soon as the SMP is restored.  


Applies To

Symantec Mobile Security 7.2 server (SMS 7.2)