Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 7 replies
  • Subscribers 1 subscriber
  • Views 13625 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

having trouble backing up sophos database

cptjck28

Hi

I trying to back the sophos database before I update to enterprise console 5.2  but i get this error

C:\Program Files\Sophos\Enterprise Console\DB\Core>sqlcmd -E -S "[ucrxsql01\mssq
lserver]" -b -Q "BACKUP DATABASE [sophos51] TO DISK = 'C:\temp\sophos_DB_backup\
sophos51.bak'"
HResult 0xFFFFFFFF, Level 16, State 1
SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFF
FF].
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : A network-related or in
stance-specific error has occurred while establishing a connection to SQL Server
. Server is not found or not accessible. Check if instance name is correct and i
f SQL Server is configured to allow remote connections. For more information see
 SQL Server Books Online..
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : Login timeout expired.

Failed

i am using command backupdb C:\temp\sophos_DB_backup ucrxsql01\mssqlserver sophos51

any help would be apppracted

My sophos database is on another server  using  sqlserver 2008 r2 on server 2008 r2

:37649


This thread was automatically locked due to age.
  • 0

    Hello cptjck28,

    you can't back up a remote database from the management server. Please see 2. under What to do in Using backupdb.bat ...: On the computer hosting the Sophos databases ... (emphasis mine). 

    HTH

    Christian

    :37659
  • 0

    I was trying to do the backup on the server that has the Database.

    :37683
  • 0

    Try just using the server name rather than servername\mssqlserver.

    Regards,

    Jak

    :37691
  • 0

    Hi,

    I'm new to Sophos and need to backup the database but getting error BACKUP DATABASE permission denied in database. Investigating that this was due to account use during the setup of SEC already left the company. I'm upgrading SEC 4.5 to 5.1 but having issue with account permission.

    Is there a possible way I can upgrade SEC?

    Thanks in advance

    :46071
  • 0

    Hello Romardy,

    BackupDB.bat - if this is what you are using - accesses the database with the credentials of the logged on user. In order to upgrade you must be logged on as an administrator and usually this account should be able to access the database on the SQL server to perform the backup.

    Could you please post all the output of BackupDB (or whatever command you are using)?

    Christian

    :46075
  • 0

    Hi Christian,

    Thank you for your response. Unfortunately, I cannot recover the account which has access to the database and installed during the initial setup. What worries me now is the current policies that will not be migrated when I upgraded to 5.1. 

    It's hard to say that we will be using the older version 4.5 until any possible solution will come. 

    :46227
  • 0

    Hi,

    Below is the command I used to backup DB


    D:\Program Files\Sophos\Enterprise Console\DB>BackupDB d:\backup\backupdb0314.ba
    k SOPAVSPML01\SQLEXPRESS SOPHOS45

    and received below error

    D:\Program Files\Sophos\Enterprise Console\DB>osql -E -S "SOPAVSPML01\SQLEXPRESS
    " -n -b -Q "BACKUP DATABASE SOPHOS45 TO DISK = 'd:\backup\backupdb0314.bak'"
    [SQL Server Native Client 10.0]SQL Server Network Interfaces: No credentials
    are available in the security package
    [SQL Server Native Client 10.0]SQL Server Network Interfaces: No credentials
    are available in the security package
    [SQL Server Native Client 10.0]Client unable to establish connection
    [SQL Server Native Client 10.0]A network-related or instance-specific error
    has occurred while establishing a connection to SQL Server. Server is not
    found or not accessible. Check if instance name is correct and if SQL Server
    is configured to allow remote connections. For more information see SQL Server
    Books Online.

    Failed

    :48160