Prev: setting up Trans repl TO clustered servers
Next: SQL Server 2005 : define a transactional replication where delete instructions are not replicated
From: Marco on 24 Jul 2008 04:03
Hi,

I have implemented a system with 2 SQL 2000 servers with a DB for
archiving of production data of a manufacturing plant; the DB is merge
replicated between the 2 servers.
Now, the technical personnel of the plant has requested me a guide for
the management of backup of DB and the restore of each machine in case
of crash/failure of one of them. I don't know where to start, so if
anyone can give me any help or any suggestion, giving a step to step
procedure for this I would appreciate.

Thanks.
Regards.
From: Hilary Cotter on 24 Jul 2008 08:37
1) script out all publications and subscriptions on a regular basis.
This can be automated.
2) backup up the master, msdb, distribution and publication databases.
Do full backups nightly and tranasactional log backups every hour or
so.
3) when you restore you can use the keep_replication switch on the
last restore of your tlogs. You will also have to restore all system
databases on the new server, rename the new server with the source
server name and reboot.
Replication should pick up where it left off.

On Jul 24, 4:03 am, Marco <pesk...(a)tin.it> wrote:
> Hi,
>
> I have implemented a system with 2 SQL 2000 servers with a DB for
> archiving of production data of a manufacturing plant; the DB is merge
> replicated between the 2 servers.
> Now, the technical personnel of the plant has requested me a guide for
> the management of backup of DB and the restore of each machine in case
> of crash/failure of one of them. I don't know where to start, so if
> anyone can give me any help or any suggestion, giving a step to step
> procedure for this I would appreciate.
>
> Thanks.
> Regards.

From: Marco on 24 Jul 2008 08:54
On 24 Lug, 14:37, Hilary Cotter <hilary.cot...(a)gmail.com> wrote:
> 1) script out all publications and subscriptions on a regular basis.
> This can be automated.
> 2) backup up the master, msdb, distribution and publication databases.
> Do full backups nightly and tranasactional log backups every hour or
> so.
> 3) when you restore you can use the keep_replication switch on the
> last restore of your tlogs. You will also have to restore all system
> databases on the new server, rename the new server with the source
> server name and reboot.
> Replication should pick up where it left off.
>
> On Jul 24, 4:03 am, Marco <pesk...(a)tin.it> wrote:
>
>
>
> > Hi,
>
> > I have implemented a system with 2 SQL 2000 servers with a DB for
> > archiving of production data of a manufacturing plant; the DB is merge
> > replicated between the 2 servers.
> > Now, the technical personnel of the plant has requested me a guide for
> > the management of backup of DB and the restore of each machine in case
> > of crash/failure of one of them. I don't know where to start, so if
> > anyone can give me any help or any suggestion, giving a step to step
> > procedure for this I would appreciate.
>
> > Thanks.
> > Regards.- Nascondi testo citato
>
> - Mostra testo citato

Hi Hilary,

thanks for your answer.
I will follow your suggestions.

Bye.
 | 
Pages: 1
Prev: setting up Trans repl TO clustered servers
Next: SQL Server 2005 : define a transactional replication where delete instructions are not replicated