Re: Log Shipping....

I have no idea what environment you have. Is it the log backups that are
140GB in size of the transaction log itself? If it is the transaction log
file then you most likely have one of two conditions. Either you did not
start with a valid FULL backup or you have an open transaction that is
preventing the log from truncating. What does DBCC OPENTRAN() show for that
db?

--
Andrew J. Kelly SQL MVP

"Rogers" <naissani@xxxxxxxxxxx> wrote in message
news:%23XfwtzdfHHA.3648@xxxxxxxxxxxxxxxxxxxxxxx
There is a log shipping environment and I can't change any thing, if you
can let me know if change the intervel time from 15 to 20 mins, will that
helpful ?

Thanks

"Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx> wrote in message
news:OZPoY9SfHHA.4872@xxxxxxxxxxxxxxxxxxxxxxx
What are you doing? Are you backing up tot he same log file (device)
each time? If so stop that:). Backup to a different file each time by
adding a timestamp to the file name. Then the backups should be
relatively small and you can delete them after a specified time period.

--
Andrew J. Kelly SQL MVP

"Rogers" <naissani@xxxxxxxxxxx> wrote in message
news:%23nibvnRfHHA.1456@xxxxxxxxxxxxxxxxxxxxxxx
Log Shipping....

In my organization we had implemented Disaster Recovery (Log Shipping)
but Log File size is increasing gradually (140 GB) and Data File size is
20 GB, I am just wondering log file size should be trancate once it will
ship to destination Server,

FYI, log ship every after 15 mins.

I would appreciate if any one can guide me how log could be shrink
automatically.

Thanks







.

Relevant Pages

  • RE: Log Shipping and Full Backup Frequency. Advice?
    ... The transaction log is different; it is a recording of database actions. ... And, if you restore from any of these, you only get that state. ... This is not the case with the transaction log or its backups. ...
    (microsoft.public.sqlserver.server)
  • Re: Transaction Log Questions
    ... > that once they got full, there would be a checkpoint and the logs would ... This is not how SQL Server work. ... I'd complement that with SQL Server backups at least database backups and possibly also ... transaction log backups. ...
    (microsoft.public.sqlserver.server)
  • Re: Large transaction log causing write performance hit
    ... model or consider moving the transaction log to a separate disk where there ... A good recovery model depends on whether you want up to the minute restores ... The frequent transaction log backups or truncations will keep the size down ... then consider setting your database ...
    (microsoft.public.sqlserver.server)
  • Re: Large transaction log causing write performance hit
    ... >transaction log on a mirrored set, ... >A good recovery model depends on whether you want up to ... >The frequent transaction log backups or truncations will ... setting your database ...
    (microsoft.public.sqlserver.server)
  • Re: how can i restore if my dropped a wrong table and recreated it?
    ... If you do regular database and transaction log backups, you can now backup the transaction log and then use ... your latest db backup and then all subsequent backups to restore up until just before that operations. ...
    (microsoft.public.sqlserver.server)
Quantcast