User:Pat

Good to know

ASCII generator

http://www.network-science.de/ascii/ Font: slant

         __                                    __                __
   _____/ /_____  ____  ___  __  __      _____/ /___  __  ______/ /
  / ___/ __/ __ \/ __ \/ _ \/ / / /_____/ ___/ / __ \/ / / / __  / 
 (__  ) /_/ /_/ / / / /  __/ /_/ /_____/ /__/ / /_/ / /_/ / /_/ /  
/____/\__/\____/_/ /_/\___/\__, /      \___/_/\____/\__,_/\__,_/   
                          /____/                                   

Stoney Cloud

State of the art

• prov-backup-rsnapshot
  • The prov-backup-rsnapshot deamon is finished. There is only one thing left to do which is to create the bash script which creates the chroot environment, see prov-backup-rsnapshot#ToDos
  • The daemon can be installed and tested according to Backup_(Server_Setup)#prov-backup-rsnapshot (don't forget Backup_(Server_Setup)#prov-backup-rsnapshot)
• rsnapshot
  • The script which executes the daily, weekly and monthly rsnapshots is finished. It requires a parameter (--interval) with the appropriate name and then executes for all users (which have set the corresponding value in the LDAP) the appropriate command. You can also pass "hourly" or "yearly" with the --interval parameter.
  • The cronjobs are set up for daily, weekly and monthly rsnapshots
  • On the test server, the command is only printed, because rsnapshot is not yet installed. If you install the script according to Backup_(Server_Setup)#rsnapshot, the script will execute the commands (don't forget Backup_(Server_Setup)#prov-backup-rsnapshot).
• Backup surveillance
  • The schedule-warning script also works for the new environment with the new LDAP and Templates.
    • Example template and description see Backup_(OpenLDAP)#Unsuccessful_Place_Holders_E-Mail_.28txt.2Fhtml.29.
  • The externalID for the deep.ch reseller is not yet implemented. To do it you must:
    • Include the placeholder in the template in the form of {$externalID}
    • Get the ID in the sendmail subroutine of the scheduleWarning.pl script
    • Add the the following line to the replace variables in the sendmail subroutine of the scheduleWarning.pl script (around line 1429):

    • externalID => $external_ID,

  • The script can be installed according to Backup_(Server_Setup)#schedule_warning (don't forget Backup_(Server_Setup)#prov-backup-rsnapshot)
• Backup helper scripts
  • The writeAccontSize.pl is adapted to the new LDAP directory. It reads and writes quota values and thresholds from/to the LDAP and gets the path to the mail templates from the LDAP
  • A script (and cronjob) which executes two commands each night is still missing and needs to be implemented. It must do an LDAP search and get all active backup account (search under ou=accounts,ou=backup,ou=services,dc=foss-cloud,dc=org for objectClass=sstBackup and sstIsActive=TRUE). Read the necessary attributes from these accounts and execute the following commands:
    • /<path/to>/writeAccountSize.pl -C /<path/to>/writeAccountSize.conf -D <home directory> -U <UID>
    • /<path/to>/scheduleWarning.pl -U <UID>
• prov-backup-kvm
  • On the new infrastructure:
  • As soon as the vips work again, make the prov-backup-kvm connect to ldapm.stepping-stone.ch:
    • vi /etc/Provisionig/Backup/KVM.conf

    • SERVER = ldaps://ldapm.stepping-stone.ch

Scripts

prov-backup-rsnapshot

See prov-backup-rsnapshot

scheduleWarning.pl

The scheduleWarning.pl is executed once a day for every (active) backup account in the LDAP directory. It compares the the scheduled backups with the backups which were really written and send the user a mail, if something is not as it should be. Every reseller can define its proper text (template) and store it on the filesystem. The path to the template is stored in the LDAP directory (see [[]]). The scheduleWarning.pl script reads these values and then open the appropriate template. In this template the following placeholders are replaced:

• {$salutation} => Salutation: "Sehr geehrter Herr" / "Dear Mrs."* {$surname} => Surname of the backup account owner* {$scheduled_date} => The scheduled date of the backup that did not succeed* {$scheduled_time} => The scheduled time of the backup that did not succeed* {$gecos} => The gecos of the backup that did not succeed* {$computer} => The computer name from which the backup did not succeed* {$last_success} => The date and time of the last successful backup
• {$uid} => The backups UID

All placeholders are language depended.