Dual Destination Support

[ryangurn]

So I have been using Laravel-backup for a couple years now with just a single destination filesystem "disk".

I am finally getting around to backing up to multiple locations, and I wanted to check what to expect before moving things to production.

Does anyone happen to know what will happen if you have two disks (one using a local driver, and one using s3), both set as a destination. If the s3 disk becomes unavailable will the backup stored locally still be taken? To what extent does this fail the backup?

[ryangurn]

Just to close the circle, I deployed this in production. When one of the disks is not accessible the disks uploaded prior appear to succeed but I do not know if it will upload to any disks after the one that failed.

Advice (probably no one wants): be sure to configure the disks (backup.backup.destination.disks) in order from highest priority to lowest priority. [I am not sure if there is some sorting on this later on, I am assuming not]. The main reason being, I have observed that backups will be successfully uploaded/transferred/stored to disks if that disk runs before the failing upload.

I do not know if subsequent disks (after a failure) will run, probably depends on the severity of the error (probably not for fatal exceptions, that seem to happen a lot for S3 compatible storage).