Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Using SQL database store on another Server 2

Status
Not open for further replies.

RichinSTL

MIS
May 3, 2004
4
US
I was wondering if it is possible to use a database on another server or if it has to be on the same machine that Backup Exec is running on. I have three SQL Servers locally, and I'd prefer not to have another instance of SQL running on another server if it all possible.

For the sake of demonstration, I have four servers, A, B, C, and D. A and B are my production servers, both running SQL Server 2000 (SP3a). C is a developmental server also running SQL Server 2000 SP3a. D is an application server that I have Backup Exec installed on. I would like to move (or recreate) the databases on one of the two existing production SQL Servers (A or B) rather than having another instance of SQL running on the network.

Any response is greatly appreciated.

Thanks,

Rich
 
Have all of the SQL servers dump their data to disk using SQL backup. Then have Veritas backup each dump directory.

Much faster and a lot more stable.
 
Right, but that doesn't address the issue of having another instance of SQL Server running on the network. Since Veritas uses SQL Server as it's database of choice, I'm interested in integrating it into our existing SQL Server structure, not alternatives on backing up our existing SQL Databases.

Rich
 
Yes.

A and B are live servers. Use SQL Backup to drop them to disk.
C is development. Drop that to disk if you need to. Use SQL backup to RESTORE from A or B's disks (shared out appropriately) and then you have an automatically updated copy one day older.
D is backup server. Have it remotely backup (as you get 3 remote agents) A, B and C's dumps.

You only need the SQL installations you want.
Your DR strategy is sound.
You automatically get C pretty up to date automatically.
Your backups are more stable.
 
Rich

You can't do it with this version of Backup Exec.

The SQL database has to be on the Backup Exec server, either in the MSDE instance or in an instance of full blown SQL server.
 
Thank you very much to both of you, your answers were both helpful, but in different ways. Zelandakh, thanks for the help with the backup strategies, and Justin2000 for answering the question that I asked. Unfortunately, it wasn't the answer I was hoping to hear, but it was the answer I expected to hear.

Rich
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top