Backup and Restore of COM.CFG

Last reviewed: April 17, 1997
Article ID: Q112636
The information in this article applies to:
  • Microsoft SNA Server for Windows NT, versions 2.0, 2.1, 2.11, 2.11sp1, and 3.0

The first step to ensuring proper configuration recovery is to back up your SNA Server configuration file (COM.CFG). This file resides on your SNA Server primary configuration server, and on any SNA Server backup configuration servers, in your <SNAROOT>\SYSTEM\CONFIG directory, shared to network users as <SERVER NAME>\COMCFG\COM.CFG.

This file contains important configuration information of the SNA Server, including SNA Servers in the domain, SNA connections they own, 3270 and APPC LUs configured, LU pools, and SNA Server user/group information.

To back up the COM.CFG file, do the following:

  1. From the File menu of SNA Admin, choose Backup.

  2. Type the name of the configuration file.

  3. In the dialog box, specify the drive you want to back up. If you want to back up a network drive, select the Network check box, or press ALT+W, to establish a network connection.

When you are satisfied with your options, choose the OK button.

(Note: All backup COM.CFG files have an .SNA extension.)

To restore your configuration:

  1. From the File menu in SNA Admin, choose Restore.

  2. Choose the path and filename you want to restore.

This file replaces the COM.CFG in the <SNAROOT>\SYSTEM\CONFIG directory.


Additional query words: prodsna
Keywords : kbnetwork ntgeneral
Version : 2.0 2.1 2.11 3.0
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 17, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.