>Writing your own backup routine? I'm sure you have your reasons, but, just to share this great free tool I use to perform automatic, or on-demand scheduled backup of Sql Server.
>
>https://sqlbackupandftp.com/
>
>
>It places the backup files on any on local or networkfolder, and will also upload to an FTP folder if you define the login and destination.
>
>It performs bull backups and also can configure incremental backups between full backups. All per a schedule.
>
>I LOVE THIS TOOL!
>
>I have reliably restored a database from a full backup+incremental backup to get some data back from rows I had accidentally. So, I know it works.

Thanks for the reference

We use this approach because this is integrated into our robots which log everything into the database as well as a lot of other automated procedures. There is something in that approach that causes the backup procedure to be very long, such as about 12 times it would take to do the same command from SSMS. I will try the suggested approach to execute this as a query command instead, but doing this I will loose the direct integration during the backup so as being able to show the progress bar, etc.