Hi, It would be good but perhaps each task should be created via cronjobs instead of having a script running all the time or one script via one cronjob Working in the enterprise environment for a major bank, we quickly learn that these sort of daily tasks should be split up Kind Regards, Alex On Thu, Nov 10, 2016 at 4:25 AM, <bepi@xxxxxxxx> wrote: > Hi. > > I'm making a script for managing btrfs. > > To perform the scrub, to create and send (even to a remote system) of the backup > snapshot (or for one copy of the current state of the data). > > The script is designed to: > - Be easy to use: > - The preparation is carried out automatically. > - Autodetect of the subvolume mounted. > - Be safe and robust: > - Check that not exist a another btrfs managing already started. > - Subvolume for created and received snapshot are mounted and accessible only > for the time necessary to perform the requested operation. > - Verify that the snapshot and sending snapshot are been executed completely. > - Progressive numbering of the snapshots for identify with certainty > the latest snapshot. > > Are also available command for view the list of snaphost present, command for > delete the snapshots. > > For example: > > btrsfManage SCRUB / > btrsfManage SNAPSHOT / > btrsfManage SEND / /dev/sda1 > btrsfManage SEND / root@xxxxxxxxxxxx/dev/sda1 > btrsfManage SNAPLIST /dev/sda1 > btrsfManage SNAPDEL /dev/sda1 "root-2016-11*" > > You are interested? > > Gdb > > > ---------------------------------------------------- > This mail has been sent using Alpikom webmail system > http://www.alpikom.it > > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
