Obviously, something to keep in mind is that each bucket will contain a series of FULL backups. Bucket 4: Annual Bucket: Keep Files 365 Days.Bucket 3: Bi-Annual Bucket: Keep Files 180 Days.Bucket 2: Quarterly Bucket: Keep Files 90 Days.Our first step is to set up our new B2 Buckets.
Starwind 27 how to#
While good notes that are up to date are also a critical part of this process, a quick visual set of queues provides an immediate understanding of what data is where and how to get to it. A key is that we replicate to B2 via VTL. The primary reason for that is to keep things simple for anyone to come along and figure out how things were set up if the primary site is lost to a disaster.Ī second reason is that we can gain some control over our GFS configuration and storage requirements that is otherwise not built-in to Veeam v10 at this time. However, we are looking to take a slightly different tact versus using the built-in feature here. Veeam has GFS built-in as a Tape Job: GFS Media Pools However, one thing that is important to us, and to our clients, is Grandfather, Father, and Son (GFS) backups. We Still have a ways to go to get comfortable with working with “Tapes” in Veeam as we’ve not done tape in a _ very_ long time. We set up a BackBlaze B2 account, set up a bucket, and then worked on getting things configured in as demonstrated in the above blog post. Blog Post: Setting Up a Veeam to StarWind Virtual Tape Library Configuration.There are several ways Veeam v10 allows for direct to block storage but limited to Azure and AWS out of the box. We’re in the process of configuring our backups for no more off-site physical rotations.