![]() ![]() When HP runs, and the maximum number of snapshot backup versions has been exceeded, the deletion of the snapshot will remove the snapshot backup "version" from the archive (but not necessarily the data files it represents). When you “Enable backup rotation”, you allow an automatic deletion of old snapshots in HB, depending on your rules you set (eg Smart cycle, custom, from the earliest). If there are duplicate photos across your volume, again only one copy is stored in the backup archive because the chunks are the same. If no file has been touched since the last backup, “the snapshot version is the only thing added to the backup archive” because all the chunks are the same. Finally, the snapshot version is added to the backup archive. On future HP backups (and snapshots) versions, HP checks to see if that chunk has already been put in the data store. HP goes through all the files and converts them to segmented chunks (a maximum block size). ![]() In the snapshot backup it lists all of files to be backed up and all of the metadata (size, permissions, etc) with them. When a HP backup is made, it starts by creating a snapshot backup version (and copies every file into the backup). Running HP will create a list of all the files (and properties) in a “snapshot”, and, creates a list of data chunks (that comprise the actual file’s physical data). Intro (and thanks to GW2_Jedi_Master) Hyper Backup (HP) is said to be an Object Oriented and incremental type of backup. I don’t want to find I’ve made a mistake months or years down the line! And, as after several days, I couldn’t find a guide that gives me the detailed explanation I wanted. I am trying to make sure I’ve understood basic backup knowledge on Hyper Backup rotation versions and snapshots. HUGE apologies if anything below is incorrect.
0 Comments
Leave a Reply. |