HCHTech
Well-Known Member
- Reaction score
- 4,210
- Location
- Pittsburgh, PA - USA
I'm using Cloudberry & B2, although this question would apply with any backup software copying data to any online storage where both places allow you to keep versions of files.
If you are doing this, how do you setup versioning? Both the local software and the online storage have versioning settings. So if I set B2 to keep 3 months of versions for each file, and set Cloudberry to keep 3 months of versions, then am I wasting resources? Should the settings line up or not?
I have Cloudberry setup to do what they call a "hybrid" backup. It copies everything to a local external drive first, then copies that external drive's contents to the B2 cloud storage. This is all as a part of a single backup job. The file storage on the external drive looks like this:
G:\Server\D$\Shared\Clients\ABC\something.doc$\20171115223051\something.doc
This is the 11/15/17 version of a file, which was backed up at 22:30:51. Then if that file is changed on 11/20, it creates the following file in that night's backup.
G:\server\D$\Shared\clients\ABC\something.doc$\20171120221535\something.doc
To B2 (it seems), these would both be seen as new files on the date they were created. Because B2 doesn't know or care about how Cloudberry does things, I expect that B2 does not know that the second file is a version of the first. So that means that none of the files B2 sees will ever be modified (because Cloudberry just creates a new file in a new directory when modifications occur). And THAT means, from B2's perspective, a file will have to be deleted by Cloudberry on the local drive (because it was modified currently and some versions grow to be older than whatever versioning setting I'm using for Cloudberry) before it can even start aging towards deletion on the B2 calendar.
If this is all true, then the a version of a modified file won't go away until the SUM of the two versioning periods. If I have 3 months set on Cloudberry and 3 months set on B2, then a file will live on both the local backup drive and on B2 for the first 3 months, then it will live only on B2 for the second 3 months - for a total of 6 months life.
On the other hand, maybe B2 IS aware of how Cloudberry stores stuff and knows that the two files above are versions of the same file, so it would delete the first one once it gets more than 3 months old. My head hurts.
Does anyone know how this really works?
If you are doing this, how do you setup versioning? Both the local software and the online storage have versioning settings. So if I set B2 to keep 3 months of versions for each file, and set Cloudberry to keep 3 months of versions, then am I wasting resources? Should the settings line up or not?
I have Cloudberry setup to do what they call a "hybrid" backup. It copies everything to a local external drive first, then copies that external drive's contents to the B2 cloud storage. This is all as a part of a single backup job. The file storage on the external drive looks like this:
G:\Server\D$\Shared\Clients\ABC\something.doc$\20171115223051\something.doc
This is the 11/15/17 version of a file, which was backed up at 22:30:51. Then if that file is changed on 11/20, it creates the following file in that night's backup.
G:\server\D$\Shared\clients\ABC\something.doc$\20171120221535\something.doc
To B2 (it seems), these would both be seen as new files on the date they were created. Because B2 doesn't know or care about how Cloudberry does things, I expect that B2 does not know that the second file is a version of the first. So that means that none of the files B2 sees will ever be modified (because Cloudberry just creates a new file in a new directory when modifications occur). And THAT means, from B2's perspective, a file will have to be deleted by Cloudberry on the local drive (because it was modified currently and some versions grow to be older than whatever versioning setting I'm using for Cloudberry) before it can even start aging towards deletion on the B2 calendar.
If this is all true, then the a version of a modified file won't go away until the SUM of the two versioning periods. If I have 3 months set on Cloudberry and 3 months set on B2, then a file will live on both the local backup drive and on B2 for the first 3 months, then it will live only on B2 for the second 3 months - for a total of 6 months life.
On the other hand, maybe B2 IS aware of how Cloudberry stores stuff and knows that the two files above are versions of the same file, so it would delete the first one once it gets more than 3 months old. My head hurts.
Does anyone know how this really works?
