BackupDir | Working PoC of using FILE_OPEN_FOR_BACKUP_INTENT | Runtime Evironment library

Try changing

Some notes:

• Get out of the habit of using ALLCAPS variable names, leave those as reserved by the shell. One day you'll write PATH=something and then wonder why your script is broken.

• mkdir -p can create parent directories, and will not error if the dir already exists

• store the filenames in an array. Then the shell does not have to duplicate the work, and you don't need to count how many there are: if there are no files, the loop has zero iterations

• if you want to keep the same directory hierarchy in the outputdir, you need to do that by hand.

• use read to get the date parts

• with bash v4.2+, printf can be used instead of calling out to date

  • use magic value "-1" to mean "now".
  • printf '%(%Y-%m-%d)T\n' -1 prints "2021-10-25" (as of the day I write this)

This is, I think, what you want:

Per the docs, dst should be a complete target file name, not a folder. You are passing E:, which is a folder, not a target file name.

It would appear that this is because $BackupDir references a file instead of a folder.

$BackupDir = "C:\SQL Installs\Backups\Full Backups\Sample_full.bak". In order for this to work $BackupDir would need to be something like $BackupDir = "C:\SQL Installs\Backups\Full Backups" After you do this you should be able to make this line work.
$LatestBackupFileName = (Get-ChildItem $BackupDir*.bak | sort LastWriteTime | select -last 1)

The failure is being caused by the fact that the use of the tempnam function actually creates a zero byte file and that is what ZipArchive::CREATE is complaining about.

The solution was to unlink the temporary file created by tempnam before trying to use it. In the example in the question I simply added unlink($temp_file); immediately after $temp_file = tempnam(sys_get_temp_dir(),'AW');.

The first few lines now look like this:

Use HTTP request GET https://www.googleapis.com/drive/v2/files/folderId/children to get children of folder using folder Id

How is the created object of NetworkConnection used in the two codes?

It's just disposed at the end of the block.

I assume that what's happening is that the constructor will fail if the credentials are invalid - so in that case, the properties are never updated. If the constructor succeeds, the properties are updated and then the NetworkConnection is disposed.

One problem with the code as it stands is that the exception isn't caught - it will propagate up into the event loop, which hopefully has an exception handler attached - but it's really not terribly pleasant.

If this were code in a code-base I was maintaining, I'd try to refactor it to something like:

In all of those situations, you could use :execute to concatenate the variable into the command.