
If no instance is passed it calculates the schedules for all the instances. * reschedule instance/s -> Calculates a new schedule for the specified instance.
YOUTUBE BACKUP SCHEDULER MANUAL
* manual instance/s -> executes the manual backup of the specified instance even if it's not planned for today. * run -> executes the backups planned for today * dry-run -> simulates the backup operations but doesn't do anything.


* list-$xxx instance/s -> using one of the following words in the place of $xxx you can ask to the scheduler to list what is planned for today (list-today), tomorrow (list-tomorrow), wednesday (list-wednestay), and so on. If no instance is specified it lists them all. * list instance/s -> lists the status of the instances/instances specified: last backup, policy, next planned backup. * help -> Prints the usage of the command The possible commands for gnt-bkscheduler.sh are: The scheduler can be also used to list and check the status of the schedules and execute manual backups. In this way it will only reschedule the selected instance without modify the already programmed schedules.įor exmaple: gnt-bkscheduler.sh reschedule my.daily.instance Scheduler Commands if you need to change the schedule of some instances just add to it the appropriate and then run again the scheduler in reschedule mode adding the modified instance as parameter. NOTE: If you do not set any tag or OS parameter for your machines it will assume that you want to do weekly backups in cold mode for the instances. Once that you accepted the schedule you're done, the scheduler will execute the backups as it promised. This command will run for a while depending by the number of VM on your cluster and in the end it will show you the calculated backups plan asking you to confirm the scheduling. Then you have to "generate" the new backup plan by running a single command on the master node: This file will run the scheduler everyday at the 1:00 AM. You need to copy the ganeti-bkscheduler crontab file into your "/etc/cron.d" directory of all the master-candidate nodes of your cluster. * instances that needs monthly backups are made every sunday with the same logic of the weekly approach. (for example if you have 14 instances to backup weekly, it will backup 2 instances per day) * instances that needs weekly backups are made a few per day in order to split up the job in 7 days. * instances that needs daily backups are made every day. The scheduler can plan daily, weekly and monthly backups following this logic: The name of the tar file will be backup-$(date +%Y-%m-%d).tar.gz ( new Backup scheduler is a command-line tool that will help you to automatically plan and execute the daily backups of your precious Virtual Machines. Tar czpvf /home/user/backup-$(date +%Y-%m-%d).tar.gz /opt/lamppThis above command will tar the entire content of the directory /opt/lampp and put the tar file into /home/user/ The CRON is set to 1400 hour (2:00 p.m.) 5 th day of week (Friday).

* 14 * * 5 root tar czpvf /home/user/backup-$(date +%Y-%m-%d).tar.gz /opt/lampp

Each section is delimited by a single blank space, but the final section may have spaces within it.
YOUTUBE BACKUP SCHEDULER PASSWORD
