DIFF backups randomly promoted to FULL using Ola

David Gray 176 Reputation points
2020-11-06T15:50:57.333+00:00

We use DatabaseBackup stored procedure to backup a load of SharePoint databases on a SQL2012 instance into Azure blob storage. We have been doing this for quite a while without any issues however for the last 6 weeks our DIFFs are randomly being promoted to FULL and we cannot see why.

This is the output from the agent step

This is the output from the agent step

BACKUP DATABASE [Database] TO URL = N'https://strorgage.blob.core.windows.net/server/instance/Database/2020/11/diff/Database_FULL_20201105_200000.bak'
WITH NO_CHECKSUM, COMPRESSION, CREDENTIAL = N'password'

DatabaseBackup is from 2019-06-14 so it needs an upgrade to be fair, but it has worked well for over 18 months.

We do not call your code directly as we have small wrapper procedure which builds up the virtual pathname for Azure, but essentially this is
how we call your code.

37988-image.png

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,696 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Tom Phillips 17,731 Reputation points
    2020-11-06T18:25:29.61+00:00

    I suggest you contact Ola directly. Please see: https://ola.hallengren.com/contact.html

    However, you have "@ChangeBackupType=Y", that is what that option does. https://ola.hallengren.com/sql-server-backup.html

    ChangeBackupType
    Change the backup type if a differential or transaction-log backup cannot be performed.

    1 person found this answer helpful.
    0 comments No comments

  2. David Gray 176 Reputation points
    2020-11-08T10:02:55.51+00:00

    Hi,
    We have tried with both Y and N for that value but it does not appear to make any difference. We are randomly getting FULL instead of DIFF
    when there should be no need for a FULL. This is SharePoint data which in 95% of the time had not changed.

    The net result is we have petabytes of backups when we should be getting gigabytes.

    I have contacted Ola but it was late on Friday.

    Thanks


  3. AmeliaGu-MSFT 13,976 Reputation points Microsoft Vendor
    2020-11-09T06:19:03.257+00:00

    Hi @David Gray ,

    Could you please try to use the latest version script?
    If the issue persists, you can open an issue on Ola Hallengren's GitHub.

    Best Regards,
    Amelia


    If the answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
    Users always get connection timeout problem when using multi subnet AG via listener. Especially after failover to another subnet

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.