Changes

** The prov-backup-rsnapshot rsnatheot 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]])

** The writeAccontSize .pl is adapted to the new LDAP directory.. TBD this eveningIt reads and writes quota values and thresholds from/to the LDAP and gets the path to the mail templates from the LDAP** Add the mail subject to the mail templates for the quota warning mails:*** Add the following line at the very top of the template*** <pre>Subject: <YOUR-MAIL-SUBJECT></pre>** 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 <code>ou=accounts,ou=backup,ou=services,dc=foss-cloud,dc=org</code>for <code>objectClass=sstBackup</code> and <code>sstIsActive=TRUE</code>). Read the necessary attributes from these accounts and execute the following commands: *** <code>/<path/to>/writeAccountSize.pl -C /<path/to>/writeAccountSize.conf -D <home directory> -U <UID></code>*** <code>/<path/to>/scheduleWarning.pl -U <UID></code>* 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:*** <code>vi /etc/Provisionig/Backup/KVM.conf</code>*** <pre>SERVER = ldaps://ldapm.stepping-stone.ch</pre> == Scripts == === prov-backup-rsnapshot === See [[prov-backup-rsnapshot]] === rsnapshot ===This script executes the very basic rsnapshot command for each user which wants to have a snapshot for the given interval. This script takes as input parameter <code>--interval</code> where you can specify the following intervals: * hourly* daily* weekly* monthly* yearly It is basically just a wrapper around the rsnapshot command for the given interval. It does an LDAP lookup and collects all users which want to have a rsnapshot made for the given interval. For all the collected users, the rsnapshot command for the given interval is executed.  A crojob for the daily, weekly and monthly rnspashots is created on the [[Backup_(Server_Setup)|Test-Backup-Server]] '''Important:''' As stated above, on the Test-Backup-Server the command are just printed to STDOUT instead of really being exceuted. 4 ==== Configuration ====<pre>[General]MaxParallelProcesses = # How many rsnapshot processes you want to have in parallel # The basic rsnapshot command, the %uid% and %interval% will be replaced by the scriptRsnapshot_command = /usr/bin/nice -n 19 /usr/bin/rsnapshot -c /etc/rsnapshot/rsnapshot.conf.%uid% %interval% [LDAP]Host = # URI of the LDAP serverPort = # Port of the LDAP serverUser = # Username to bind to the LDAP serverPassword = # Password for the given userCA_Path = # Directory containing the CA for the given LDAP serverAccounts_Base = # Base dn to the backup accouts</pre> === 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 UIDAll placeholders are language depended. ==== Configuration ====<pre>[XML]# In this section you should not change anything. This is the path of the schemas and XML files located on the serverSCHEDULE_FILE = %homeDirectory%/incoming/%computerName%/.sepiola_backup/scheduler.xmlSCHEDULE_XSD = %configpath%/../etc/schema/scheduler_schema.xsdBACKUP_ENDED_FILE = %homeDirectory%/incoming/%computerName%/.sepiola_backup/backupEnded.xmlBACKUP_ENDED_XSD = %configpath%/../etc/schema/backupended_schema.xsdBACKUP_STARTED_FILE = %homeDirectory%/incoming/%computerName%/.sepiola_backup/backupStarted.xmlBACKUP_STARTED_XSD = %configpath%/../etc/schema/backupstarted_schema.xsd  [TEMPLATE]# You can modify thesea variables as you wish, they# will be used for the saluataion in the mail that will# be sent to the user. The salutations are language and # gender dependant (m = male / f = female)Salutation_Default_de-CH = Liebe Kundin / Lieber KundeSalutation_m_de-CH = Sehr geehrter HerrSalutation_f_de-CH = Sehr geehrte FrauSalutation_Default_en-GB = Dear customerSalutation_m_en-GB = Dear Mr.Salutation_f_en-GB = Dear Mrs. [LDAP] SERVER = # The URI of your LDAP serverPORT = # The port on which your LDAP server listensDEBUG = # If you want debug messages for LDAP connection ADMIN_DN = # The admin-bind DN to you LDAP serverADMIN_PASSWORD = # The appropriate very secret password BACKUP_BASE = # The base dn of the backup accountsPEOPLE_BASE = # The base dn of the people accountsRESELLER_BASE = # The base dn of the reseller-configuration accountsSCOPE = sub [MAIL]mailTo = # To whom the mail is sent if nothing is found in the LDAPhost = # The mail host over which the mails are sentport = # The port of the mail hostusername = # The username to authenticate on the mail hostpassword = # The password to authenticate on the mail hostfrom = # From which the mail comes from if nothing is found in the LDAP</pre> === writeAccountSize.pl ===This is just an adaption of the [https://int.stepping-stone.ch/wiki/writeAccountSize.pl writeAccountSize.pl script]. The following modifications were done:* Write quota values also to the LDAP directory* Using new the Net::SMTPS lib to send the mails* Generate the mail text according to the templates specified by the reseller in the LDAP* Using a library to fill in the templates '''Important:''' On the Test-Backup-Server the script returns a dummy quota, because it the quota command does not work yet. But if you install it from scratch it will get the correct quota. To change the behaviour on the LDAP server, uncomment the "getQuotaSize" method starting at line 512.