How to extend backup Retention for FSx
I am trying to extend the retention of already made backups in FSx for Windows. AWS Backup can have unlimited retention but in the console for FSx you can only do a maximum of 90 days. For existing backups can they be copied and then categorized as a user-initiated backup and then use the Custom Backup schedule 1 extend the retention based on whats defined? Importing the Automatic backups defined in the FSx console would be ideal but I have not found a way to do this.
1 - https://docs.aws.amazon.com/fsx/latest/WindowsGuide/additional-info.html
Automatic backups cannot be recategorized to user-initiated backups by copying. However, you can create a custom backup plan in AWS Backup and assign a specific resource ID to include the copied backup in the new plan. Going forward, you can create custom backup schedules with retention periods of longer than 90 days.
Relevant questions
tagging to AWS FSx windows file system
Accepted Answerasked 3 months agoAmazon FSx for Windows File Server Now Supports AWS CloudFormation
Accepted Answerasked 3 years agoHow to extend backup Retention for FSx
asked 12 days agofsx for windows - billing model
asked 2 months agoCost of FSx backup
Accepted Answerasked 2 years agoHow do I access Freespace/usedspace/totalspace stats on my FSx filesystem?
asked 3 years agoSAP on Windows in HA using Amazon FSx for Windows File Server - CNAME for SAPGlobalHost share
Accepted Answerasked 2 years agoMigrate data using windows deduplication function to FSx(windows)
asked 2 years agoIndividual file to be restore from FSX file system
Accepted Answerasked 4 months agoFile System (FS) stuck with DELETING status in AWS FSX ONTAP
asked 6 months ago
We tried this out in the AWS Backup console and while you can assign specific resource IDs to the backup plan those are limited to existing filesystems and not backups. Is the suggestion here to restore the file system from the older automatic backup and then have AWS backup make one automatically with the older point? I think that can work but will not scale well as we have a few older backups that are aging out that we need to keep for compliance.