- Newest
- Most votes
- Most comments
Okay. If there were features available for use but just not visible in the console, they would show in the API documentation. For AWS Backup, the CreateBackupPlan API (https://docs.aws.amazon.com/aws-backup/latest/devguide/API_CreateBackupPlan.html) accepts the AdvancedBackupSettings property (https://docs.aws.amazon.com/aws-backup/latest/devguide/API_AdvancedBackupSetting.html). It doesn't allow for configurability beyond VSS being enabled or not.
A copy-only backup is launched by providing the COPY_ONLY option to the BACKUP DATABASE statement in SQL Server used to start the backup. I don't think it should affect the integration between SQL Server and VSS in any way, so I don't think there's any VSS configuration to change for it to work.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/create-vss-snapshots-ssm.html
CopyOnly (string, optional) If you use the native SQL Server backup in addition to AWS VSS, performing a Copy-only backup prevents AWS VSS from breaking the native differential backup chain. To perform a Copy-only backup operation, set this parameter to True. The default value for this parameter is False, which causes AWS VSS to perform a full backup operation.
In an old home-grown backup solution using SSM documents, Lambda and Step Functions, the value was being set to avoid resetting the backup chain of the native SQL Sever backups that are also being performed in addition to the snapshot backups.
I'm trying to find the same parameter in AWS Backup that exists in the SSM AWSEC2-CreateVssSnapshot document.
Thx! Bryan
Thanks, Leo.
I confirmed through support there was nothing available. It's now officially a feature request.
Cheers! Bryan
Relevant content
- asked 3 years ago
- asked 3 years ago
- asked 4 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 3 years ago
