Create weekly synthetics, so the inactive chain or inactive vbk/vib can start to move to the cloud after 30 days. Have operational window on capacity tier to 30 days. How to configure the gfs to make sure the local repository (performance tier) always has enough space to accommodate the new backups.ġ. The plan is to add capacity tier and push backup older than 30 days to the cloud. The storage capacity is reaching exhaustion. vbk files.Īnd I'll have 30 restore points from the local backup job in the repository. vbk remain at any given time.įor yearly backup - it will synthesize a full backup from the 12 monthly flagged GFS backups? or will it do an active full backup? at the end of the year I'll have 1. In the next cycle starting the next year the previous chain will start to get pruned? As new. So every month we'll get a monthly restore point. The best option is GFS here, but I am not sure I understand its workings correctly.įor monthly backup - it will synthesize a full backup at the end of the month and flag it (30 retention points will be available as per current backup job configuration). Job retention: 30 restore points, incremental.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |