[rsnapshot-discuss] rsnapshot - cron - schedule | important

[Masi Osmani]

Hey guys,



here are some information:



my important config part:

#####################

link_dest 1

sync_first 1



retain daily 7

retain weekly 4

retain monthly 12





my cron schedule:

###############



28 1 * * 1-6 root rsnapshot sync && rsnapshot daily



52 2 * * 0 root rsnapshot sync && rsnapshot daily &&
rsnapshot weekly



59 3 1 * * root monthly





In the manpage i read this note:



"It is usually a good idea to schedule the larger backup levels to run a bit
before the lower ones. For

example, in the crontab above, notice that "beta" runs 10 minutes
before "alpha". The main reason for this

is that the beta rotate will pull out the oldest alpha and make that
the youngest beta (which means that

the next alpha rotate will not need to delete the oldest alpha),
which is more efficient."

From my point of view this note does not care about on which day the backup

starts and if the first chain is completed.



Lets say i will start my first backup on
<https://www.dict.cc/englisch-deutsch/Wednesday.html> Wednesday 03.08.2016
this would be the chain on Sunday:



Sun - 07.08.2016 - daily.0

Sat - 06.08.2016 - daily.1

Fri - 05.08.2016 - daily.2

Thu - 04.08.2016 - daily.3

Wed - 03.08.2016 - daily.4



Concerning my cron for Sunday:



"52 2 * * 0 root rsnapshot sync && rsnapshot daily &&
rsnapshot weekly"



This would happen at the end of the first week:



"[2016-08-07T02:56:02] daily.6 not present (yet), nothing to copy"



Exactly here is my problem, based on this error i would not have a backup
from the first week.



To create on <https://www.dict.cc/englisch-deutsch/Wednesday.html>
Wednesday daily.0/1/2 (exact same copies) for the purpose of chain
fullfillment (retain 7 = d0-d6) would not be the right solution in my
opinion if you want to start your backup on any day.





Do you have another idea to solve this problem ?



I would appreciate an answer to this question!





Regards

Masi

[Masi Osmani]

Hey guys,

I would really appreciate an answer to my question below!

##############################################################################################################

my important config part:
-------------------------
link_dest 1
sync_first 1

retain daily 7
retain weekly 4
retain monthly 12

my cron schedule:
-------------------------
28 1 * * 1-6 root rsnapshot sync && rsnapshot daily
52 2 * * 0 root rsnapshot sync && rsnapshot daily &&
rsnapshot weekly
59 3 1 * * root monthly

In the manpage i read this note:
-------------------------

"It is usually a good idea to schedule the larger backup levels to run a bit
before the lower ones..."

From my point of view this note does not care about on which day the backup

starts and if the first chain is completed and to guarantee the first rotation of the first week.

Lets say i will start my first backup on Wednesday 03.08.2016
this would be the chain on Sunday:

Sun - 07.08.2016 - daily.0
Sat - 06.08.2016 - daily.1
Fri - 05.08.2016 - daily.2
Thu - 04.08.2016 - daily.3
Wed - 03.08.2016 - daily.4

Concerning my cron for Sunday:

"52 2 * * 0 root rsnapshot sync && rsnapshot daily &&
rsnapshot weekly"

This would happen at the end of the first week:

"[2016-08-07T02:56:02] daily.6 not present (yet), nothing to copy"

Exactly here is my problem, based on this error i would not have a backup
from the first week.

To create on Wednesday daily.0/1/2 (exact same copies) for the purpose of chain
fullfillment (retain 7 = d0-d6) would not be the right solution in my
opinion if you want to start your backup on any day.

##############################################################################################################

Do you have another idea to solve this problem or is this the only solution to check when the backup startday is and to count how many days till sunday is left and then to create multiple snapshots of the same day to complete the chain ?

##############################################################################################################

[David Keegel]

Masi,

I think your question is essentially:
How can I stop getting:
"... daily.6 not present (yet), nothing to copy"

If that is your question, then my answer is to ignore that message
in the first week of running rsnapshot, after which time you should
have a complete set of daily.N backups and then the message should
stop.

If that is not your question, then I suggest you find a new way to
phrase your question, rather than just repeating a big blob of text
that we seem not to be understanding.

If you were looking for advice on how to set up your cron scheduling
then I would set up the cron entries something like this:

50 0 * * * rsnapshot sync; if [ $? -ne 1 ]; then rsnapshot daily; fi
40 0 * * 0 rsnapshot weekly
30 0 1 * * rsnapshot monthly

Post by Masi Osmani
Hey guys,
I would really appreciate an answer to my question below!
#######################################################################
#######################################
-------------------------
link_dest 1
sync_first 1
retain daily 7
retain weekly 4
retain monthly 12
-------------------------
28 1 * * 1-6 root rsnapshot sync && rsnapshot daily
52 2 * * 0 root rsnapshot sync && rsnapshot daily &&
rsnapshot weekly
59 3 1 * * root monthly
-------------------------
"It is usually a good idea to schedule the larger backup levels to run a bit
before the lower ones..."
From my point of view this note does not care about on which day the backup
starts and if the first chain is completed and to guarantee the first
rotation of the first week.
Lets say i will start my first backup on Wednesday 03.08.2016
Sun - 07.08.2016 - daily.0
Sat - 06.08.2016 - daily.1
Fri - 05.08.2016 - daily.2
Thu - 04.08.2016 - daily.3
Wed - 03.08.2016 - daily.4
"52 2 * * 0 root rsnapshot sync && rsnapshot daily &&
rsnapshot weekly"
"[2016-08-07T02:56:02] daily.6 not present (yet), nothing to copy"
Exactly here is my problem, based on this error i would not have a backup
from the first week.
To create on Wednesday daily.0/1/2 (exact same copies) for the purpose of chain
fullfillment (retain 7 = d0-d6) would not be the right solution in my
opinion if you want to start your backup on any day.
#######################################################################
#######################################
Do you have another idea to solve this problem or is this the only
solution to check when the backup startday is and to count how many
days till sunday is left and then to create multiple snapshots of the
same day to complete the chain ?
#######################################################################
#######################################
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
_______________________________________________
rsnapshot-discuss mailing list
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss