{"id":105497,"date":"2022-11-07T21:36:54","date_gmt":"2022-11-07T19:36:54","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/predlozhen-mehanizm-blksnap-dlya-sozdaniya-snapshotov-blochnyh-ustrojstv-v-linux"},"modified":"2022-11-07T21:36:54","modified_gmt":"2022-11-07T19:36:54","slug":"predlozhen-mehanizm-blksnap-dlya-sozdaniya-snapshotov-blochnyh-ustrojstv-v-linux","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/predlozhen-mehanizm-blksnap-dlya-sozdaniya-snapshotov-blochnyh-ustrojstv-v-linux","title":{"rendered":"The blksnap mechanism is proposed for creating snapshots of block devices in Linux.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Veeam, a company that develops backup and disaster recovery software, has proposed a blksnap module for inclusion in the Linux kernel, implementing a mechanism for creating snapshots of block devices and tracking changes in block devices. A command-line utility, blksnap, and the library blksnap.so have been prepared for working with snapshots, allowing user space interaction with the kernel module through ioctl calls. <\/p>\n
The purpose of creating the module is to organize the backup of drives and virtual disks without interrupting operations \u2014 the module allows you to capture the current state of the entire block device in a snapshot, providing an isolated snapshot for backup that is independent of ongoing changes. An important feature of blksnap is the ability to create snapshots simultaneously for multiple block devices, which not only ensures data integrity at the block device level but also achieves consistency of the state of different block devices in the backup. <\/p>\n
To track changes in the block device subsystem (bdev), the ability to attach filters for intercepting input\/output requests has been added. Blksnap implements a filter that intercepts write requests, reads the old value, and saves it in a separate list of changes that defines the state of the snapshot. With this approach, the logic of interacting with the block device remains unchanged; writes to the original block device are made as is, regardless of the snapshots, which eliminates the possibility of data corruption and allows avoiding issues even in the event of unpredictable critical errors in blksnap and overflow of space allocated for changes. <\/p>\n
The module also allows you to determine which blocks have changed in the time frame between the last and any previous snapshot, which can be useful for implementing incremental backups. To retain changes relative to the snapshot state, any range of sectors on a block device can be allocated, enabling changes to be saved in separate files within the filesystem on block devices. The size of the area for storing changes can be increased at any time, even after a snapshot has been created. <\/p>\n
Blksnap is based on the code of the veeamsnap module, which is part of the Veeam Agent for Linux product, but reworked with consideration for its delivery as part of the main Linux kernel. The conceptual difference between blksnap and veeamsnap is the involvement of a filter system attached to the block device instead of a separate bdevfilter component that intercepts input\/output. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"