This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

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

We recently moved a SGE 7.1 DB from one SQL cluster to another. I was able to reconfigured through SGE Manager to point to the new location, restarted, created server config packages for the internal server and for a server in the DMZ we use for clients on the internet to report to. However, after running the Config package installer, uninstalling the old config and installing the new, the test page (where you test Connection to the DB) is still connecting to the old database. Likewise, it appears that the clients are as well. The clients are configured to connect to a DNS name that hasn't changed.

This thread was automatically locked due to age.

Parents

0 S1P over 5 years ago
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.}

In the SafeGuard Management Center menu bar, select 'Tools
| Options'.

Select the 'Certificates' tab and click 'Export...' in the 'Company
Certificate' section.

You are prompted to enter a password for securing the
exported file. Enter a password, confirm it and click 'OK'.

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:

In the SafeGuard Management Center menu bar, select 'Tools
| Options'.

Select the 'Certificates' tab and
click 'Export...' in the 'Certificate
of {MSO Currently Logged In}' section.

You are prompted to enter a password for securing the
exported file. Enter a password, confirm it and click 'OK'.

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:

Use SQL Management Studio to create a 'FULL' backup
of the SafeGuard database.

Make note of all Users assigned Security rights on the SafeGuard database.

Restore SafeGuard Database backup to New SQL Server:

Use SQL Management Studio to restore the SafeGuard
database backup to new SQL server.

Ensure that all Users assigned Security rights on the
SafeGuard database are added to the new SQL Server.

Reset SafeGuard Management
Center Configuration:

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:

Select 'Tools | Configuration Package Tool'

Select the 'Servers' tab.

Select server(s) that is connecting to the old database
location.

Database connection can be verified in the 'Database
connection' field.

Double-Click on selected server's 'Database
connection' field to open connection settings.

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:

Select 'Tools | Configuration
Package Tool'

Select the 'Server Packages' tab.

Select the server that had database connection changed.

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):

Go to 'Start | Control Panel |
Programs and Features' in Windows.

Uninstall the outdated server configuration package.

Install the new server configuration package.

Verify SafeGuard Server database connection with
'Invoke' test:

From within Windows, open Internet Information Services
(IIS) Manager.

Expand '{server name} | Sites | Default Web
Site'.

Click on 'SGNSRV' and select 'Browse
*:80 (http) or 'Browse *:443 (https)'.

From the Sophos SafeGuard web page that opens, select the 'CheckConnection' link.

Under 'CheckConnection | Test' click on 'Invoke'.

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.}
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 S1P over 5 years ago
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.}

In the SafeGuard Management Center menu bar, select 'Tools
| Options'.

Select the 'Certificates' tab and click 'Export...' in the 'Company
Certificate' section.

You are prompted to enter a password for securing the
exported file. Enter a password, confirm it and click 'OK'.

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:

In the SafeGuard Management Center menu bar, select 'Tools
| Options'.

Select the 'Certificates' tab and
click 'Export...' in the 'Certificate
of {MSO Currently Logged In}' section.

You are prompted to enter a password for securing the
exported file. Enter a password, confirm it and click 'OK'.

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:

Use SQL Management Studio to create a 'FULL' backup
of the SafeGuard database.

Make note of all Users assigned Security rights on the SafeGuard database.

Restore SafeGuard Database backup to New SQL Server:

Use SQL Management Studio to restore the SafeGuard
database backup to new SQL server.

Ensure that all Users assigned Security rights on the
SafeGuard database are added to the new SQL Server.

Reset SafeGuard Management
Center Configuration:

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:

Select 'Tools | Configuration Package Tool'

Select the 'Servers' tab.

Select server(s) that is connecting to the old database
location.

Database connection can be verified in the 'Database
connection' field.

Double-Click on selected server's 'Database
connection' field to open connection settings.

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:

Select 'Tools | Configuration
Package Tool'

Select the 'Server Packages' tab.

Select the server that had database connection changed.

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):

Go to 'Start | Control Panel |
Programs and Features' in Windows.

Uninstall the outdated server configuration package.

Install the new server configuration package.

Verify SafeGuard Server database connection with
'Invoke' test:

From within Windows, open Internet Information Services
(IIS) Manager.

Expand '{server name} | Sites | Default Web
Site'.

Click on 'SGNSRV' and select 'Browse
*:80 (http) or 'Browse *:443 (https)'.

From the Sophos SafeGuard web page that opens, select the 'CheckConnection' link.

Under 'CheckConnection | Test' click on 'Invoke'.

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.}
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data

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

SafeGuard Database Migration Process:

Prior to Database Migration:

Migrate SafeGuard Database to New SQL Server:

Reset SafeGuard Management Center Configuration:

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

SafeGuard Database Migration Process:

Prior to Database Migration:

Migrate SafeGuard Database to New SQL Server:

Reset SafeGuard Management Center Configuration:

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

SafeGuard Database Migration
Process:

Migrate SafeGuard Database to
New SQL Server:

Reset SafeGuard Management
Center Configuration:

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

SafeGuard Database Migration
Process:

Migrate SafeGuard Database to
New SQL Server:

Reset SafeGuard Management
Center Configuration:

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