October 27, 2008 at 1:50 pm
I have 2 SQL servers.
1 is the MAIN one with various databases on it! It's being backed up!
The other is the for one HR application with ONE Database.
Is this possible? and HOW can I do this????
1. Synchronize the HR Database to the Main-SQL server. - This way there is always a copy on the other server.
2. This way I will only back up the MAIN-SQL server with Backup Exec. and I don't have to buy two clients.
October 27, 2008 at 2:02 pm
There isn't a great way to do this. If you have two SQL Servers, you want to back up the HR database separately. You can script or setup a package of some sort to copy those backup files to the main server and use Backup Exec to then get the data to tape.
You could also use Database mirroring to move the data to the main server if you wanted. That's a relatively easy solution.
If you are talking about the Backup Exec Agent for SQL Server, I'd highly recommend you just don't use this. I have had numerous issues getting that to work on restores. Back up to disk with SQL Server and then let Backup Exec grab the files and move them to tape.
October 27, 2008 at 2:08 pm
So I could do database mirror. with the MAIN server. How can I do this? Is it a simple step by step process? or a mini/delicate project?
* To be Honest I'm thinking about steering away from backup exec and using the Acronis True Image SQL server BACKUP for the MAIN. (Back Up exec is just headaches all over for me) -
Whatcha think?
October 27, 2008 at 2:10 pm
if you are talking about an hr database the needs to be updated on each server then merge replication would allow that
It you are talking just reporting off of one of the servers then transactional replications would be the ticket
October 27, 2008 at 2:14 pm
oscar (10/27/2008)
Is it a simple step by step process? or a mini/delicate project?
Look up Database Mirroring in Books Online. It's not too complex, but it's not a 2-click process. Also you need to make sure you don't impact the primary server (possible if the network is poor or the mirror server under heavy load)
* To be Honest I'm thinking about steering away from backup exec and using the Acronis True Image SQL server BACKUP for the MAIN. (Back Up exec is just headaches all over for me) -
Whatcha think?
Use SQL native backups unless you've got a good reason not to. It works, it can be easily scheduled (sql agent), it's well known, your backup can be restored to any SQL server without needing a 3rd party tool installed.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 30, 2008 at 1:09 pm
That's interesting... and it sounds good. Using the native backup solution. Does it do recurring backups? In other words... I've had issues in the past where it keeps backing up and fills up the drive. - Can I set it to only maintain a certain time period worth of data? recycle after a month?
October 30, 2008 at 2:12 pm
There are a ton of ways to setup backups in SSMS, and yes there is a clean up task that you can have execute at the end of the task that will delete old backups.
This should get you started.
http://msdn.microsoft.com/en-us/library/ms187510(SQL.90).aspx
October 31, 2008 at 7:09 am
Ok thanks, I will look into that link and give it a shot!
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply