Koozali.org: home of the SME Server

[Announce] Dar - Disk Archive (alpha build)

Offline byte

  • *
  • 2,183
  • +2/-0
[Announce] Dar - Disk Archive (alpha build)
« on: September 18, 2006, 08:09:44 PM »
Over on...

http://bugs.contribs.org/show_bug.cgi?id=1880

there is some great work being made to incorporate the excellent work of Jean-Paul Leclère & Free-EOS (http://free-eos.org) also with Darrell May who brought us Backupws.

Please only report back on the bug shown above as they will probably not see any posts here, so make it easy and post feedback there.
--[byte]--

Have you filled in a Bug Report over @ http://bugs.contribs.org ? Please don't wait to be told this way you help us to help you/others - Thanks!

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #1 on: September 19, 2006, 12:27:42 AM »
byte----
I installed the dar rpm referenced at:
wget http://212.234.119.227/dar-2.3.1-1.i386.rpm
rpm -ivh dar-2.3.1-1.i386.rpm
...then updated the standard e-smith-backup with...
http://bugs.contribs.org/attachment.cgi?id=547
rpm -Uvh e-smith-backup-1.14.0-05jpltest03.noarch.rpm
SME7.0 control panel (for 'Backup or restore') reports that:
'Your server has too much data for a reliable backup to desktop.'
Brief specs:
* SME7 (OS) -  two 75GB in s/w RAID1
* SME7 (data) - 2TB in h/w RAID5 mounted in an iBay.
----best wishes, Robert

Offline jpl

  • *
  • 112
  • +0/-0
[Announce] Dar - Disk Archive (alpha build)
« Reply #2 on: September 19, 2006, 09:17:24 AM »
Quote from: "icpix"

'Your server has too much data for a reliable backup to desktop.'
Brief specs:
* SME7 (OS) -  two 75GB in s/w RAID1
* SME7 (data) - 2TB in h/w RAID5 mounted in an iBay.
----best wishes, Robert


Yes... but it's true, no ?
Is this message preventing workstation backup ?

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #3 on: September 19, 2006, 09:31:33 AM »
jpl----

Cannot agree;~| I have distributed pockets of workstation GBs available.
It is a failing of the calling application that it cannot so distribute the much
needed backup. Darrell's original contrib (Backup2) manages to distribute
backup sets appropriately without issue though it could do with going at it
faster and using incrementals/partials.

No it doesn't 'stop' me from going ahead with a backup attempt despite me
having to so do against a red line warning! Ten hours ago I set the thing
off... I gave it a single hour's window to see what happened. There is
nothing at all on the target/destination share. My CPU util has been showing
circa 95% for a dar process continuously. My OS drive array had some
50 or 60GB space on it originally. 'Something' has filled this up and now
there is about 2GB remaining. Presumably the backup run is now using
my (small) OS drive array to aggregate the backup run for a 2TB (data)
drive array... so I can see why I was given a red line text warning initially.

Presumably I now have to try to abort this thing somehow before the
entire OS drive array space remaining hits the floor... is there a big
red 'OFF' button somewhere?

[postedit] ...too late it's hit the floor, the OS array has 0 bytes left.

----best wishes, Robert

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #4 on: September 19, 2006, 10:21:06 AM »
( duplicate posting )
----best wishes, Robert

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #5 on: September 19, 2006, 10:22:57 AM »
To recover working space on the OS array I deleted some 95 .dar
backup dataset files (CD-sized? ~718MB each) I found remaining on...
/mnt/smb/servername.mydomain/set0/
...and then deleted the /mnt/smb. At no point did I receive any
admin or warning emails nor any indication(s) at the control panel
about what might be or actually was happening.
----best wishes, Robert

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #6 on: September 19, 2006, 12:43:04 PM »
Believe I misinterpreted the function of the box for...
Timeout only incrementals
...which earlier I had ticked (hence the 10hr never-ending marathon?).
Attempted another 1hr (backup window duration) test.
Shortly after the start received these two emails:

Subject: Cron <root@teri> /sbin/e-smith/do_backupwk
Could not resolve mount point /mnt/smb
No terminal found for user interaction. All questions will be assumed a negative answer (less destructive choice), which most of the time will abort the program.
Received signal: Terminated
Archive delayed termination engaged
Disabling signal handler, the next time this signal is received the program will end immediately
Program has been aborted for the following reason: Thread cancellation requested, aborting as properly as possible
umount2: Invalid argument
umount: /mnt/smb: not mounted

Subject: Daily Backup Report
==================================
DAILY BACKUP TO WORKSTATION REPORT
==================================
Backup started at Tue Sep 19 11:30:01 2006
Backup of mysql databases has been done.
Mounting backup shared directory //workstation/sme7-f
Backup shared directory mounted on /mnt/smb
Using set number 0 of 1
Making full backup
Backup directory teri.mydomain/set0 created
Backup base file name is full-20060919
Making backup on temporary dir...
Backup success on shared folder temporary dir
Deleting files on target backup directory
Moving backup files to target directory //workstation/sme7-f/teri.mydomain/set0
Updating backup configuration data
Backup successfully terminated at : Tue Sep 19 11:30:03 2006

This time I've left the /mnt/smb stuff in situ.
There's about 2MB of a single .dar file stored (/mnt/smb/...)
but absolutely nothing has appeared on the target drive share.
Not been brilliant so far;~/
a) never-ending, system filling, backup run that didn't work.
b) A barely started backup run that didn't work.
Did I break something somewhere!?

----best wishes, Robert

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #7 on: September 19, 2006, 02:43:35 PM »
That red line warning was right about the unreliability.
Have unsuccessfully tried three locations on my intranet.
My own workstation, a spare workstation and a NAS box.
All abort shortly after starting:

Subject: Cron <root@teri> /sbin/e-smith/do_backupwk
Code: [Select]
No terminal found for user interaction. All questions will be assumed a negative answer (less destructive choice), which most of the time will abort the program.
Received signal: Terminated
Archive delayed termination engaged
Disabling signal handler, the next time this signal is received the program will end immediately
Program has been aborted for the following reason: Thread cancellation requested, aborting as properly as possible


The file size left at the destination share is ~1.7MB and
which reminds me of the old SCSI days of an unterminated
drive causing errors on the chain but still allowing the first
1MB or 2MB through into the buffer. Seems clear I have
broken something... just let me know what you need.

----best wishes, Robert

Offline jpl

  • *
  • 112
  • +0/-0
[Announce] Dar - Disk Archive (alpha build)
« Reply #8 on: September 19, 2006, 02:57:16 PM »
Quote from: "icpix"
Believe I misinterpreted the function of the box for...
Timeout only incrementals
...which earlier I had ticked (hence the 10hr never-ending marathon?).
Attempted another 1hr (backup window duration) test.
Shortly after the start received these two emails:

Subject: Cron <root@teri> /sbin/e-smith/do_backupwk
Could not resolve mount point /mnt/smb
No terminal found for user interaction. All questions will be assumed a negative answer (less destructive choice), which most of the time will abort the program.
Received signal: Terminated
Archive delayed termination engaged
Disabling signal handler, the next time this signal is received the program will end immediately
Program has been aborted for the following reason: Thread cancellation requested, aborting as properly as possible
umount2: Invalid argument
umount: /mnt/smb: not mounted


Please could you answer next questions :

- What is the value you give to timeout ? 3600 ?
- logs indicates that the server was unable to mount the share. Are you sure that the share configuration was ok, and no other mount deamon was left on the share point ?

Offline jpl

  • *
  • 112
  • +0/-0
[Announce] Dar - Disk Archive (alpha build)
« Reply #9 on: September 19, 2006, 03:02:30 PM »
Quote from: "icpix"
jpl----

Cannot agree;~| I have distributed pockets of workstation GBs available.
It is a failing of the calling application that it cannot so distribute the much
needed backup. Darrell's original contrib (Backup2) manages to distribute
backup sets appropriately without issue though it could do with going at it
faster and using incrementals/partials.


The message that makes you angry is MESSAGE FROM ORIGINAL SME E-SMITH-BACKUP package. Not issued by my modifications.

If you think it must not be issued, create a bug about it on the bugtrack.

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #10 on: September 19, 2006, 03:17:20 PM »
Here's some stuff in the server's message log:
Code: [Select]
Sep 19 13:57:01 teri esmith::event[9383]: S50rewind-tape=action|Event|pre-backup|Action|S50rewind-tape|Start|1158670621 513701|End|1158670621 612080|Elapsed|0.098379
Sep 19 13:57:02 teri kernel: init_special_inode: bogus i_mode (0)
Sep 19 13:57:02 teri kernel: smb_retry: no connection process
Sep 19 13:57:32 teri kernel: smb_add_request: request [f1ec7e00, mid=0] timed out!
Sep 19 13:57:32 teri kernel: smb_delete_inode: could not close inode 2
Sep 19 13:57:32 teri mount.smbfs[9392]: [2006/09/19 13:57:32, 0] client/smbmount.c:send_fs_socket(410)
Sep 19 13:57:32 teri mount.smbfs[9392]:   mount.smbfs: entering daemon mode for service \\workstation\sme7dar, pid=9392
Sep 19 13:57:34 teri kernel: smb_writepage_sync: failed write, wsize=4096, write_ret=-512
Sep 19 13:57:34 teri esmith::event[9408]: Processing event: post-backup  
Sep 19 13:57:34 teri esmith::event[9408]: Running event handler: /etc/e-smith/events/post-backup/S10mysql-delete-dumped-tables
Sep 19 13:57:34 teri esmith::event[9408]: S10mysql-delete-dumped-tables=action|Event|post-backup|Action|S10mysql-delete-dumped-tables|Start|1158670654 378105|End|1158670654 380457|Elapsed|0.002352
Sep 19 13:57:34 teri esmith::event[9408]: Running event handler: /etc/e-smith/events/post-backup/S50rewind-tape
Sep 19 13:57:34 teri esmith::event[9408]: S50rewind-tape=action|Event|post-backup|Action|S50rewind-tape|Start|1158670654 380775|End|1158670654 479030|Elapsed|0.098255
Sep 19 13:57:34 teri /sbin/e-smith/do_backupwk[9382]: /home/e-smith/db/backups: OLD 1158670621=backup_record|BackupType|workstation|StartEpochTime|1158670621
Sep 19 13:57:34 teri /sbin/e-smith/do_backupwk[9382]: /home/e-smith/db/backups: NEW 1158670621=backup_record|BackupType|workstation|EndEpochTime|1158670654|StartEpochTime|1158670621
Sep 19 13:57:34 teri /sbin/e-smith/do_backupwk[9382]: /home/e-smith/db/backups: OLD 1158670621=backup_record|BackupType|workstation|EndEpochTime|1158670654|StartEpochTime|1158670621
Sep 19 13:57:34 teri /sbin/e-smith/do_backupwk[9382]: /home/e-smith/db/backups: NEW 1158670621=backup_record|BackupType|workstation|EndEpochTime|1158670654|Result|0|StartEpochTime|1158670621


Possibly it may be that old issue (smb/samba/login-passwords)... possibly.

----best wishes, Robert

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #11 on: September 19, 2006, 03:22:02 PM »
jpl----
Quote
- What is the value you give to timeout ? 3600 ?
- logs indicates that the server was unable to mount the share. Are you sure that the share configuration was ok, and no other mount deamon was left on the share point ?


What timeout?
Maximum allowed backup time (hours) = 1

Share config was/is OK.
Your application makes new directory structure...
Other mount daemons? I don't know, I'm just the human;~)

----best wishes, Robert

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #12 on: September 19, 2006, 03:26:16 PM »
jpl----
The red line message didn't make me angry.
My ;~| (pursed lips) is for annoyance!
I could not see the point of a backup package that tells
me I cannot backup because I have too much data.
eg "You can't bank here at Barclays/Lloyds bank,
you have too much money... try at Coutts!"
;~))
----best wishes, Robert

Offline jpl

  • *
  • 112
  • +0/-0
[Announce] Dar - Disk Archive (alpha build)
« Reply #13 on: September 19, 2006, 03:28:39 PM »
Quote from: "icpix"
jpl----

No it doesn't 'stop' me from going ahead with a backup attempt despite me
having to so do against a red line warning! Ten hours ago I set the thing
off... I gave it a single hour's window to see what happened. There is
nothing at all on the target/destination share. My CPU util has been showing
circa 95% for a dar process continuously. My OS drive array had some
50 or 60GB space on it originally. 'Something' has filled this up and now
there is about 2GB remaining. Presumably the backup run is now using
my (small) OS drive array to aggregate the backup run for a 2TB (data)
drive array... so I can see why I was given a red line text warning initially.


No, the backup run does not use your OS drive to aggregate anything.

Explication may be more trivial : share is not mounted and the backup was correctly running and saving datas on the server itself... 50 or 60 Gb of compressed data saved in 10 hours seems a normal value for that.

The questions in this case are : why was the share not correctly mounted, and why backup script does not detect it ?

Another point : how workstation dar backup will do to backup 2Tb of datas ?

In theory, it can do it, but not in one night through lan share. You must try to use one set of backup and incremental backup for a lot of days...
The first night the first backup will be stopped by the timeout you set (value is in seconds, not in hours). Not Terabytes of datas will be saved, just tens of Gb. The backup should restart and continue on next nights... until all datas are saved. It's possible only if the daily amount of changed datas is inferior to the amount of datas saved every night.

I think you understand we have not make tests for such amount of datas. But if it works it's a promising test ;-)

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #14 on: September 19, 2006, 03:38:56 PM »
jpl----

It must have used my OS drive to aggregate because that is where I found
all the .dar files sitting, whereas they SHOULD have been across the LAN
on my workstation. For some reason the samba/smb/login-password stuff
is not working...

My 2TB array is not yet full. About 1TB at the moment. It is built up in lots
of directories. These various directories I have to backup over the LAN. It
is not at all important to do it all in one go... a little bit all the time is good.
Much of the data does not change for days or even months.

The control panel says hours so I put in '1'. I will now try 3600;~)

I will work DAR very hard if I can get it to work for me;~)

----best wishes, Robert

Offline jpl

  • *
  • 112
  • +0/-0
[Announce] Dar - Disk Archive (alpha build)
« Reply #15 on: September 19, 2006, 03:42:28 PM »
Quote from: "jpl"


... by the timeout you set (value is in seconds, not in hours).


The bigger is the mistake...

Timeout command use timeout value in seconds. Not easy, so I decided my panel should ask for backup timeout in hours... and I have forgotten hours to seconds conversion in my backup script.

All seems more clear now. You got only a few Mb of datas backuped in... one second.

Thank for pointing this problem.

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #16 on: September 19, 2006, 03:49:11 PM »
jpl----
I tried 3600 but control panel only wants 1-24...
Need another rpm?
----best wishes, Robert

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #17 on: September 19, 2006, 04:07:04 PM »
jpl----
Progress... I am allowed only 1-24 (seconds) in the box so I try 24.
This time my filesize transferred increases from ~1.7MB to 47MB.
ie the max I can now backup in 24secs (approx 144GB/day)
LAN is a gigabit LAN - no other traffic but my workstations.
----best wishes, Robert

Offline jpl

  • *
  • 112
  • +0/-0
[Announce] Dar - Disk Archive (alpha build)
« Reply #18 on: September 19, 2006, 04:13:26 PM »
Quote from: "icpix"
jpl----
I tried 3600 but control panel only wants 1-24...
Need another rpm?
----best wishes, Robert


shure...

But before the new rpm you can set it with the command :

/sbin/e-smith/db configuration setprop backupwk Timeout value_in_seconds

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #19 on: September 19, 2006, 04:19:46 PM »
jpl----
Code: [Select]
/sbin/e-smith/db configuration setprop backupwk Timeout 3600
but how to tell the control panel not to check for 1-24?
----best wishes, Robert

Offline byte

  • *
  • 2,183
  • +2/-0
[Announce] Dar - Disk Archive (alpha build)
« Reply #20 on: September 19, 2006, 04:23:41 PM »
Quote from: "icpix"
jpl----
Code: [Select]
/sbin/e-smith/db configuration setprop backupwk Timeout 3600
but how to tell the control panel not to check for 1-24?
----best wishes, Robert


You would have to run directly from script...

/etc/e-smith/events/actions/workstation-backup-dar

See the bug post by Darrell.
--[byte]--

Have you filled in a Bug Report over @ http://bugs.contribs.org ? Please don't wait to be told this way you help us to help you/others - Thanks!

Offline jpl

  • *
  • 112
  • +0/-0
[Announce] Dar - Disk Archive (alpha build)
« Reply #21 on: September 19, 2006, 04:40:27 PM »
Quote from: "icpix"
jpl----
Code: [Select]
/sbin/e-smith/db configuration setprop backupwk Timeout 3600
but how to tell the control panel not to check for 1-24?
----best wishes, Robert


The problem is not in the check or in the panel, which is correct, but in the subsequent treatment which mut convert hours in seconds.

The modification is here (line 1679 of /etc/e-smith/web/functions/backup) :

Code: [Select]
   if  (( $timeout < 1 ) || ( $timeout > 24 ))
    {
        esmith::cgi::genResult(
            $q, $fm->localise('ERR_INVALID_TIMEOUT')
        );
        return;
    }


must become :

Code: [Select]
   if  (( $timeout < 1 ) || ( $timeout > 24 ))
    {
        esmith::cgi::genResult(
            $q, $fm->localise('ERR_INVALID_TIMEOUT')
        );
        return;
    }
    else
    {
        $timeout = ($timeout*3600)-60;
    }


with this modification, it should be ok.

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #22 on: September 19, 2006, 04:55:30 PM »
jpl----
I edited that file as you wrote.
Still the control panel checks for 1-24.
Do I have to reboot or something?
----best wishes, Robert

Offline jpl

  • *
  • 112
  • +0/-0
[Announce] Dar - Disk Archive (alpha build)
« Reply #23 on: September 19, 2006, 05:22:19 PM »
Quote from: "icpix"
jpl----
I edited that file as you wrote.
Still the control panel checks for 1-24.
Do I have to reboot or something?
----best wishes, Robert


Normal : you give the timeout in hours, but it is now correctly converted in seconds by the script.

You can verify it by typing :

/sbin/e-smith/db configuration getprop backupwk Timeout

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #24 on: September 19, 2006, 05:27:20 PM »
jpl----
I have 3600 (seconds) manually entered.
This is not my problem here.
The control panel, on exit, keeps protesting for values 1-24...
When I go back into the control panel I find what I entered is missing.
Yes, I still have 3600 but this isn't the remaining issue.
----best wishes, Robert

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #25 on: September 19, 2006, 05:31:29 PM »
jpl----
Oh! I see. Your edit makes it into hours and now I must take out
3600 and put in 1... I'm not a programmer (photographer);~)
----best wishes, Robert

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #26 on: September 19, 2006, 05:37:25 PM »
jpl----
Still doesn't work if you go around again in a circle to check.
Now there is a strange number for timeout which itself does
not get accepted after exit (must be 1-24)...
----best wishes, Robert

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #27 on: September 19, 2006, 06:02:50 PM »
jpl----
It still doesn't make sense to me.
Yes, I know I am not a programmer but I can do maths.
Your code says:
$timeout = ($timeout*3600)-60;
...that '-' minus symbol... maybe it should be a divide symbol '/'?
Try for 1hrs when I return to the control panel it is 3540 (1x3600)-60.
Try for 2hrs when I return to the control panel it is 7140 (2x3600)-60.
----best wishes, Robert

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #28 on: September 19, 2006, 06:52:52 PM »
How do I kill this thing? I've let it do its stuff for over the nominal '1hr' for
which it was configured. It's taking 98% CPU utilisation and there are no
files in the destination share (yet?). The OS drive's space hasn't gone
down by anything significant so just what DAR is doing with 98% of a
pair of 3.4GHz Xeons without producing I do not know. 'htop' shows
PID 14219 for the DAR process... how do I stop DAR?
----best wishes, Robert

Offline byte

  • *
  • 2,183
  • +2/-0
[Announce] Dar - Disk Archive (alpha build)
« Reply #29 on: September 19, 2006, 07:00:45 PM »
type...

kill 14219

but be careful when using the kill command. do a man kill for more usage
--[byte]--

Have you filled in a Bug Report over @ http://bugs.contribs.org ? Please don't wait to be told this way you help us to help you/others - Thanks!

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #30 on: September 19, 2006, 07:07:23 PM »
byte---
It's still running after 'kill 14219'.
Have you got any 'Parazone/DDT'-flavoured commands?
ie anything stronger?
----best wishes, Robert

Offline byte

  • *
  • 2,183
  • +2/-0
[Announce] Dar - Disk Archive (alpha build)
« Reply #31 on: September 19, 2006, 07:11:23 PM »
Then you will need to have a read and find out how to use the "kill" command more effective.
--[byte]--

Have you filled in a Bug Report over @ http://bugs.contribs.org ? Please don't wait to be told this way you help us to help you/others - Thanks!

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #32 on: September 19, 2006, 07:27:29 PM »
byte----
I see nothing in man kill(1) to strengthen the scope of 'kill 14219'.
It mentions kill(2) but I can't for the moment see how to access (2).
Oh well
#console
#reboot
should do the trick;~)
----best wishes, Robert

Offline byte

  • *
  • 2,183
  • +2/-0
[Announce] Dar - Disk Archive (alpha build)
« Reply #33 on: September 19, 2006, 07:33:18 PM »
Going OT now, but you would have used kill -9 pid number
--[byte]--

Have you filled in a Bug Report over @ http://bugs.contribs.org ? Please don't wait to be told this way you help us to help you/others - Thanks!

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #34 on: September 19, 2006, 07:39:39 PM »
byte----
Actually I tried 'kill (9) 14219' but I should've thought of '-9';~)
Needed to reboot to eyeball the bootup graphics for EL or ELsmp.
Will continue in other thread (more point).
----best wishes, Robert

Offline jpl

  • *
  • 112
  • +0/-0
[Announce] Dar - Disk Archive (alpha build)
« Reply #35 on: September 19, 2006, 08:25:02 PM »
Quote from: "icpix"
jpl----
It still doesn't make sense to me.
Yes, I know I am not a programmer but I can do maths.
Your code says:
$timeout = ($timeout*3600)-60;
...that '-' minus symbol... maybe it should be a divide symbol '/'?
Try for 1hrs when I return to the control panel it is 3540 (1x3600)-60.
Try for 2hrs when I return to the control panel it is 7140 (2x3600)-60.
----best wishes, Robert


The meaning of the formule is : n hours minus 1 minute

The minute is kept in case of 24h to cleanly stop running backup before cron start a new backup job.

About the panel : why do you come back to the configuration panel ?

The given modification is just a temporary solution. Yes if you enter 1 hour and go again to configuration you see 3540, and must re-enter 1.
But it permits you to do configuration. All will be ok in next rpm.

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #36 on: September 19, 2006, 08:47:55 PM »
jpl----
Understood, my thanks.
I look forward to the new rpm.
Had difficulty stopping the DAR process when I could see it was
'doing' nothing at all productive except using nearly 98% CPU.
Is this an appropriate way to stop it...
root# kill -9 PIDnumber
...where the PIDnumber is the PID shown for DAR in 'htop'?
----best wishes, Robert

Offline jpl

  • *
  • 112
  • +0/-0
[Announce] Dar - Disk Archive (alpha build)
« Reply #37 on: September 19, 2006, 11:09:19 PM »
Quote from: "icpix"
jpl----
Had difficulty stopping the DAR process when I could see it was
'doing' nothing at all productive except using nearly 98% CPU.
Is this an appropriate way to stop it...
root# kill -9 PIDnumber


Yes it'is a good way to kill it, but don't forget to kill also the mount process for the share if it runs.

For 95% or 98% CPU it is also normal.
Nigthly backup often occurs when no other task needs CPU. Also by default dar-workstation backup uses maximum compression algorithm and... maximum CPU disponibility. But compression effort can be decreased from 9 to 0 by templating. In this case load of the CPU must not be very hard (but I can't think it's a good idea to backup while your server is busy)

Perhaps (apart from the timeout format bug) all your problem is one unique problem : user used in configuration doesn't have rights to write on the mounted share.

In this case maybe the script detect that the share is correctly mounted, but it doesn't detect the fact that you cannot write in it. Could you - after a reboot - start a backup and see if the shared folder is really mounted and if the server can write in it ?

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #38 on: September 19, 2006, 11:23:48 PM »
jpl----

SME7 box has dual 3.4GHz Xeons. At the moment it serves just me.
Later (when more problems are fixed) it goes on-line for web sites
and email but still used (on gigabit intranet) with picture library for me.
98% CPU utilisation for one CPU is OK. My problem was/is that I now
realise SME7 box now uses only one CPU and not two CPUs;~( That
was why I needed to kill the DAR process! Something is now different
between SME7 beta's and gold. What - Why - How to fix! Reload...?

Everywhere here user is admin/root. Not best I know but only me.

Yes, I try again, now or soon. For some reason I am very good
at breaking new software/hardware - my curse? ability? whatever;~)

----best wishes, Robert

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #39 on: September 20, 2006, 01:16:37 AM »
jpl----

While testing or at least trying to use/run DAR was dealing with a CPU
issue that I have now been able to fix with everyone's help. Don't think
that it affected DAR except the SME7 box not having its usual 'grunt'.

Trying to implement another test run. It's now just after midnight.
There may be an issue to address... it's between the control panel
checking algorithm and the use of your AM/PM and whatever DAR
is expecting. Can't seem to find the right combination to kick it off...
0.01 AM
12.01 AM
...around this particular witching hour. To me this time is 0001hrs
(24hr clock) but the old Backup package uses AM/PM but something
perhaps doesn't match between what is expected to be keyed in and
what the equations want/need afterwards. Also what is acknowledged
afterwards right at the top of the screen...

Or maybe I'm just too tired;~/

----best wishes, Robert

Offline Tib

  • *
  • 571
  • +0/-0
    • http://www.tibors.net
[Announce] Dar - Disk Archive (alpha build)
« Reply #40 on: September 20, 2006, 03:09:16 AM »
icpix

Have a look at the bug tracker ... you can follow whats been hapening.

http://bugs.contribs.org/show_bug.cgi?id=1880

Regards,

Tib

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #41 on: September 20, 2006, 03:24:36 AM »
jpl----

I left DAR set for 1.00AM and so off it went...

Using mc I see /mnt/smb with temporary folder and a domain folder.
At the moment the temporary path contains some.dar archives. There
is nothing at all in the domain folder other than an empty /set2 folder.
Certainly nothing yet appeared on the destination share of the LAN.
So, DAR *is* aggregating its backups of my server ON the server.
I don't know at what point or when it will transfer them to the given
destination drive ie over the LAN. That it is NOT doing this, as and
when system logistics allows, is disappointing because this has poor
implications for a site (mine) with up to 2TB dataset to backup.

Half way through the given 1hr backup window (if it works) and there
are now some five .dar archives in the temporary folder area but
still occupying space on the server's smallest drives. There is nothing
on the target/destination drive.

Having 'fixed' my second CPU (thanks to byte/Tib) I manually set off a
ClamAV run concurrently to the backup run. Now both CPUs are at peak
activity with the average CPU utilisation showing as 100% (htop). It's
getting warmer around here;~)

At the end of the allotted hour DAR *did* actually stop;~)
There are ten and a half .dar archives sitting in the domain path area
under the /set2 folder. There is *nothing* on the target drive across
the LAN but I don't know if that is because they are *now* in transit
or whether DAR might not have been able to write on the target(?).

<see if the shared folder is really mounted and if the server can write in it ?>
I don't know how to properly check what you have asked.

It's late (2.30am) - been a long day - much activity - g'night;~)

----best wishes, Robert

icpix

[Announce] Dar - Disk Archive (alpha build)
« Reply #42 on: September 20, 2006, 03:29:55 AM »
Tib----
Yes, I dive in and look sometimes.
It's very technical in there, mostly too difficult for me;~/
I stay away from it if I can;~)
The glitch (for jpl----) about the witching hour is different to
what was discussed about the merits of AM/PM and that of
matching the flavour of the existing Backup & Restore package.
Always match - Never advance - Never fix... is my view.
Should Always improve - Assessed each time.
(Many thanks again for the help in the dual CPU thread)
----best wishes, Robert (g'night)

Offline jpl

  • *
  • 112
  • +0/-0
[Announce] Dar - Disk Archive (alpha build)
« Reply #43 on: September 20, 2006, 03:54:11 PM »
Quote from: "icpix"
jpl----

Using mc I see /mnt/smb with temporary folder and a domain folder.
At the moment the temporary path contains some.dar archives. There
is nothing at all in the domain folder other than an empty /set2 folder.
Certainly nothing yet appeared on the destination share of the LAN.
So, DAR *is* aggregating its backups of my server ON the server.


There is only one reason that can make dar write on your server : the share  is not mounted correctly.

Normally, the script could detcet it, but it seems the rpm lacks creation of one directory.

Please :

- on your server, delete all directories under /mnt/smb (be sure the share is not mounted, ie after a reboot)
- create the directory /mnt/smb/smbmount-failure

This will prevent dar to do backups on the server itself.

Quote

I don't know at what point or when it will transfer them to the given
destination drive ie over the LAN.


Never, because the temporary directory should be on the destination system, not on the server (and would be in case of correct mount of the share).

Quote
At the end of the allotted hour DAR *did* actually stop;~)
There are ten and a half .dar archives sitting in the domain path area
under the /set2 folder.

Good in itself. If the share had been mounted, all where ok and the backup session would be correct.

Quote

There is *nothing* on the target drive across
the LAN but I don't know if that is because they are *now* in transit
or whether DAR might not have been able to write on the target(?).

There are not in transit. The explenation is the same : they would have been on the target if the shared had been correctly mounted.

Offline dmay

  • *
  • 450
  • +0/-0
    • http://myezserver.com
[Announce] Dar - Disk Archive (alpha build)
« Reply #44 on: September 20, 2006, 04:51:58 PM »
The original post stated all feedback should go to the Bugzilla ticket. All your problems encountered have been addressed and answered in the ticket. FYI this is an alpha build that will change substantially from day-to-day as new feedback is received, problems identified and fixed and new ideas implemented. If you are keen to play along, the playpen is Bugzilla  :wink:  Not here.

Darrell

Offline Denbert

  • *
  • 156
  • +0/-0
    • hegnstoften.net
[Announce] Dar - Disk Archive (alpha build)
« Reply #45 on: September 21, 2006, 05:01:46 PM »
Trying to install this on a test server:

[root@server1 DAR]# rpm -Uvh smeserver-backup2-1.0.0-b2dmay.noarch.rpm
error: Failed dependencies:
        perl-CGI-FormMagick >= 0.92-08 is needed by smeserver-backup2-1.0.0-b2dmay.noarch
        rar >= 3.5.1-7 is needed by smeserver-backup2-1.0.0-b2dmay.noarch


I’m obviously doing something wrong here, anyone please  :hammer:
/ Denbert
"Success is not final, failure is not fatal: it is the courage to continue that counts" - Sir Winston Churchill

Offline jpl

  • *
  • 112
  • +0/-0
[Announce] Dar - Disk Archive (alpha build)
« Reply #46 on: September 21, 2006, 11:10:55 PM »
Quote from: "Denbert"

I’m obviously doing something wrong here, anyone please  :hammer:


This discussion is not about smeserver-backup2 but about e-smith-backup with dar integration.

see http://bugs.contribs.org/show_bug.cgi?id=1880

Offline dmay

  • *
  • 450
  • +0/-0
    • http://myezserver.com
[Announce] Dar - Disk Archive (alpha build)
« Reply #47 on: September 23, 2006, 05:15:31 PM »
Call for testers:

http://bugs.contribs.org/show_bug.cgi?id=1880#c160
http://bugs.contribs.org/show_bug.cgi?id=1880#c155

Please remember this is an alpha build :hammer: for non-production use only.

Feedback only to the Bug Tracker please. :wink:

Darrell