Logshipping out of sync

Every once in a while, my logshipping gets out of sync, the backup server
cannot restore. I found out that each time this happens, it is because on
the primary server about 17 tlog files get deleted, rather than the usual 1
file. The maintenance plan is set to keep files for 4 hours. IN the logs, I
see that most of the time, there is a tlog backup, followed by 1 file deleted
- every once in a while, it shows 17 or 18 files deleted, and then the
restore job fails, apparently because the remaining tlogs are out of sync.
I am new to logshipping and really don't know what is causing this - any
help would be greatly appreciated!
Better delete logs on daily basis rather than hourly one. It will save your
life a lot.
In our design we keep last 8 days logs with us. After that only we delete
the logs. We do logshipping manually not using maintenance plan. Our DB size
is 60 GB, whats the size of your DB?
Thanks
Sree
"megabyte" wrote:

> Every once in a while, my logshipping gets out of sync, the backup server
> cannot restore. I found out that each time this happens, it is because on
> the primary server about 17 tlog files get deleted, rather than the usual 1
> file. The maintenance plan is set to keep files for 4 hours. IN the logs, I
> see that most of the time, there is a tlog backup, followed by 1 file deleted
> - every once in a while, it shows 17 or 18 files deleted, and then the
> restore job fails, apparently because the remaining tlogs are out of sync.
> I am new to logshipping and really don't know what is causing this - any
> help would be greatly appreciated!
|||Well, this is a tiny database so far, but it is mission critical. I actually
found the problem: I had a full backup of the DB going to tape overnight -
when that backup worked, there was no problem with the logshipping, but when
the backup got stuck for some reason, it must have kept the DB locked or
something, because that's when everything went out of whack.
Thanks for the reply.
"Sreejith G" wrote:
[vbcol=seagreen]
> Better delete logs on daily basis rather than hourly one. It will save your
> life a lot.
> In our design we keep last 8 days logs with us. After that only we delete
> the logs. We do logshipping manually not using maintenance plan. Our DB size
> is 60 GB, whats the size of your DB?
> Thanks
> Sree
>
> "megabyte" wrote:
|||Yes thats a reason, If backup procedure and logshipping collide it can mess
up things.
Thanks,
Sree
"megabyte" wrote:
[vbcol=seagreen]
> Well, this is a tiny database so far, but it is mission critical. I actually
> found the problem: I had a full backup of the DB going to tape overnight -
> when that backup worked, there was no problem with the logshipping, but when
> the backup got stuck for some reason, it must have kept the DB locked or
> something, because that's when everything went out of whack.
> Thanks for the reply.
> "Sreejith G" wrote:

Logshipping out of sync

Every once in a while, my logshipping gets out of sync, the backup server
cannot restore. I found out that each time this happens, it is because on
the primary server about 17 tlog files get deleted, rather than the usual 1
file. The maintenance plan is set to keep files for 4 hours. IN the logs,
I
see that most of the time, there is a tlog backup, followed by 1 file delete
d
- every once in a while, it shows 17 or 18 files deleted, and then the
restore job fails, apparently because the remaining tlogs are out of sync.
I am new to logshipping and really don't know what is causing this - any
help would be greatly appreciated!Better delete logs on daily basis rather than hourly one. It will save your
life a lot.
In our design we keep last 8 days logs with us. After that only we delete
the logs. We do logshipping manually not using maintenance plan. Our DB size
is 60 GB, whats the size of your DB?
Thanks
Sree
"megabyte" wrote:

> Every once in a while, my logshipping gets out of sync, the backup server
> cannot restore. I found out that each time this happens, it is because on
> the primary server about 17 tlog files get deleted, rather than the usual
1
> file. The maintenance plan is set to keep files for 4 hours. IN the logs
, I
> see that most of the time, there is a tlog backup, followed by 1 file dele
ted
> - every once in a while, it shows 17 or 18 files deleted, and then the
> restore job fails, apparently because the remaining tlogs are out of sync.
> I am new to logshipping and really don't know what is causing this - any
> help would be greatly appreciated!|||Well, this is a tiny database so far, but it is mission critical. I actuall
y
found the problem: I had a full backup of the DB going to tape overnight -
when that backup worked, there was no problem with the logshipping, but when
the backup got stuck for some reason, it must have kept the DB locked or
something, because that's when everything went out of whack.
Thanks for the reply.
"Sreejith G" wrote:
[vbcol=seagreen]
> Better delete logs on daily basis rather than hourly one. It will save you
r
> life a lot.
> In our design we keep last 8 days logs with us. After that only we delete
> the logs. We do logshipping manually not using maintenance plan. Our DB si
ze
> is 60 GB, whats the size of your DB?
> Thanks
> Sree
>
> "megabyte" wrote:
>|||Yes thats a reason, If backup procedure and logshipping collide it can mess
up things.
Thanks,
Sree
"megabyte" wrote:
[vbcol=seagreen]
> Well, this is a tiny database so far, but it is mission critical. I actua
lly
> found the problem: I had a full backup of the DB going to tape overnight -
> when that backup worked, there was no problem with the logshipping, but wh
en
> the backup got stuck for some reason, it must have kept the DB locked or
> something, because that's when everything went out of whack.
> Thanks for the reply.
> "Sreejith G" wrote:
>sql

Logshipping out of sync

Every once in a while, my logshipping gets out of sync, the backup server
cannot restore. I found out that each time this happens, it is because on
the primary server about 17 tlog files get deleted, rather than the usual 1
file. The maintenance plan is set to keep files for 4 hours. IN the logs, I
see that most of the time, there is a tlog backup, followed by 1 file deleted
- every once in a while, it shows 17 or 18 files deleted, and then the
restore job fails, apparently because the remaining tlogs are out of sync.
I am new to logshipping and really don't know what is causing this - any
help would be greatly appreciated!Better delete logs on daily basis rather than hourly one. It will save your
life a lot.
In our design we keep last 8 days logs with us. After that only we delete
the logs. We do logshipping manually not using maintenance plan. Our DB size
is 60 GB, whats the size of your DB?
Thanks
Sree
"megabyte" wrote:
> Every once in a while, my logshipping gets out of sync, the backup server
> cannot restore. I found out that each time this happens, it is because on
> the primary server about 17 tlog files get deleted, rather than the usual 1
> file. The maintenance plan is set to keep files for 4 hours. IN the logs, I
> see that most of the time, there is a tlog backup, followed by 1 file deleted
> - every once in a while, it shows 17 or 18 files deleted, and then the
> restore job fails, apparently because the remaining tlogs are out of sync.
> I am new to logshipping and really don't know what is causing this - any
> help would be greatly appreciated!|||Well, this is a tiny database so far, but it is mission critical. I actually
found the problem: I had a full backup of the DB going to tape overnight -
when that backup worked, there was no problem with the logshipping, but when
the backup got stuck for some reason, it must have kept the DB locked or
something, because that's when everything went out of whack.
Thanks for the reply.
"Sreejith G" wrote:
> Better delete logs on daily basis rather than hourly one. It will save your
> life a lot.
> In our design we keep last 8 days logs with us. After that only we delete
> the logs. We do logshipping manually not using maintenance plan. Our DB size
> is 60 GB, whats the size of your DB?
> Thanks
> Sree
>
> "megabyte" wrote:
> > Every once in a while, my logshipping gets out of sync, the backup server
> > cannot restore. I found out that each time this happens, it is because on
> > the primary server about 17 tlog files get deleted, rather than the usual 1
> > file. The maintenance plan is set to keep files for 4 hours. IN the logs, I
> > see that most of the time, there is a tlog backup, followed by 1 file deleted
> > - every once in a while, it shows 17 or 18 files deleted, and then the
> > restore job fails, apparently because the remaining tlogs are out of sync.
> >
> > I am new to logshipping and really don't know what is causing this - any
> > help would be greatly appreciated!|||Yes thats a reason, If backup procedure and logshipping collide it can mess
up things.
Thanks,
Sree
"megabyte" wrote:
> Well, this is a tiny database so far, but it is mission critical. I actually
> found the problem: I had a full backup of the DB going to tape overnight -
> when that backup worked, there was no problem with the logshipping, but when
> the backup got stuck for some reason, it must have kept the DB locked or
> something, because that's when everything went out of whack.
> Thanks for the reply.
> "Sreejith G" wrote:
> > Better delete logs on daily basis rather than hourly one. It will save your
> > life a lot.
> > In our design we keep last 8 days logs with us. After that only we delete
> > the logs. We do logshipping manually not using maintenance plan. Our DB size
> > is 60 GB, whats the size of your DB?
> >
> > Thanks
> > Sree
> >
> >
> >
> > "megabyte" wrote:
> >
> > > Every once in a while, my logshipping gets out of sync, the backup server
> > > cannot restore. I found out that each time this happens, it is because on
> > > the primary server about 17 tlog files get deleted, rather than the usual 1
> > > file. The maintenance plan is set to keep files for 4 hours. IN the logs, I
> > > see that most of the time, there is a tlog backup, followed by 1 file deleted
> > > - every once in a while, it shows 17 or 18 files deleted, and then the
> > > restore job fails, apparently because the remaining tlogs are out of sync.
> > >
> > > I am new to logshipping and really don't know what is causing this - any
> > > help would be greatly appreciated!

Login migration

Is there an easy way to migrate logins (and passwords) from a Production server over to a DR server and ensure that they stay in sync
Thanks.Chris,
See
HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
http://support.microsoft.com/support/kb/articles/Q246/1/33.ASP
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Chris" <anonymous@.discussions.microsoft.com> wrote in message
news:66BA19F3-B1CC-4875-A0EE-DBCD19DC1F65@.microsoft.com...
> Is there an easy way to migrate logins (and passwords) from a Production
server over to a DR server and ensure that they stay in sync?
> Thanks.