|
|
Posted by Greg D. Moore \(Strider\) on 02/15/07 21:33
--
--
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com
<danceli@gmail.com> wrote in message
news:1171570480.195547.91540@v33g2000cwv.googlegroups.com...
> Actually we need replicate 3 databases from server A to server B. But
> no idea why replication does not work fine.
>
I'd focus on fixing that.
> So, my boss asked me to do hourly full backup/restore to server B,
> which is kind of relication.
Questions to ask then:
1) What do you do on Server B while the restore is taking place?
2) What do you do if the backup/restore cycle takes more than an hour?
With log-shipping at least you can put the databases on server B into
"read-only" mode between log restores.
>
> Now I still can schedule a job for hourly full backup on server A, but
> i have no idea how to schedule a job for hourly full restore dbs to
> server B.
>
> How to make those hourly .Bak files in server A to server B, and then
> do restore in server B????
What I basically did was create a job on Server A that performed the backup
and then called a job on ServerB to start the restore. (ServerB would look
to the MSDB on ServerA to find the most recentlly performed backup and
location and restore that.)
>
> BTW, thank you so much to keep helping me out!!
>
>
> On Feb 15, 10:48 am, "Greg D. Moore \(Strider\)"
> <mooregr_deletet...@greenms.com> wrote:
>>
>> Generally you have to do the initialbackup/restore yourself.
>>
>> I've written scripts in the past to do a fullbackup/restore but that was
>> a
>> specialized case that I replaced with a log-shipping script the first
>> chance
>> I got.
>>
>> I'm still unclear why you want to go the fullbackup/restore route rather
>> than using log-shipping.
>
>
>
Navigation:
[Reply to this message]
|