• anthony.green (8/6/2012)


    If you have such a big log after 30 minutes, then change it to 15 minutes.

    You can shrink the log in full recovery, but you will have to wait until the log reuse description is set to nothing, which in full recovery you have to be pretty quick.

    select log_reuse_wait_desc from sys.databases where name = ''

    You can also take a manual backup of the log in Logshipping, the ONLY[/i] caviat, is that the TRN file must go into the same directory which is used in logshipping so that it can be copied and restored as normal.

    "If you have such a big log after 30 minutes, then change it to 15 minutes."

    I dont understand what you mean.

    My ldf file are big, and I think it take bigger maybe everyweek, perhaps month ? It's no every 30mn when my logshipping running.

    The shrink option have every time we tried with a lot of option "truncate, truncate only etc etc" break the logshipping sequence.

    "You can also take a manual backup of the log in Logshipping, the ONLY[/i] caviat, is that the TRN file must go into the same directory which is used in logshipping so that it can be copied and restored as normal"

    I tried also to made a manual backup of the log, and then it's the error message 2 post away. But I will tried to set up into the logshipping folder... maybe it's the issu!

    I run to test it, and I come back here.