Skip to main content
Database Administrators

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • I'm curious what mechanism do you use to append? i.e. what is the content of the SQL Agent job that does this? (i.e. the T-SQL being used). Do you get an error when trying to append? All I could see was that Append might need a different API (that mightn't be supported by SQL Agent) Commented Sep 17, 2023 at 23:20
  • @Nick.Mc The filename for the t-log backup contains the date, and is generated as the final step of the nightly full backup job "WITH INIT". Then, the hourly job uses the same filename format (meaning the filename will be the same until the date changes) but using "WITH NOINIT". When backing up to disk, since NOINIT is specified and the backup file already exists, it will append. When backing up to blob storage I get: The file [blob url to file] exists on the remote endpoint, and WITH FORMAT was not specified. Backup cannot proceed. BACKUP LOG is terminating abnormally. Commented Sep 18, 2023 at 13:23
  • Reading around, apparently this might work if you pre create an empty append blob beforehand. This might have some useful powershell that will let you do it 4sysops.com/archives/… Commented Sep 18, 2023 at 23:51
  • 1
    @Nick.Mc Thanks, that looked promising. I tried creating the empty blob in advance as an Append Blob, and could see it in the storage explorer listed as an Append Blob but unfortunately when I try to write the t-log to it, I still get the same errror, "The file t-log-test.bak exists on the remote endpoint, and WITH FORMAT was not specified. Backup cannot proceed." I have gone back to writing the hourly t-log backup to disk for now. Commented Sep 25, 2023 at 23:44