Moved DB - Test and users still reporting to old DB?

Did you restart the machine after removing and then applying the new config? I have known clients/servers to remember the config and a reboot was required before it would use the new config.

I would also use the tool (Server connectivity Check) SGNCSCC on the client. This will confirm exactly what the client is pointing at. The client though doesn't ever point at the SQL server - just the servers do this. The clients should (and do) point at the servers for connectivity.

The tool can be found here - c:\Program Files (x86)\Sophos\SafeGuard Enterprise\Client\SGNCSCC.exe 

If the client is pointing at the wrong server (although it doesn't sound as if you've changed this) this will be evident in this tool. 

Yes, I have restarted the server. The internal server works correctly (the internally connected systems report to the new DB location) but the one in the DMZ does not. It still proxies the external systems to the old DB.

The tool you mention must be in the SGE 7 client, as it doesn't appear to exist in the 6.00.1 client.

I guess I'll have to contact support as I'm out of ideas about how to get this to update.

Ah, sorry. Yes the tool appears in the 7 client and I'd presumed you were running the 7 client as well as the 7 server you did mention. 

It IS possible to get the tool on the older version though, I'll send you a DM....

Hello

I've recently migrated SGE to a new server. I called Sophos Support for guidance, and was given these high level steps to follow. They are not complete, and you still have to jump through a few hoops... But they may be of help to you, or any one else that needs them.

Thanks

Simon

---------------------------------------------

SafeGuard Database Migration
Process:

Prior to Database Migration:

• • Export the Company Certificate:

^{Note: Only Master Security Officers are entitled to export company
certificates for backup purposes.}

1. 1. In the SafeGuard Management Center menu bar, select 'Tools
      | Options'.
   2. Select the 'Certificates' tab and click 'Export...' in the 'Company
      Certificate' section.
   3. You are prompted to enter a password for securing the
      exported file. Enter a password, confirm it and click 'OK'.
   4. Enter a filename and storage location for the file then
      click 'OK'. 

^{Result: The company certificate is exported as a .p12 file to the
defined location and can be used for recovery purposes.}

• • Export the Master Security Officer Certificate: 
    
    
    1. 1. In the SafeGuard Management Center menu bar, select 'Tools
          | Options'.
       2. Select the 'Certificates' tab and
          click 'Export...' in the 'Certificate
          of {MSO Currently Logged In}' section.
       3. You are prompted to enter a password for securing the
          exported file. Enter a password, confirm it and click 'OK'.
       4. Enter a filename and storage location for the file then
          click 'OK'.

^{Result: The Master Security Officer certificate of the currently logged
on MSO is exported as a .p12 file to the defined location
and can be used for recovery purposes.}

Migrate SafeGuard Database to
New SQL Server:

^{Note: Stop
the IIS service on SafeGuard Server(s) to avoid any updates
to the database during migration.}

• • Backup Current SafeGuard Database:
    
    
    1. 1. Use SQL Management Studio to create a 'FULL' backup
          of the SafeGuard database.
       2. Make note of all Users assigned Security rights on the SafeGuard database.
  • Restore SafeGuard Database backup to New SQL Server:
    
    
    1. 1. Use SQL Management Studio to restore the SafeGuard
          database backup to new SQL server.
       2. Ensure that all Users assigned Security rights on the
          SafeGuard database are added to the new SQL Server.
    
    
    

Reset SafeGuard Management
Center Configuration:

1. 1. Delete the SafeGuard Management Console configuration files
      
      
      • • Browse to the Management Centre configuration files
          located in:
          
          
          • • Windows XP/ 2003:
              
              
              • • C:\Documents and
                  Settings\"User"\Local Settings\Application
                  Data\Utimaco\SafeGuard Enterprise\Configuration\
              
              
              
          
          
          • • Windows Vista/7/2008/2012:
              
              
              • • C:\Users\"User"\AppData\Local\Utimaco\SafeGuard
                  Enterprise\Configuration\
              
              
              
          
          
          
      
      
      • • Backup and delete all the .xml files from within the
          folder.
      
      
      • • Restart the SafeGuard Management Center.
      
      
      • • The 'SafeGuard Management Center Configuration Wizard'
          will now run automatically.
      
      
      • • Follow the prompts to configure your new SQL database
          instance and log into the Management Console.
      
      
      • • Repeat this process for 'each' SafeGuard
          Management Console install.
      
      
      

Re-Configure SafeGuard
Server(s) to Connect to database on new SQL server:

• • Reconfigure SafeGuard server(s) Database Connection:
    
    
    1. 1. Select 'Tools | Configuration Package Tool'
       2. Select the 'Servers' tab.
       3. Select server(s) that is connecting to the old database
          location.
          
          
          • • Database connection can be verified in the 'Database
              connection' field.
          
          
          
    
    
    1. 1. Double-Click on selected server's 'Database
          connection' field to open connection settings.
       2. Make the necessary connection changes and click on'Check
          connection'.
          
          
          • • Make sure you receive'Database connection
              verified successfully'.
          
          
          • • Click 'OK'.
          
          
          • • Click 'OK'. 
          
          
          

^{Note: Repeat for 'each' server listed that is connecting
to the old database location.}

• • Create 'new' server configuration package:
    
    
    1. 1. Select 'Tools | Configuration
          Package Tool'
       2. Select the 'Server Packages' tab.
       3. Select the server that had database connection changed.
       4. Click on '...' and choose an output path for the server
          configuration .msi.
    
    
    

^{Note: Repeat this process for 'each' server that had
it's database connection reconfigured.}

• • Apply 'new' server configuration package to
    SafeGuard Server(s):
    
    
    1. 1. Go to 'Start | Control Panel |
          Programs and Features' in Windows.
       2. Uninstall the outdated server configuration package.
       3. Install the new server configuration package.
    
    
    

• • Verify SafeGuard Server database connection with
    'Invoke' test:

1. 1. From within Windows, open Internet Information Services
      (IIS) Manager.
   2. Expand '{server name} | Sites | Default Web
      Site'.
   3. Click on 'SGNSRV' and select 'Browse
      *:80 (http) or 'Browse *:443 (https)'.
   4. From the Sophos SafeGuard web page that opens, select the 'CheckConnection' link.
   5. Under 'CheckConnection | Test' click on 'Invoke'.
   6. You should receive the following results if your SafeGuard
      Server is properly configured and connecting to the database
      in it's new location:

^{Note: Verify that the <WebService> and <DBAuth> are 'OK' and
the <Server> is set to your new SafeGuard Database SQL
Server.}