Fruitless attempt to re-set-up Cron-scheduled backups

[Fuddyduddy]

@fvdw

Thanks for keeping me posted.

I hope the family reasons are happy ones not misfortunes.

Best wishes in any case.

[Jocko]

Hi Fuddyduddy,

Btw I've realised that in my previous post dated Apr 5 I sent the wrong job lines; here are the right ones

Code: Select all

0 19 */3 * * /usr/bin/php '/share/1000/cronjobs/Rsync_USB-NAS_backup_1.from.My_Movies_jr9VB9.php' >>/share/1000/cronjobs/cron.log

Code: Select all

0 20 */2 * * /usr/bin/php '/share/1000/cronjobs/Rsync_USB-NAS_backup_1.from.Recorded_TV_YNTgFT.php' >>/share/1000/cronjobs/cron.log

Five days have since gone by, so two backups ought to have been made of the second of these jobs and one of the other. But when I look in the log in fvdw there is no activity recorded since Apr 4! And furthermore whilst the log records 39 files being transferred to the Recorded_TV destination folder on that date, when I look into the backup today I find only two!

Do you have a trace on the cron log file ? If not that means these cron jobs did not perform.
To see if cron daemon runs really, can you post:
- a screen capture of the main cron menu.
- the output of the command line

Code: Select all

 ps auxw|grep cron

[Fuddyduddy]

Hi Jocko

Output of the command

Code: Select all

login as: root
root@192.168.11.5's password:
root@fvdwsl-base:/ # ps auxw | grep cron
root      1450  0.0  0.2   3656   628 ?        Ss   May15   0:00 /usr/sbin/crond -c /share/1000/cronjobs -L /share/1000/cronjobs/cron.log
root      4631  0.0  0.4   5804  1208 pts/0    S+   22:36   0:00 grep cron
root@fvdwsl-base:/ #


Screenshot attached.

The most recent entries in the Cron log all look like this

Code: Select all

crond: USER root pid 4402 Rsync script started at : 2017-05-16_20:00:10
crond: USER root pid 4402 No write access on USB drive !
crond: USER root pid 4402 Rsync script ended at : 2017-05-16_20:00:11

[Jocko]

Hi Fuddyduddy,

So now the issue is identified!

There is no issue on the cron side or the backup script but only how the USB disk is mounted!

Code: Select all

crond: USER root pid 4402 No write access on USB drive !

It seems this one is mounted with the readonly option.

This may happens :
-if the fs on the USB is corrupted
-You have a ntfs fs on it and you did not activate the write access on it (use ntfs-3g driver). See the USB disk menu.

Can you post the output of

Code: Select all

mount

[Fuddyduddy]

Can you post the output of

Code: Select all

mount

Here it is

Code: Select all

login as: root
root@192.168.11.5's password:
root@fvdwsl-base:/ # mount
rootfs on / type rootfs (rw)
/dev/root on / type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
/dev/sda2 on / type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600)
/dev/sda5 on /rw_fs type ext3 (rw,noatime,errors=continue,barrier=1,data=ordered)
tmpfs on /rw_fs/tmp/usr/var type tmpfs (rw,relatime,size=5000k)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
/dev/sdb1 on /rw_fs/tmp/mnt/NAS_backup_1 type ntfs (ro,relatime,uid=0,gid=0,umask=0222,nls=utf8,errors=continue,mft_zone_multiplier=1)
/dev/sda8 on /share/1000 type ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=1,data=ordered)
/dev/sdb1 on /share/1000/NAS_backup_1 type ntfs (ro,relatime,uid=0,gid=0,umask=0222,nls=utf8,errors=continue,mft_zone_multiplier=1)
/dev/root on /lacie-boot type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered)
root@fvdwsl-base:/ #


[Jocko]

Hi Fuddyduddy,

So the issue is you did not enable the ntfs-3g driver !

Code: Select all

/dev/sdb1 on /share/1000/NAS_backup_1 type ntfs (ro,relatime,uid=0,gid=0,umask=0222,nls=utf8,errors=continue,mft_zone_multiplier=1)

The default driver can mount a ntfs filesystem only with the readonly option: 'ro' and umask 222

You must enable ntfs-3g driver on the usb disk menu (help page gives more details)

[Fuddyduddy]

Jocko

Is this better?

Code: Select all

login as: root
root@192.168.11.5's password:
root@fvdwsl-base:/ # mount
rootfs on / type rootfs (rw)
/dev/root on / type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
/dev/sda2 on / type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600)
/dev/sda5 on /rw_fs type ext3 (rw,noatime,errors=continue,barrier=1,data=ordered)
tmpfs on /rw_fs/tmp/usr/var type tmpfs (rw,relatime,size=5000k)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
/dev/sda8 on /share/1000 type ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=1,data=ordered)
/dev/root on /lacie-boot type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered)
/dev/sdc1 on /rw_fs/tmp/mnt/NAS_backup_1 type fuseblk (rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
/dev/sdc1 on /share/1000/NAS_backup_1 type fuseblk (rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
root@fvdwsl-base:/ #


[Jocko]

Yes Fuddyduddy,

Now the firmware uses ntfs-3g driver to mount your USb drive (type fuseblk) and you have a read/write access on it (rw) :thumbup

So now you should have no longer issue with your backups.

Otherwise with your cron jobs, two backups may run on the same time at every 6 days (one every 2 days and the other every 3 days)which will have an impact on the backup duration and should have an impact on the NAS performances). Indeed if you have many data to backup, an offset of one hour between these two jobs is not enough.

[Fuddyduddy]

Hi Jocko

That's very good to hear, and thanks a lot for your patience.
I will re-schedule one of the backups so as to separate them more widely (thanks for spotting that) but as well as doing that I'd like, if I may, to try your patience a little more :please

It seems that this other thread I started viewtopic.php?f=11&t=2670 has been overlooked. I'd be most grateful to have your advice on it.