Menu
▾
▴
Re: [Exist-open] Full backup at 4 a.m.
|
From: Florian S. <ml-...@fl...> - 2021-01-15 17:44:33
|
Hi Christian, in short: Based on the documentation, i don't see a way to make the backup start on 0 (12am = midnight), with the full backup at 4am. In your case, it seems that the combination of the increment of 4 together with the max attribute of 6 leads to strange results. Setting max to 6 says: "Create one full backup after creating six incremental backups". But with an increment of 4 for [0-23], starting on 0, you get only five incremental backups per day. With max set to 6, the time of the full backup will "roam" over the entire day: On day 1, the backup run on 0 (12am = midnight) should be a full backup, since the first run is always a full backup. With max set to 6, the following six (!) backups will be incremental, so the sixth incremental backup is the first one of the following day (0 = 12am = midnight), with the next full backup on 4am of day 2. The third full backup again will take place after six incremental ones, thus on 8am of day 3, and so on. Thus, setting max to 5 should fix the problem of the different full backup times, but you won't get a full backup at 4am with that trigger definition; only the backup run on 0 (12am = midnight) will be a full backup; the following five are incremental, the next one (again at 0 = 12am = midnight) is full, and so on. In that case, you may even drop the max attribute completely; it doesn't have any special meaning in this case. It won't have any effect since there are only five incremental backups per day, with the first backup on next day as full backup. I assume that, if you want to have a full backup at 4am, you'll need to make 4am as first backup run, so the cron expression would be "0 0 4/4 * * ?". But this trigger will create only five backups per day, not six (no backup at 12am/midnight). Thus, i don't see a way to make the backup trigger start on 0 (12am = midnight), creating six backups per day, with the full backup on 4am. Kind regards Florian Am 15.01.21 um 15:01 schrieb Christian Achter: > Dear all, > > I have a backup scheduler running that creates 6 backups per day, 5 > incremental and 1 full backup. > > The code in my etc/conf.xml looks like this: > > <job type="system" name="backup" > class="org.exist.storage.ConsistencyCheckTask" > cron-trigger="0 0 0/4 * * ?"> > <parameter name="output" > value="/opt/server/ediarum/exist-db_5.2.0/backup"/> > <parameter name="backup" value="yes"/> > <parameter name="incremental" value="yes"/> > <parameter name="incremental-check" value="no"/> > <parameter name="max" value="6"/> > </job> > > Here is my problem: > > I want the full backup to be created at 4:00 a.m. I consulted the > eXist online documentation and the book and assumed that 0 0 0/4 would > be translated to: every 4 hours starting at midnight with the first > backup being a full backup. > > But in reality, the full backup is created at 8:00 a.m. My experience > during several months showed that this time even differs. Sometimes, > the full backup was created at 4 p.m. oder at noon - maybe depending > in the time when the eXist-db ws started. > > What am I doing wrong? How can I improve this scheduler to have a full > backup at 4 a.m. while keeping the 5 incremental backups during the day? > > Thanks in advance and kind regards > > Christian > > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open |
