Guest

Cisco Security Agent

CSA FAQ: How do I move CSA-MC Release 6.x to a new physical server?

Document ID: 116449

Updated: Sep 05, 2013

Contributed by Scott Nishimura and Corey Lawrence, Cisco TAC Engineers.

   Print

Introduction

This document describes the process to move Cisco Security Agent (CSA)-Management Center (MC) 6.x to a new server. For customers on Release 6.x who look to move to a new server, you need to perform the steps outlined in this document. The process is different than when you reinstall and restore the configuration since CSA is homed to a specific server.

How do I move CSA-MC Release 6.x to a new physical server?

Use this process to move CSA-MC 6.x to a new server.

Note: CSA is homed to a specific server. It is critical to maintain the new server with the same IP and Windows device name in order to migrate with minimal changes/procedures.

  1. Run a backup and export the configuration in CSA.
  2. Back up the configuration with the CSA 6.x Configuration Guide.
  3. Install the new Windows server with the same IP and Windows name.

    Note: The new server must be Windows 2003 and cannot be 64 bit, as this is not supported by CSA-MC. The clients can be 64 bit but not the Management Center.

  4. When the new server is functional, ensure that you unplug and/or shut down the old server as to prevent a duplicate IP address.
  5. Install CSA-MC as administrator.
  6. Restore the configuration on the new server from Step 1.
  7. Create a backup of the new server. This step is very important.
  8. Replace the old CSA backup files with the new CSA server files.
  9. Manually copy these database files from the old server to the new server:
    • *.mdf
    • *.ldf
    • *.ndf - for the csamc60
    • *.mdf and *.ldf - for the analysis60

If all steps are completed properly, the clients should report to the new server.

Related Information

Updated: Sep 05, 2013
Document ID: 116449