September 14, 2009 at 11:50 am
I am a database Admin for SQL Server. Now i have a client who need to do a backup every day to secure his data. So what i thought was doing replication or mirroring that will continuously synchronise data on our servers. now let me expplain the scenario
client has different domain
client has windows server 2003 standard exition
my company have different domain
my company have windows server 2003 enterprise edition
so if someone can suggest me some third party tools through which i can do replication or mirroring from client database to my local servers.
any help is appreciated.
September 14, 2009 at 1:25 pm
I'm not sure if it can cross domains or not, but double-take has been working well for us. It replicates at the filesystem level and we use it to replicate our .mdf, .ldf and backup files.
September 14, 2009 at 5:22 pm
I'm not sure if this is an option for you but if you don't need realtime replication, which can sometimes get hung up and delayed anyway if the publisher is lagged, you could look into log shipping.
You could set it up in a way where seperate domains weren't an issue perhaps, this is assuming that the two domains have some type of fast connectivity.
Just a thought.
September 14, 2009 at 7:37 pm
Even i agree with mortalic, logshipping seems the option here.
By the way why are you thinking about mirroring or replication? Does the client want a solution for high availability of their database? If not then why to go this way?
If this is the only way you are thinking to get the backup files across, then you may also have to think about the scenario to restore the database on client site from all these backup files.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply