Forum Discussion

Itera_Drift's avatar
Itera_Drift
Level 3
10 years ago

SQL Backup of Multiple instance

Hi

I have a server that contains two SQL instance. When creating a backup job, I'm able to see both SQL instance but i seems like it's the same Databases on

both instance. Do I have to configure anything so the agent is able to see both instace or should the databases appear by it self. The agent do have full access to the SQL server and databases.

 

 .Capture.PNG

 

Capture02.PNG

 Thanks

Steen Roenne

 

2014
Agent for Microsoft SQL Server
Backup and Recovery
Backup Exec
Not Applicable
  • SSR_7767's avatar
    SSR_7767
    10 years ago

    No specific configurations required. Just the installation of the remote agent is enough to show all the instances and the databases contained.

     

    As Colin Weaver has mentioned, you may have to check with your SQL admin to see if it is replicated.

  • Colin_Weaver's avatar
    Colin_Weaver
    Moderator
    10 years ago

    Probably more of a question for your SQL admin to confirm what is held within the two SQL instances (and whether or not they replicate between one anotbher.)

  • SSR_7767's avatar
    SSR_7767
    Level 4
    10 years ago

    No specific configurations required. Just the installation of the remote agent is enough to show all the instances and the databases contained.

     

    As Colin Weaver has mentioned, you may have to check with your SQL admin to see if it is replicated.

  • Itera_Drift's avatar
    Itera_Drift
    Level 3
    10 years ago

    Thanks for your feedback. I'm agree that it has to be in the SQL to solve the problem, as i'm sure if it was related to the agent it would have been mentioned in some whitepaper. Now I have to convince my SQL Admin to take another look at the server.

  • Itera_Drift's avatar
    Itera_Drift
    Level 3
    10 years ago

    Found the problem.

    the backup agent mixed the instance names (SQL management studio didn't have the problem - but ODBC manager could reproduce the problem).

    Using cliconfg.exe (use c:\windows\system32\cliconfg.exe for 64 bit and C:\Windows\SysWOW64\cliconfg.exe for 32 bit.exe) we created aliases for both instances choosing TCP as protocol and fixed port number 1433)

    This creates registry entries like this (you can also just add this to the registry directly - replace SERVERNAME with your SQL servers name and MYINSTANCE with you instance name - last set the correct IPnumbers).

    In this example the SQL server (and default instance of SQL server) SERVERNAME binds to 10.0.0.226 (TCP port 1433)

    and second instance of SQL server binds til 10.0.0.236 (TCP port 1433)

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo]
    "SERVERNAME"="DBMSSOCN,10.0.0.226,1433"
    "SERVERNAME\\MYINSTANCE"="DBMSSOCN,10.0.0.236,1433"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\ConnectTo]
    "SERVERNAME"="DBMSSOCN,10.0.0.226,1433"
    "SERVERNAME\\MYINSTANCE"="DBMSSOCN,10.0.0.236,1433"

    We restarted the Symantec backup agent after this