When you make a scheduled appliance backup task with the utility, the task must specify the same Run As user as the one you're logged in with when you run the tool. Otherwise, your encrypted passwords for vCenter and the MA will be unavailable. You will see errors like this in the Appliance Backup logs:
00-00-29-AM - Error Updating Status with Management Appliance - Received an unhandled exception of type System.Management.Automation.PSInvalidCastException. Cannot convert the "" value of type "System.String" to type "System.Management.Automation.PSCredential".
At C:\downloads\backuputility\powershell\MCPBackup.ps1:1082 char:68
+ $passwordbackMA = Get-Content $CredFileMA | ConvertTo-SecureString <<<<
Exception:
Key not valid for use in specified state.
At C:\downloads\backuputility\powershell\MCPBackup.ps1:1083 char:28
+ $credentialMA = New-Object <<<< System.Management.Automation.PsCredential("Administrator",$passwordbackMA)
Exception:
Exception calling ".ctor" with "2" argument(s): "Cannot process argument because the value of argument "password" is null. Change the value of argument "password" to a non-null value."
At C:\downloads\backuputility\powershell\MCPBackup.ps1:1084 char:127
+ $MyUDAdminPassword = [Runtime.InteropServices.Marshal]::PtrToStringAuto([Runtime.InteropServices.Marshal]::SecureStringToBSTR <<<< ($credentialMA.Password))
Exception:
Exception calling "SecureStringToBSTR" with "1" argument(s): "Value cannot be null.
Parameter name: s"
At C:\downloads\backuputility\powershell\MCPBackup.ps1:1086 char:147
+ $global:credMA = New-Object System.Management.Automation.PSCredential -argumentlist "Administrator", (ConvertTo-SecureString -AsPlainText -String <<<< $MAPW -Force)
Exception:
Cannot bind argument to parameter 'String' because it is an empty string.
And pretty much every function in the script will have failed with those or similar functions. To resolve this, login as the Run As user and re-run the tool, specifying and saving both passwords (VC and MA). Then the next scheduled run will be fine.
Testing a live backup (not a scheduled one) will not test this properly. You need to have this run as a scheduled task. But you can always change the schedule to run "in 2 minutes" rather than waiting for the next run at midnight.