Backup fail after upgrade

backup
v7

(Enrique D) #1

NethServer Version: 7.6.1810 (final)
Module: Backup

Backup: backup-data
Backup started at 2018-12-18 02:00:01
Event pre-backup-data: FAIL
Backup status: FAIL
Log file: /var/log/backup/backup-backup-data-201812180200.log

It was working at: backup-backup-data-201812170200.log

Action 'backup-data-duplicity ': SUCCESS
Post backup scripts status: SUCCESS
Backup status: SUCCESS
Backup ended at 2018-12-17 02:00:37
Time elapsed: 0 hours, 0 minutes, 36 seconds
Disk Usage:
Size Used Available Use%
912.23 GB 182.65 GB 729.59 GB 20.02%

The backup configuration is using a CIFS share:


I see here that NFS is more recommended.
I don’t remember if NFS fails for me the first time that I try instead of CIFS; I’ll try to use a NFS share. (and post my finds laters).
Regards


(Dan) #2

If the backup log doesn’t explain why this is, the system log (/var/log/messages) should. Try grep -C 20 pre-backup-data /var/log/messages and see what it tells you.


(Enrique D) #3

Thank you, maybe something is broken after the upgrade in (samba); I will try to use the NFS instead (need to find time to do it… now! :fire: :fire_extinguisher:)

Dec 18 02:00:44 ads kernel: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
Dec 18 02:00:45 ads kernel: CIFS VFS: Dialect not supported by server. Consider specifying vers=1.0 or vers=2.0 on mount for accessing older servers
Dec 18 02:00:45 ads kernel: CIFS VFS: cifs_mount failed w/return code = -95
Dec 18 02:00:45 ads esmith::event[26344]: Error while mounting 192.168.xx.yy:nhs : mount error(95): Operation not supported Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Dec 18 02:00:45 ads esmith::event[26344]: Action: /etc/e-smith/events/pre-backup-data/S70mount-cifs FAILED: 32 [0.844304]
Dec 18 02:00:45 ads esmith::event[26344]: Action: /etc/e-smith/events/pre-backup-data/S70mount-nfs SUCCESS [0.842365]
Dec 18 02:00:46 ads esmith::event[26344]: Action: /etc/e-smith/events/pre-backup-data/S70mount-usb SUCCESS [0.204948]
Dec 18 02:00:46 ads esmith::event[26344]: Action: /etc/e-smith/events/pre-backup-data/S70mount-webdav SUCCESS [0.176115]
Dec 18 02:00:46 ads esmith::event[26344]: Event: pre-backup-data FAILED


Dec 19 02:00:15 ads kernel: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
Dec 19 02:00:15 ads kernel: CIFS VFS: Dialect not supported by server. Consider specifying vers=1.0 or vers=2.0 on mount for accessing older servers
Dec 19 02:00:15 ads kernel: CIFS VFS: cifs_mount failed w/return code = -95
Dec 19 02:00:15 ads esmith::event[24115]: Error while mounting 192.168.xx.yy:nhs : mount error(95): Operation not supported Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Dec 19 02:00:15 ads esmith::event[24115]: Action: /etc/e-smith/events/pre-backup-data/S70mount-cifs FAILED: 32 [0.181508]
Dec 19 02:00:16 ads esmith::event[24115]: Action: /etc/e-smith/events/pre-backup-data/S70mount-nfs SUCCESS [0.156214]
Dec 19 02:00:16 ads esmith::event[24115]: Action: /etc/e-smith/events/pre-backup-data/S70mount-usb SUCCESS [0.149504]
Dec 19 02:00:16 ads esmith::event[24115]: Action: /etc/e-smith/events/pre-backup-data/S70mount-webdav SUCCESS [0.155374]
Dec 19 02:00:16 ads esmith::event[24115]: Event: pre-backup-data FAILED


(Paolo Fornara) #4

Hi,

Quite sure you’re trying to mount and old protocol (1.0) CIFS share from Nethserver.

You need to specify -o vers=1.0 in backup mount script:

/etc/e-smith/events/actions/mount-cifs

Correct Line:

$err = qx(/bin/mount -t cifs “//$smbhost/$smbshare” $mntdir -o vers=1.0,credentials=$tmp,nounix 2>&1);

King Regards

Paolo


(Enrique D) #5

Thank you!, It was working before the upgrade, maybe the NAS has the shared folder using the old SMB v1.0 protocol

This is a Synology NAS, and the services is configured as:
image

Right now I put the same share as a NFS.

I wonder how can I force test a backup from the GUI or Terminal?

  • added image

(Paolo Fornara) #6

Honestly I do not know , but you could try scheduling backup job now+1 min and see what happens.


(Enrique D) #7

Reading the Backup documentation.
I run this and it doesn’t show anything; is that correct?

# db backups show
#

BTW, I modified the maximum protocol in the nas/synology to use SMB3.
Hoping it fix the issue.


(Dan) #8

/sbin/e-smith/backup-data


(Paolo Fornara) #9

Same behaviour for me.

# db backups show

do not display anything on cli.


(Dan) #10

Including the same error message? Then try the same troubleshooting steps already recommended up-thread.


(Marc) #11

It’s normal. “backups” database is for multiple backups feature (available from command line, not from server-manager), and you’ve single backup configuration which can be seen using this command:

config show backup-data

(Enrique D) #12

Greetings, I take a day out at work, after changing the SMB protocol version to max 3 it works again, the “config show backup-data” shows:

config show backup-data
backup-data=configuration
    BackupTime=2:00
    CleanupOlderThan=28D
    FullDay=6
    IncludeLogs=disabled
    NFSHost=192.168.xx.14
    NFSShare=/volume1/nhs
    Notify=always
    NotifyFrom=
    NotifyTo=sist@domain.com
    Program=duplicity
    SMBHost=192.168.xx.14
    SMBLogin=[...]
    SMBPassword=****
    SMBShare=nhs
    Type=incremental
    USBLabel=
    VFSType=cifs
    VolSize=250
    WebDAVLogin=
    WebDAVPassword=
    WebDAVUrl=
    status=enabled
Backup: backup-data
Backup started at 2018-12-21 02:00:01
Pre backup scripts status: SUCCESS
--------------[ Backup Statistics ]--------------
StartTime 1545382829.69 (Fri Dec 21 02:00:29 2018)
EndTime 1545382835.53 (Fri Dec 21 02:00:35 2018)
ElapsedTime 5.84 (5.84 seconds)
SourceFiles 10693
SourceFileSize 4321155853 (4.02 GB)
NewFiles 10
NewFileSize 1526328 (1.46 MB)
DeletedFiles 12
ChangedFiles 110
ChangedFileSize 93412798 (89.1 MB)
ChangedDeltaSize 0 (0 bytes)
DeltaEntries 132
RawDeltaSize 7488816 (7.14 MB)
TotalDestinationSizeChange 3024401 (2.88 MB)
Errors 0

Action 'backup-data-duplicity ': SUCCESS
Post backup scripts status: SUCCESS
Backup status: SUCCESS
Backup ended at 2018-12-21 02:00:38
Time elapsed: 0 hours, 0 minutes, 37 seconds

Disk Usage:
      Size       Used  Available     Use%
 912.23 GB  182.43 GB  729.80 GB      20%
Log file: /var/log/backup/backup-backup-data-201812210200.log

(Hris Angelo) #13

Hello and Happy new year!
I have same problem today after upgrade NS from 7.5 to 7.6

Backup: backup-data
Backup started at 2019-01-04 11:13:01
Pre backup scripts status: SUCCESS
Attempt 1 failed. IOError:
Attempt 2 failed. IOError:
Attempt 3 failed. IOError:
Attempt 4 failed. IOError:
Giving up after 5 attempts. IOError:
Duplicity backup failed
Action 'backup-data-duplicity ': FAIL
Backup status: FAIL

I tried this but did not work for me. Data backup clean-up
how can i fix it? thanks in advance!


(David) #14

same issue here!
I don’t understand, why there is only "IOError: " and no explanation after the colon…


(Stéphane de Labrusse) #15

No errors in /var/log/messages ?
cc @giacomo @Tyno


(Giacomo Sanchietti) #16

It’s the duplicity output, maybe something is not currently mounted?

There is no simple way to debug it if duplicity doesn’t show the output …


(David) #17

no nothing to see here


(David) #18

the drive is mounted.
I configured the backup from the cockpit UI and disabled the backup in the old UI, maybe that’s an issue?
Also things worked for some weeks and then it suddenly started…


(Giacomo Sanchietti) #19

So it seems more an error on the destination side.

Could you try to change the protocol? Maybe from SMB to NFS?


(David) #20

the strange thing is, that it’s an USB. I formatted it with ext3
according tothe nethserver-manual…