running back up logs to a different server to maintain a copy

[Tom]

I am going to use the backup and restore function to copy data from one server to the other server. We would like to keep the servers in sink at this point (not instantaneously but update the server say once a day) and I would like to do this by using the back up transaction logs. I have tried to back up from individual transaction logs but in also seems to restore the full database also. The database is roughly 6 gig and transaction logs are about 25- 50 meg. I really do not want to have to restore the database every time.

I know I could set up replication but this has been more of a pain administering this on a daily basis. I would like to do a schedule and forget type of thing. This is going to be done on 6.5.

Any suggestions would be helpful

Thanks

TS

[Craig]

On 12/28/98 2:03:01 PM, Tom wrote:
> I am going to use the backup and restore function to copy data from one
> server to the other server. We would like to keep the servers in sink at
> this point (not instantaneously but update the server say once a day) and I
> would like to do this by using the back up transaction logs. I have tried
> to back up from individual transaction logs but in also seems to restore
> the full database also. The database is roughly 6 gig and transaction logs
> are about 25- 50 meg. I really do not want to have to restore the database
> every time.

I know I could set up replication but this has been more of
> a pain administering this on a daily basis. I would like to do a schedule
> and forget type of thing. This is going to be done on 6.5.

Any
> suggestions would be helpful

Thanks

TS

++++++++

TS,

I do this on multiple servers at my shop.

The number of full database restores to your standby environment is dictated by how often you backup the database at your primary site. If you back up daily, you must restore daily.

If you do a full backup weekly and dump the transaction logs in between, then take the database backup and restore to your standby. Then make sure the 'no checkpoint on recovery' flag is set on your database at your standby site. After the full database load is complete, you can then apply all of your transaction log backups from the primary site up until you did your next full database backup.

Let me know if you need more help..........

[Paul Ross]

On 12/29/98 6:25:04 AM, Craig wrote:
> On 12/28/98 2:03:01 PM, Tom wrote:
> I am going to use the backup and
> restore function to copy data from one
> server to the other server. We
> would like to keep the servers in sink at
> this point (not
> instantaneously but update the server say once a day) and I
> would like
> to do this by using the back up transaction logs. I have tried
> to back
> up from individual transaction logs but in also seems to restore
> the
> full database also. The database is roughly 6 gig and transaction logs
>
> are about 25- 50 meg. I really do not want to have to restore the database
>
> every time.

I know I could set up replication but this has been more
> of
> a pain administering this on a daily basis. I would like to do a
> schedule
> and forget type of thing. This is going to be done on
> 6.5.

Any
> suggestions would be
> helpful

Thanks

TS

++++++++

TS,

I do this on multiple servers
> at my shop.

The number of full database restores to your standby
> environment is dictated by how often you backup the database at your
> primary site. If you back up daily, you must restore daily.

If you do a
> full backup weekly and dump the transaction logs in between, then take the
> database backup and restore to your standby. Then make sure the 'no
> checkpoint on recovery' flag is set on your database at your standby
> site. After the full database load is complete, you can then apply all of
> your transaction log backups from the primary site up until you did your
> next full database backup.

Let me know if you need more help..........

Craig,

You should only have to restore the full database once, then you can just apply log dumps regardless of how many full database dumps you make (provided that you don't ever truncate the log or run non-logged BCP).

Paul

[Craig]

On 12/30/98 9:55:43 AM, Paul Ross wrote:
> On 12/29/98 6:25:04 AM, Craig wrote:
> On 12/28/98 2:03:01 PM, Tom wrote:
>
> I am going to use the backup and
> restore function to copy data from
> one
> server to the other server. We
> would like to keep the servers
> in sink at
> this point (not
> instantaneously but update the server
> say once a day) and I
> would like
> to do this by using the back up
> transaction logs. I have tried
> to back
> up from individual
> transaction logs but in also seems to restore
> the
> full database
> also. The database is roughly 6 gig and transaction logs
>
> are about
> 25- 50 meg. I really do not want to have to restore the database
>
>
> every time.

I know I could set up replication but this has been more
>
> of
> a pain administering this on a daily basis. I would like to do a
>
> schedule
> and forget type of thing. This is going to be done on
>
> 6.5.

Any
> suggestions would be
>
> helpful

Thanks

TS

++++++++

TS,

I do this on multiple servers
>
> at my shop.

The number of full database restores to your standby
>
> environment is dictated by how often you backup the database at your
>
> primary site. If you back up daily, you must restore daily.

If you do a
>
> full backup weekly and dump the transaction logs in between, then take
> the
> database backup and restore to your standby. Then make sure the
> 'no
> checkpoint on recovery' flag is set on your database at
> your standby
> site. After the full database load is complete, you can
> then apply all of
> your transaction log backups from the primary site up
> until you did your
> next full database backup.

Let me know if you
> need more help..........

Craig,

You should only have to restore the
> full database once, then you can just apply log dumps regardless of how
> many full database dumps you make (provided that you don't ever
> truncate the log or run non-logged BCP).

Paul

++++++++++
Paul,

You should only have to do it once, but that is not the way it works. When the database dump occurs on your primary database, a record is written indicating that a full backup was done to the transaction log. When you try to apply that transaction log dump to the remote server without first applying the dump, you get the out of sequence message.

If this is not the case (and I believe it is), then he should try it your way first and see if it works.