Skip to main content
commvault.com commvault.com
Solved

Azure SQL bacpac exports not cleaning up

Michael Woodward
Commvault Certified Expert
Forum|alt.badge.img+11

I have a customer that’s running Azure SQL backups, the backup process triggers the export of the database to a bacpac file in a dedicated storage account and then backs this up to a Cloud library.

I was under the impression that the data in the export location would only be transient as part of the backup process, however, looking at the storage account there are bacpac files going back for as long as we have had backups running for these Azure SQL accounts.

Is this the expected behaviour or should the backup process be cleaning up the staging location?

Best answer by Mike Struening RETIRED

Sharing case resolution:

Solution:

- It seems like the older files in the storage account relate to backups during a period where many issues were occurring with that proxy machine.
- Customer cleared the files and will monitor.

View original
Did this answer your question?

5 replies

Emils
Vaulter
Forum|alt.badge.img+12
  • EmilsVaulter
  • Vaulter
  • 146 replies
  • June 27, 2022

Hi @Michael Woodward 

The process should clean up once the backup is completed

the process goes...

  1. create copy of the DB since this will be transactionally consistent
  2. Export copy of the DB to Azure Storage account in .bacpac format
  3. Download that .bacpac file
  4. clean-up

 

We will need to determine what's in the export location and review the logs for any failures during clean-up.

 

I recommend raising a support ticket to review this issue further

Onno van den Berg
Commvault Certified Expert
Forum|alt.badge.img+19

Could it be that the account is lacking permissions? Have you checked the logs? 

Michael Woodward
Commvault Certified Expert
Forum|alt.badge.img+11
  • Michael WoodwardCommvault Certified Expert
  • Author
  • Commvault Certified Expert
  • 79 replies
  • July 1, 2022
Emils wrote:

Hi @Michael Woodward 

The process should clean up once the backup is completed

the process goes...

  1. create copy of the DB since this will be transactionally consistent
  2. Export copy of the DB to Azure Storage account in .bacpac format
  3. Download that .bacpac file
  4. clean-up

 

We will need to determine what's in the export location and review the logs for any failures during clean-up.

 

I recommend raising a support ticket to review this issue further



Thanks for this - it’s how I expected it to work as well, the .bacpac files that have been left behind are relatively old now and there’s no job logs that show me anything, logged a support ticket to confirm why this may be happening and if we can safely delete the files.

Mike Struening
Vaulter
Forum|alt.badge.img+23

@Michael Woodward , can you share the case number so I can track it?

https://www.linkedin.com/in/michael-struening
Mike Struening
Vaulter
Forum|alt.badge.img+23

Sharing case resolution:

Solution:

- It seems like the older files in the storage account relate to backups during a period where many issues were occurring with that proxy machine.
- Customer cleared the files and will monitor.

https://www.linkedin.com/in/michael-struening

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings