1/31/2024 0 Comments Chronosync archive items![]() ![]() I've been running versioned backups for almost two years to an external backup disks and since about 1.5 months I also do NAS-to-NAS. Unchanged files are only a link to the original file in each additional version so occupy no additional storage capacity. Paul2018 wrote:Btw I had thought that some form of versioning might do the trick but QNAP support claims that would create a lot of wasteful redundancy in the backup.Hybrid Backup Sync versioning only use additional storage capacity for files that have changed or been deleted from the previous version. I’m pretty green and it’s very important I get this right and weigh all my options, does anyone care to weigh in with suggestions/opinions? Btw I had thought that some form of versioning might do the trick but QNAP support claims that would create a lot of wasteful redundancy in the backup. We’re working with QNAP support and they are proposing a conjunction of Snapshot Replication jobs, I’m hoping to test drive this in a day or two. Finally the primary NAS (1685) is formatted Static for performance reasons, and the backup (1635ax) is formatted Thick. For this reason there should be few instances of modified files. our operation it is important to add that when a (video) project folder is submitted to (deposited on) the primary NAS archive, it is finished package and should remain unchanged. Our archive is now 30TB and lives on two QNAPs with a capacity of 100TB each, so we can’t casually build up a lot of duplicates as our archive is growing rapidly. This would be a hedge against a file that was changed negatively (human error, malfeasance, bit-rot, virus etc) overwriting and destroying the only good backup copy. ![]() I need to draw a distinction in the way the backup software handles new material *added* to the archive -vs- files already in the archive that have been modified,įor each overnight backup I want the system to do an inventory that allows a faithful copy of new files/folders… *but* in the case of existing files that have been modified… the original file would be set aside/preserved on the backup somehow. The kind of backup regime I need involves setting up a relationship between a ‘primary’ archive (local NAS) directory and its ‘twin’ on the remote NAS backup which should mirror the original directory and additions made to it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |