I have a backup copy job that runs daily and has a 30 day retention with a gfs policy set for 6 monthly and 1 yearly and is sent to a Linux repository with 365 days of immutability. gfs month 4 backup in the scenario above will not be immutable.ģ. Is this also the case with the capacity tier or are gfs backups that sit on the capacity tier still only immutable for the immutable days set on the capacity extent? i.e. I have read that all gfs backups sent to an archive tier are immutable for the entire lifespan of the gfs backup. The immutability set on the capacity extent is 90 days. This job sends to a SOBR and the SOBR is set to immediately copy all backups to the capacity tier. I have a gfs policy defined with 6 monthly and 1 yearly. I have a backup job set to run daily with 7 days retention and weekly synthetic fulls. On the 8th day is there anything in Veeam that makes the previous week’s full still immutable (due to the fact that the incrementals depend on that full) even though it will be beyond the 7 day immutable set on the repository?Ģ. On the 8th day I should have on the repository the new full for the current week and the previous week’s full and 6 incremental. This job is being sent to a Linux repository that has immutability set to 7 days. I have a backup job set to run once a day with 7 days retention and weekly synthetic fulls.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |