[rsnapshot-discuss] result review

[Masi Osmani]

Hello everybody,

would you consider the chain as correct ? From my point of view i dont have a backup from September but therefore two of October.

The backup creation starts from Aug 27 to Dec 01.

cron - schedule
###############
55 1 * * * root rsnapshot sync && rsnapshot daily
39 1 * * 0 root rsnapshot weekly
17 1 1 * * root rsnapshot monthly

server1
#######
Aug 27 01:57 - daily.0
...
Dec 01 01:57 daily.0
Nov 30 01:57 daily.0
Nov 29 01:57 daily.1
Nov 28 01:57 daily.2
Nov 27 01:57 daily.3

Nov 20 01:57 weekly.0
Nov 13 01:57 weekly.1
Nov 06 01:57 weekly.2

Oct 30 01:57 monthly.0
Oct 02 01:57 monthly.1
Aug 28 01:57 monthly.2

THX!

[Ken Woods]

Why don't you consider this to be your September backup?

> Oct 02 01:57 monthly.1




> On Sep 2, 2016, at 06:11, Masi Osmani <***@outlook.de> wrote:
>
> Hello everybody,
>
> would you consider the chain as correct ? From my point of view i dont have a backup from September but therefore two of October.
>
> The backup creation starts from Aug 27 to Dec 01.
>
> cron - schedule
> ###############
> 55 1 * * * root rsnapshot sync && rsnapshot daily
> 39 1 * * 0 root rsnapshot weekly
> 17 1 1 * * root rsnapshot monthly
>
> server1
> #######
> Aug 27 01:57 - daily.0
> ...
> Dec 01 01:57 daily.0
> Nov 30 01:57 daily.0
> Nov 29 01:57 daily.1
> Nov 28 01:57 daily.2
> Nov 27 01:57 daily.3
>
> Nov 20 01:57 weekly.0
> Nov 13 01:57 weekly.1
> Nov 06 01:57 weekly.2
>
> Oct 30 01:57 monthly.0
> Oct 02 01:57 monthly.1
> Aug 28 01:57 monthly.2
>
> THX!
> ------------------------------------------------------------------------------
> _______________________________________________
> rsnapshot-discuss mailing list
> rsnapshot-***@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

[Ken Woods]

Who cares? The timestamp is meaningless.

Do you care about what data exists, or what the timestamp says?




> On Sep 2, 2016, at 07:51, Masi Osmani <***@outlook.de> wrote:
>
> Because the timestamp says it was created on 02.10.2016 and not in September.
>
>> Am 02.09.2016 um 17:40 schrieb Ken Woods <***@gmail.com>:
>>
>> Why don't you consider this to be your September backup?
>>
>>> Oct 02 01:57 monthly.1
>>
>>
>>
>>
>>> On Sep 2, 2016, at 06:11, Masi Osmani <***@outlook.de> wrote:
>>>
>>> Hello everybody,
>>>
>>> would you consider the chain as correct ? From my point of view i dont have a backup from September but therefore two of October.
>>>
>>> The backup creation starts from Aug 27 to Dec 01.
>>>
>>> cron - schedule
>>> ###############
>>> 55 1 * * * root rsnapshot sync && rsnapshot daily
>>> 39 1 * * 0 root rsnapshot weekly
>>> 17 1 1 * * root rsnapshot monthly
>>>
>>> server1
>>> #######
>>> Aug 27 01:57 - daily.0
>>> ...
>>> Dec 01 01:57 daily.0
>>> Nov 30 01:57 daily.0
>>> Nov 29 01:57 daily.1
>>> Nov 28 01:57 daily.2
>>> Nov 27 01:57 daily.3
>>>
>>> Nov 20 01:57 weekly.0
>>> Nov 13 01:57 weekly.1
>>> Nov 06 01:57 weekly.2
>>>
>>> Oct 30 01:57 monthly.0
>>> Oct 02 01:57 monthly.1
>>> Aug 28 01:57 monthly.2
>>>
>>> THX!
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> rsnapshot-discuss mailing list
>>> rsnapshot-***@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

[Masi Osmani]

Sorry but i cannot understand how the timestamp can be meaningless.

Lets say i have a dir called "Backup".
On 30 September it contains 3 files and on 2 October 1 file.

It something different to have a snapshot from 30.9 or from 2.10 ?!

Maybe i dont understand your logic.

> Am 02.09.2016 um 17:40 schrieb Ken Woods <***@gmail.com>:
>
> Why don't you consider this to be your September backup?
>
>> Oct 02 01:57 monthly.1
>
>
>
>
>> On Sep 2, 2016, at 06:11, Masi Osmani <***@outlook.de> wrote:
>>
>> Hello everybody,
>>
>> would you consider the chain as correct ? From my point of view i dont have a backup from September but therefore two of October.
>>
>> The backup creation starts from Aug 27 to Dec 01.
>>
>> cron - schedule
>> ###############
>> 55 1 * * * root rsnapshot sync && rsnapshot daily
>> 39 1 * * 0 root rsnapshot weekly
>> 17 1 1 * * root rsnapshot monthly
>>
>> server1
>> #######
>> Aug 27 01:57 - daily.0
>> ...
>> Dec 01 01:57 daily.0
>> Nov 30 01:57 daily.0
>> Nov 29 01:57 daily.1
>> Nov 28 01:57 daily.2
>> Nov 27 01:57 daily.3
>>
>> Nov 20 01:57 weekly.0
>> Nov 13 01:57 weekly.1
>> Nov 06 01:57 weekly.2
>>
>> Oct 30 01:57 monthly.0
>> Oct 02 01:57 monthly.1
>> Aug 28 01:57 monthly.2
>>
>> THX!
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> rsnapshot-discuss mailing list
>> rsnapshot-***@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

[Thiep Duong]

Only daily.0 is actually by "rsync" -- Everything else is by "mv" command, so If the Oct 02 date is confusing to you,

do a "touch" command to change is to Sep 30 if you want.


Anthony

________________________________
From: Masi Osmani <***@outlook.de>
Sent: Friday, September 2, 2016 12:53 PM
To: Ken Woods
Cc: rsnapshot-***@lists.sourceforge.net
Subject: Re: [rsnapshot-discuss] result review

Sorry but i cannot understand how the timestamp can be meaningless.

Lets say i have a dir called "Backup".
On 30 September it contains 3 files and on 2 October 1 file.

It something different to have a snapshot from 30.9 or from 2.10 ?!

Maybe i dont understand your logic.

Am 02.09.2016 um 17:40 schrieb Ken Woods <***@gmail.com<mailto:***@gmail.com>>:

Why don't you consider this to be your September backup?

Oct 02 01:57 monthly.1



On Sep 2, 2016, at 06:11, Masi Osmani <***@outlook.de<mailto:***@outlook.de>> wrote:

Hello everybody,

would you consider the chain as correct ? From my point of view i dont have a backup from September but therefore two of October.

The backup creation starts from Aug 27 to Dec 01.

cron - schedule
###############
55 1 * * * root rsnapshot sync && rsnapshot daily
39 1 * * 0 root rsnapshot weekly
17 1 1 * * root rsnapshot monthly

server1
#######
Aug 27 01:57 - daily.0
...
Dec 01 01:57 daily.0
Nov 30 01:57 daily.0
Nov 29 01:57 daily.1
Nov 28 01:57 daily.2
Nov 27 01:57 daily.3

Nov 20 01:57 weekly.0
Nov 13 01:57 weekly.1
Nov 06 01:57 weekly.2

Oct 30 01:57 monthly.0
Oct 02 01:57 monthly.1
Aug 28 01:57 monthly.2

THX!
------------------------------------------------------------------------------

[Masi Osmani]

@Anthony



The dir timestamp "Oct 02" is not a mistaken modification through "mv", it
is the original timestamp. The dir became "monthly.1" by rotation.



You can find the full calc as e-mail attachment.



But i am still confused by statements like:

- "Why don't you consider this to be your September backup? Oct
02 01:57 monthly.1"

- "Who cares? The timestamp is meaningless."



I would say a backup of 02.09.2016 and 03.09.2016 are not equal if during
the time the were changes.



I hope i can get an explanation.



THX!



Von: Thiep Duong [mailto:***@nantero.com]
Gesendet: Freitag, 2. September 2016 23:16
An: Masi Osmani <***@outlook.de>
Cc: rsnapshot-***@lists.sourceforge.net
Betreff: Re: [rsnapshot-discuss] result review



Only daily.0 is actually by "rsync" -- Everything else is by "mv" command,
so If the Oct 02 date is confusing to you,

do a "touch" command to change is to Sep 30 if you want.



Anthony

_____

From: Masi Osmani <***@outlook.de <mailto:***@outlook.de> >
Sent: Friday, September 2, 2016 12:53 PM
To: Ken Woods
Cc: rsnapshot-***@lists.sourceforge.net
<mailto:rsnapshot-***@lists.sourceforge.net>
Subject: Re: [rsnapshot-discuss] result review



Sorry but i cannot understand how the timestamp can be meaningless.



Lets say i have a dir called "Backup".

On 30 September it contains 3 files and on 2 October 1 file.



It something different to have a snapshot from 30.9 or from 2.10 ?!



Maybe i dont understand your logic.


Am 02.09.2016 um 17:40 schrieb Ken Woods <***@gmail.com
<mailto:***@gmail.com> >:

Why don't you consider this to be your September backup?



Oct 02 01:57 monthly.1






On Sep 2, 2016, at 06:11, Masi Osmani <***@outlook.de
<mailto:***@outlook.de> > wrote:

Hello everybody,

would you consider the chain as correct ? From my point of view i dont have
a backup from September but therefore two of October.

The backup creation starts from Aug 27 to Dec 01.

cron - schedule
###############
55 1 * * * root rsnapshot sync && rsnapshot daily
39 1 * * 0 root rsnapshot weekly
17 1 1 * * root rsnapshot monthly

server1
#######
Aug 27 01:57 - daily.0
...
Dec 01 01:57 daily.0
Nov 30 01:57 daily.0
Nov 29 01:57 daily.1
Nov 28 01:57 daily.2
Nov 27 01:57 daily.3

Nov 20 01:57 weekly.0
Nov 13 01:57 weekly.1
Nov 06 01:57 weekly.2

Oct 30 01:57 monthly.0
Oct 02 01:57 monthly.1
Aug 28 01:57 monthly.2

THX!

----------------------------------------------------------------------------
--

[Masi Osmani]

@Anthony

The dir timestamp "Oct 02" is not a mistaken modification through "mv", it
is the original timestamp. The dir became "monthly.1" by rotation.

You can find the full calc as e-mail attachment or here
https://sourceforge.net/p/rsnapshot/mailman/message/35331403/

But i am still confused by statements like:
- "Why don't you consider this to be your September backup? Oct
02 01:57 monthly.1"
- "Who cares? The timestamp is meaningless."

I would say a backup of 02.09.2016 and 03.09.2016 are not equal if during
the time the were changes.

I hope i can get an explanation.

THX!

------------------------------------------------------------------------------

[Ken Woods]

You're confused by my statements because we look at the data differently.
You care *when* the backup happened (for some reason, perhaps valid,
perhaps not)
The "monthly" backup from Oct 02 contains the oldest weekly backup, which
was the oldest daily backup of that week.

I only care that it was backed up on a rotating schedule.
Some of my "daily" backups can take weeks (or more) to run, so I don't give
a shit what they're named or when they run, as long as they run in a
certain sequence. Keep in mind that the names "hourly, daily,
weekly,monthly" are meaningless to rsnapshot. You can call them "bob,
george, tom, and harry" if you want to.


kw


On Fri, Sep 2, 2016 at 3:50 PM, Masi Osmani <***@outlook.de> wrote:

> @Anthony
>
> The dir timestamp "Oct 02" is not a mistaken modification through "mv", it
> is the original timestamp. The dir became "monthly.1" by rotation.
>
> You can find the full calc as e-mail attachment or here
> https://sourceforge.net/p/rsnapshot/mailman/message/35331403/
>
> But i am still confused by statements like:
> - "Why don't you consider this to be your September backup? Oct
> 02 01:57 monthly.1"
> - "Who cares? The timestamp is meaningless."
>
> I would say a backup of 02.09.2016 and 03.09.2016 are not equal if during
> the time the were changes.
>
> I hope i can get an explanation.
>
> THX!
>
> ------------------------------------------------------------
> ------------------
> _______________________________________________
> rsnapshot-discuss mailing list
> rsnapshot-***@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss
>

[Masi Osmani]

I can comprehend your view. From my point of view if the first backup is done on 02.10 lets call it „daily“ and after a certain time it becames „monthly“ by rotation (rotation from a technical view in this case the same as renaming a folder, no data transfer), no matter what its name at the end is, it will contain a data state from „02.10“.



And here comes my problem. Lets say an important file is created on 4th of september and someone deleted it on 27th of september and because of the rotation alle snaps of september are deleted (exactly my example). I would only have a monthly of 2nd of october.



Maybe i have a wrong way of thinking :)





Von: Ken Woods [mailto:***@gmail.com]
Gesendet: Samstag, 3. September 2016 02:13
An: Masi Osmani <***@outlook.de <mailto:***@outlook.de> >
Cc: rsnapshot discuss <rsnapshot-***@lists.sourceforge.net <mailto:rsnapshot-***@lists.sourceforge.net> >
Betreff: Re: [rsnapshot-discuss] result review



You're confused by my statements because we look at the data differently.

You care *when* the backup happened (for some reason, perhaps valid, perhaps not)

The "monthly" backup from Oct 02 contains the oldest weekly backup, which was the oldest daily backup of that week.



I only care that it was backed up on a rotating schedule.

Some of my "daily" backups can take weeks (or more) to run, so I don't give a shit what they're named or when they run, as long as they run in a certain sequence. Keep in mind that the names "hourly, daily, weekly,monthly" are meaningless to rsnapshot. You can call them "bob, george, tom, and harry" if you want to.





kw





On Fri, Sep 2, 2016 at 3:50 PM, Masi Osmani <***@outlook.de <mailto:***@outlook.de> > wrote:

@Anthony

The dir timestamp "Oct 02" is not a mistaken modification through "mv", it
is the original timestamp. The dir became "monthly.1" by rotation.

You can find the full calc as e-mail attachment or here
https://sourceforge.net/p/rsnapshot/mailman/message/35331403/

But i am still confused by statements like:
- "Why don't you consider this to be your September backup? Oct
02 01:57 monthly.1"
- "Who cares? The timestamp is meaningless."

I would say a backup of 02.09.2016 and 03.09.2016 are not equal if during
the time the were changes.

I hope i can get an explanation.

THX!

------------------------------------------------------------------------------

[David Keegel]

On Sat, Sep 03, 2016 at 03:02:07AM +0200, Masi Osmani wrote:
>
> And here comes my problem. Lets say an important file is created on 4th
> of september and someone deleted it on 27th of september and because of
> the rotation alle snaps of september are deleted (exactly my example).
> I would only have a monthly of 2nd of october.
>

With rsnapshot, you could retain 365 daily snapshots and then yearly
snapshots. Or 7 daily snapshots then 52 weekly snapshots then
yearly snapshots. Or something else which doesn't match the
Gregorian calendar.

There is plenty of flexibility there which can be customised to
suit your site's preferred tradeoff between disk space usage and
fine grained ability to restore past backups (eg being able to
restore a file which only existed for 1 day from 6 months ago).

If you can work out your requirements in terms of how long you need
to retain daily backups, and then further back than that how long
you need weekly resolution and after that how long you need monthly
(really 4 or 5 week) resolution, it should be pretty easy to convert
that to rsnapshot.conf. (Feel free to skip weekly or monthly
retentions if that suits your requirements better.)

If you're still having trouble, please tell us your requirements
for how long you need to keep backups of different resolutions,
and someone can suggest how to translate that to rsnapshot.conf,
(unless your requirements are totally not suited to rsnapshot).

--
___________________________________________________________________________
David Keegel <***@cyber.com.au> Cyber IT Solutions Pty. Ltd.
http://www.cyber.com.au/~djk/ Linux & Unix Systems Administration


------------------------------------------------------------------------------

[Christopher Barry]

On Sat, 3 Sep 2016 15:55:18 +1000
David Keegel <***@cyber.com.au> wrote:

>On Sat, Sep 03, 2016 at 03:02:07AM +0200, Masi Osmani wrote:
>>
>> And here comes my problem. Lets say an important file is created
>> on 4th of september and someone deleted it on 27th of september and
>> because of the rotation alle snaps of september are deleted (exactly
>> my example). I would only have a monthly of 2nd of october.
>>
>
>With rsnapshot, you could retain 365 daily snapshots and then yearly
>snapshots. Or 7 daily snapshots then 52 weekly snapshots then
>yearly snapshots. Or something else which doesn't match the
>Gregorian calendar.
>
>There is plenty of flexibility there which can be customised to
>suit your site's preferred tradeoff between disk space usage and
>fine grained ability to restore past backups (eg being able to
>restore a file which only existed for 1 day from 6 months ago).
>
>If you can work out your requirements in terms of how long you need
>to retain daily backups, and then further back than that how long
>you need weekly resolution and after that how long you need monthly
>(really 4 or 5 week) resolution, it should be pretty easy to convert
>that to rsnapshot.conf. (Feel free to skip weekly or monthly
>retentions if that suits your requirements better.)
>
>If you're still having trouble, please tell us your requirements
>for how long you need to keep backups of different resolutions,
>and someone can suggest how to translate that to rsnapshot.conf,
>(unless your requirements are totally not suited to rsnapshot).
>

That has to be the best description of how to use rsnapshot I've ever
read. Nice.

--
Regards,
Christopher

------------------------------------------------------------------------------

[Masi Osmani]

First of all thx for all your explanations and for taking your time.

These are my requirements:
- to have backups from the the last 7 days
- to have backups from the last 4 weeks
- to have backups for each past month since backup start

lets say i would start on 1.1.2016 then i would expect till today something
like this:

03.09 - d0
02.09 - d1
01.09 - d2
31.08 - d3
30.08 - d4
29.08 - d5

28.08 - w0
21.08 - w1
14.08 - w2
07.08 - w3

07.2016 - m0 (which day is not important)
06.2016 - m1
05.2016 - m2
04.2016 - m3
03.2016 - m4
02.2016 - m5
01.2016 - m6

I hope you can understand my requirements.


-----Ursprüngliche Nachricht-----
Von: David Keegel [mailto:***@cyber.com.au]
Gesendet: Samstag, 3. September 2016 07:55
An: Masi Osmani <***@outlook.de>
Cc: rsnapshot-***@lists.sourceforge.net
Betreff: Re: [rsnapshot-discuss] WG: result review

On Sat, Sep 03, 2016 at 03:02:07AM +0200, Masi Osmani wrote:
>
> And here comes my problem. Lets say an important file is created on 4th
> of september and someone deleted it on 27th of september and because of
> the rotation alle snaps of september are deleted (exactly my example).
> I would only have a monthly of 2nd of october.
>

With rsnapshot, you could retain 365 daily snapshots and then yearly
snapshots. Or 7 daily snapshots then 52 weekly snapshots then yearly
snapshots. Or something else which doesn't match the Gregorian calendar.

There is plenty of flexibility there which can be customised to suit your
site's preferred tradeoff between disk space usage and fine grained ability
to restore past backups (eg being able to restore a file which only existed
for 1 day from 6 months ago).

If you can work out your requirements in terms of how long you need to
retain daily backups, and then further back than that how long you need
weekly resolution and after that how long you need monthly (really 4 or 5
week) resolution, it should be pretty easy to convert that to
rsnapshot.conf. (Feel free to skip weekly or monthly retentions if that
suits your requirements better.)

If you're still having trouble, please tell us your requirements for how
long you need to keep backups of different resolutions, and someone can
suggest how to translate that to rsnapshot.conf, (unless your requirements
are totally not suited to rsnapshot).

--
___________________________________________________________________________
David Keegel <***@cyber.com.au> Cyber IT Solutions Pty. Ltd.
http://www.cyber.com.au/~djk/ Linux & Unix Systems Administration


------------------------------------------------------------------------------

[Oon-Ee Ng]

On Sun, Sep 4, 2016 at 4:12 AM, Masi Osmani <***@outlook.de> wrote:
> First of all thx for all your explanations and for taking your time.
>
> These are my requirements:
> - to have backups from the the last 7 days
> - to have backups from the last 4 weeks
> - to have backups for each past month since backup start

As has already been discussed, you're responsible for this part of it.
Cron can indeed do all of the above (the systemd equivalent is more
complicated for day-of-the-month type stuff, AFAICR), but YOU will
need to define what 'week' and 'month' means, and then set the cron up
appropriately.

What you'd want is (probably) for monthly to run on the 1st day of the
month (I would take 4th or 5th), weekly to run on 1st day of the week
(or last?), and of course the daily.

------------------------------------------------------------------------------

['David Keegel']

Masi,

For those requirements (especially "which day is not important" for
monthly backups), you could change the timing of rsnapshot monthly
to run around the middle of the month (say the 15th day of month),
instead of 1st day of month which most people use.

Then whether the snapshot used for the monthly is a week before or a
week after the middle of the month, it will still be in the calendar
month after the previous monthly backup and before the next monthly.

On Sat, Sep 03, 2016 at 10:12:03PM +0200, Masi Osmani wrote:
> First of all thx for all your explanations and for taking your time.
>
> These are my requirements:
> - to have backups from the the last 7 days
> - to have backups from the last 4 weeks
> - to have backups for each past month since backup start
>
> lets say i would start on 1.1.2016 then i would expect till today something
> like this:
>
> 03.09 - d0
> 02.09 - d1
> 01.09 - d2
> 31.08 - d3
> 30.08 - d4
> 29.08 - d5
>
> 28.08 - w0
> 21.08 - w1
> 14.08 - w2
> 07.08 - w3
>
> 07.2016 - m0 (which day is not important)
> 06.2016 - m1
> 05.2016 - m2
> 04.2016 - m3
> 03.2016 - m4
> 02.2016 - m5
> 01.2016 - m6
>
> I hope you can understand my requirements.

--
___________________________________________________________________________
David Keegel <***@cyber.com.au> Cyber IT Solutions Pty. Ltd.
http://www.cyber.com.au/~djk/ Linux & Unix Systems Administration


------------------------------------------------------------------------------

[Masi Osmani]

Hi David,

thx a lot for your support und to everyone who did the brainstorming with me and answered my questions.

changing the "monthly" creation date to 15th did exactly what i wanted.

------------------------------------------------------------------------------
Aug 27 01:57 - daily.0
...
Jan 15 01:57 daily.0 | monthly creation
Jan 14 01:57 daily.1
Jan 13 01:57 daily.2
Jan 12 01:57 daily.3
Jan 11 01:57 daily.4
Jan 10 01:57 daily.5
Jan 09 01:57 daily.6
Jan 08 01:57 weekly.0
Jan 01 01:57 weekly.1
Dec 25 01:57 weekly.2
Dec 18 01:57 monthly.0
Nov 13 01:57 monthly.1
Oct 16 01:57 monthly.2
Sep 11 01:57 monthly.3
------------------------------------------------------------------------------

Regards
Masi


> Date: Mon, 5 Sep 2016 11:44:35 +1000
> From: ***@cyber.com.au
> To: ***@outlook.de
> CC: rsnapshot-***@lists.sourceforge.net
> Subject: Re: [rsnapshot-discuss] WG: result review
>
> Masi,
>
> For those requirements (especially "which day is not important" for
> monthly backups), you could change the timing of rsnapshot monthly
> to run around the middle of the month (say the 15th day of month),
> instead of 1st day of month which most people use.
>
> Then whether the snapshot used for the monthly is a week before or a
> week after the middle of the month, it will still be in the calendar
> month after the previous monthly backup and before the next monthly.
>
> On Sat, Sep 03, 2016 at 10:12:03PM +0200, Masi Osmani wrote:
> > First of all thx for all your explanations and for taking your time.
> >
> > These are my requirements:
> > - to have backups from the the last 7 days
> > - to have backups from the last 4 weeks
> > - to have backups for each past month since backup start
> >
> > lets say i would start on 1.1.2016 then i would expect till today something
> > like this:
> >
> > 03.09 - d0
> > 02.09 - d1
> > 01.09 - d2
> > 31.08 - d3
> > 30.08 - d4
> > 29.08 - d5
> >
> > 28.08 - w0
> > 21.08 - w1
> > 14.08 - w2
> > 07.08 - w3
> >
> > 07.2016 - m0 (which day is not important)
> > 06.2016 - m1
> > 05.2016 - m2
> > 04.2016 - m3
> > 03.2016 - m4
> > 02.2016 - m5
> > 01.2016 - m6
> >
> > I hope you can understand my requirements.
>
> --
> ___________________________________________________________________________
> David Keegel <***@cyber.com.au> Cyber IT Solutions Pty. Ltd.
> http://www.cyber.com.au/~djk/ Linux & Unix Systems Administration
>