Koozali.org formerly Contribs.org

Workstation Backup

Workstation Backup
« on: January 10, 2015, 11:16:00 AM »
Is this how a workstation backup report should look ?

Partial backup stored on backup workstation.
Session cleanly closed by timeout after 82770 seconds.
Not an error, backup process will continue next night.
Received signal: Quit
Archive delayed termination engaged
Disabling signal handler, the next time this signal is received the program will abort immediately
Final memory cleanup...
Program has been aborted for the following reason: Thread cancellation requested, aborting as properly as possible
Error while running dar: 4 at /etc/e-smith/events/actions/workstation-backup-dar line 505.
Backup terminated: backup failed - status: 7424
...

guest22

Re: Workstation Backup
« Reply #1 on: January 10, 2015, 11:26:21 AM »
Maybe you want to follow this http://bugs.contribs.org/show_bug.cgi?id=8789

Re: Workstation Backup
« Reply #2 on: January 10, 2015, 11:40:47 AM »
Thank You. I will follow this bug however I am using SME8.1 and it is not a USB disk so I am not sure if it is fully relevant.

In fact at this time I am not sure if it is a bug or only a limitation. I have done a heap of searching on "Dar backp resume" and similiar but not really turned anything up which is useful.
« Last Edit: January 10, 2015, 11:43:34 AM by p-jones »
...

Offline Stefano

  • *
  • 10,779
  • Skype account: maghissimo
    • Smeserver italian community
Re: Workstation Backup
« Reply #3 on: January 10, 2015, 12:09:30 PM »
how much data to backup? where?
Consulente di Smeserver.it -  Soluzioni e supporto su Sme server in Italia

Offline TerryF

  • *
  • 1,047
Re: Workstation Backup
« Reply #4 on: January 10, 2015, 12:55:00 PM »
Do you have your backup set to timeout at 23hrs?

What is your backup config

db configuration show backupwk

will display your settings from a terminal
--
qui scribit bis legit

Re: Workstation Backup
« Reply #5 on: January 10, 2015, 09:56:40 PM »
Backup is set to time out at 23hrs (with the expectation it will resume and complete). Without the timeout, the job tries to restart before the previous job has completed.

backupwk=service
    BackupTime=23:19
    Compression=6
    CompressionProg=gzip
    DaysInSet=1
    FullDay=7
    IncOnlyTimeout=no
    Login=
    Password=
    Program=dar
    SetsMax=1
    SmbHost=192.168.2.22
    SmbShare=nasstore
    Timeout=23
    VFSType=cifs
    status=enabled

Backing up about 1.5Tb of Data
« Last Edit: January 10, 2015, 11:06:43 PM by p-jones »
...

Offline TerryF

  • *
  • 1,047
Re: Workstation Backup
« Reply #6 on: January 10, 2015, 11:50:24 PM »
How much free space on the target?, default behaviour setup requires 2*dar to complete successfully

Added: can you include the section of log that covers this period and error please
« Last Edit: January 11, 2015, 12:40:37 AM by TerryF »
--
qui scribit bis legit

Re: Workstation Backup
« Reply #7 on: January 11, 2015, 01:08:32 AM »
Jan 10 22:24:34 server2 /sbin/e-smith/do_backupwk[25731]: /home/e-smith/db/backups: OLD 1420798741=backup_record|BackupType|workstation|StartEpochTime|1420798741
Jan 10 22:24:34 server2 /sbin/e-smith/do_backupwk[25731]: /home/e-smith/db/backups: NEW 1420798741=backup_record|BackupType|workstation|EndEpochTime|1420881874|StartEpochTime|1420798741
Jan 10 22:24:34 server2 /sbin/e-smith/do_backupwk[25731]: /home/e-smith/db/backups: OLD 1420798741=backup_record|BackupType|workstation|EndEpochTime|1420881874|StartEpochTime|1420798741
Jan 10 22:24:34 server2 /sbin/e-smith/do_backupwk[25731]: /home/e-smith/db/backups: NEW 1420798741=backup_record|BackupType|workstation|EndEpochTime|1420881874|Result|backup:7424|StartEpochTime|1420798741


There is heaps of room - approx 3-3.5Tb's

After re-reading a link re backup timeouts, setting full backups to timeout at 23hrs is wrong - my bad, and I have kicked off a new backup without that option. Will be 20hrs before I know anything.
...

Offline TerryF

  • *
  • 1,047
Re: Workstation Backup
« Reply #8 on: January 11, 2015, 01:33:58 AM »
There is heaps of room - approx 3-3.5Tb's

A full backup with default settings requires space for twice the size of the backup, there also memory requirements to consider.
--
qui scribit bis legit

Re: Workstation Backup
« Reply #9 on: January 11, 2015, 03:30:02 AM »
Exact amount Data is 1.1Tb. 3-3.5Tb (depending on how you define 1Tb) far exceeds the 2x data. I would have expected 4Gb RAM, an x64 Kernel and zero swapfile useage to suggest the RAM resources were adequate ??

I am still assuming the message I initially posted is incorrect and that my expectation that the backup should just resume is not an incorrect assumption.
...

Offline TerryF

  • *
  • 1,047
Re: Workstation Backup
« Reply #10 on: January 11, 2015, 03:44:06 AM »
You may very well be correct in all assumptions, however without knowing your SME version, config or hardware setup etc, things like this have to be considered.  http://sourceforge.net/p/dar/mailman/message/18851530/

and it may simply be the miss config as you suggest
--
qui scribit bis legit

Offline TerryF

  • *
  • 1,047
Re: Workstation Backup
« Reply #11 on: January 12, 2015, 01:08:54 AM »
There are a number of references to issues that MAY be related to the errors we sometimes see with a failed backup.
eg.
Jan  8 01:12:16 rslserver kernel:  CIFS VFS: sends on sock e8f45b00 stuck for 15 seconds
Jan  8 01:12:16 rslserver kernel:  CIFS VFS: Error -11 sending data on socket to server
Jan  8 01:12:16 rslserver kernel:  CIFS VFS: Write2 ret -11, wrote
and
Jan 11 00:32:43 rslserver kernel:  CIFS VFS: No response to cmd 47 mid 32912
Jan 11 00:32:43 rslserver kernel:  CIFS VFS: Write2 ret -11, wrote 0
Jan 11 00:32:46 rslserver kernel:  CIFS VFS: No response to cmd 47

http://blog.dhampir.no/content/cifs-vfs-no-response-for-cmd-n-mid

Am now running with OpLocks disabled on a system that has displayed intermittent failures for unknown reasons.

Lets see what happens :-)

db configuration setprop smb OpLocks disabled
signal-event ibay-modify

--
qui scribit bis legit

Re: Workstation Backup
« Reply #12 on: January 12, 2015, 01:25:27 AM »
Thank you for that information.

At approx 23hrs 45min the backup stopped in an orderly manner and appears to have resumed where it left off. That is the result of changing the timeout setting. Guess I can only be patient and see where it goes from here !

Re oplocks, I have been running without oplocks for some significant time to accomodate and "old" database which hates op locks.

I have a second identical server that also also runs without op locks for same reason but only has a tiny amount of data and that has backed up totally uneventfully for a long time, same config.

At this point, although perhaps a little prematurely, I am leaning towards answering my initial question that the reports I posted is abnormal and also that I ererred in timing out the full backup. Time will confirm.
...

Offline TerryF

  • *
  • 1,047
Re: Workstation Backup
« Reply #13 on: January 12, 2015, 02:11:24 AM »
The reason I went a looking is because this morning got this cron error report, look familiar?  :-)

Partial backup stored on backup workstation.
Session cleanly closed by timeout after 88500 seconds.
Not an error, backup process will continue next night.
Received signal: Quit
Archive delayed termination engaged
Disabling signal handler, the next time this signal is received the program will abort immediately
Final memory cleanup...
Program has been aborted for the following reason: Thread cancellation requested, aborting as properly as possible
umount: /mnt/smb: device is busy
umount: /mnt/smb: device is busy
umount: /mnt/smb: device is busy
umount: /mnt/smb: device is busy
Error while running dar: 4 at /etc/e-smith/events/actions/workstation-backup-dar line 505.
Backup terminated: backup failed - status: 7424

Full backup failed, and then an inc was done, screwy...

See log extracts above..

Seems to all be related to samba issues..maybe :-)
--
qui scribit bis legit

guest22

Re: Workstation Backup
« Reply #14 on: January 12, 2015, 02:13:26 AM »
About time you guys start report and continue this possible issue over at our Bugzilla :-)