Post reply

DBATools Invoke-DbaDbLogShipping doesn't create the secondary database correct

  • May 4, 2022 at 10:59 am

    #4026527

    Hi

    I've been using DBATools more lately and encountered an issue with the Invoke-DbaDbLogShipping command. Before I raise it as a potential issue with them I wanted to see if anyone could spot something I might have done incorrectly.

    I have rechecked permissions on the shared folders multiple times.

    Command Run:

    $params = @{

    SourceSqlInstance = 'sql01'

    DestinationSqlInstance = 'sql02'

    Database = 'Database92'

    SharedPath= '\\sql01\_logshipping'

    GenerateFullBackup = $true

    CopyDestinationFolder = '\\sql02\_logshippingdest'

    Force = $true

    }

    Invoke-DbaDbLogShipping @params

     

    Essentially it sets log shipping up on the database, takes a full backup and restores it on the secondary instance but doesn't seem to register any of the details for the secondary in the system tables on the primary. So although it appears at first to have succeeded it won't actually copy and restore logs until I manually go into properties>transaction log shipping for the database, delete the secondary and re-add it.

    The DB does not show up on the log shipping report on the secondary either.

    All advice very welcome 🙂

    Many thanks.

     

    EDIT - Think it was the force parameter causing the issue. Changed it to false after reading about something else in the DBATools slack channel and that seems to have corrected the behaviour.

    • This topic was modified 2 years, 7 months ago by  alexhdavies.

    Attachments:
    You must be logged in to view attached files.

  • May 5, 2022 at 11:10 am

    #4027242

    Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply