Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 1 subscriber
  • Views 2389 views
  • Users 0 members are here
Options
Suggested
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

Restoring Sophos45 on Sophos50 database

boeink_ID

hi, 

i recently  installing a fresh SEC 5.0 on my new server. 

the installation in success, with a new SOHPOS50 database of course (download also completed via the internet).

next phase:

import database from my pld server SOPHOS45.

i run restoredb.exe d:\sophos45.bak .\sophos sophos50 -->resulting the SEC now cannot start.

i've been walking around to find how to manage upgrading the database SOPHOS45 directly to 5.0 without affecting my old server.  so i tried to firstly :

- restore SOPHOS45.bak to mssqlserver,

-run upgradeDB.exe -debug -sourceVersion=45 , from ny new server, it said complete. but the database still empty.

i have also found an article said that the UpgradeDB.exe looked up to registry HKLM\software\sophos\ee\management tools\databaseconnectionMS

so i edited the key from SOPHOS50 to SOPHOS45, and SOPHOS47

niether works.

i need help.

thanks for any help.

:27071


This thread was automatically locked due to age.
Parents
  • 0

    Hello boeink_ID,

    restoredb.exe d:\sophos45.bak .\sophos sophos50

    SEC uses specific database names for specific versions (please see Sophos consoles and associated database names). Thus a backup from a SOPHOS45 database must be restored as SOPHOS45.

    UpgradeDB.exe looked up to registry ... so i edited the key

    Wrong again :smileywink:

    It works (and indeed does) as follows:

    You back up your old database (e.g. SOPHOS45) and restore with the same name (SOPHOS45) on your new (SOPHOS) database instance which was installed (or is used) by the new installation. The install created and initialized the database for the current version (in your case SOPHOS50).

    The key you mentioned names the current (i.e. target) version for the UpgradeDB, thus setting it to something else won't produce the desired results.

    So if you use upgradeDB.exe -sourceVersion=45 it looks for a SOPHOS45 database. I'd have expected that it would complain when not finding it but indeed it doesn't. Thus although the upgrade seemed "successful" the new database is empty due to the missing source.

    I see that while I was writing this Jak has already provided a detailed answer.

    I'd like to add one more caveat: If you intend to manage your existing clients (i.e. "move them over" to the new server) you'd have to reprotect them unless you imported the Certification Manager registry keys before installing SEC5.0.    

    Christian

    :27077
Reply
  • 0

    Hello boeink_ID,

    restoredb.exe d:\sophos45.bak .\sophos sophos50

    SEC uses specific database names for specific versions (please see Sophos consoles and associated database names). Thus a backup from a SOPHOS45 database must be restored as SOPHOS45.

    UpgradeDB.exe looked up to registry ... so i edited the key

    Wrong again :smileywink:

    It works (and indeed does) as follows:

    You back up your old database (e.g. SOPHOS45) and restore with the same name (SOPHOS45) on your new (SOPHOS) database instance which was installed (or is used) by the new installation. The install created and initialized the database for the current version (in your case SOPHOS50).

    The key you mentioned names the current (i.e. target) version for the UpgradeDB, thus setting it to something else won't produce the desired results.

    So if you use upgradeDB.exe -sourceVersion=45 it looks for a SOPHOS45 database. I'd have expected that it would complain when not finding it but indeed it doesn't. Thus although the upgrade seemed "successful" the new database is empty due to the missing source.

    I see that while I was writing this Jak has already provided a detailed answer.

    I'd like to add one more caveat: If you intend to manage your existing clients (i.e. "move them over" to the new server) you'd have to reprotect them unless you imported the Certification Manager registry keys before installing SEC5.0.    

    Christian

    :27077
Children
No Data