Koozali.org: home of the SME Server

flexbackup to disk on server is backing up backup files

Pascal Van Hecke

flexbackup to disk on server is backing up backup files
« on: February 26, 2003, 01:55:14 PM »
Hi,

I followed the instructions on http://mirror.contribs.org/smeserver/contribs/dmay/mitel/howto/flexbackup-to-disk-howto.html but instead of backing up to a client pc, I use a third hard disk on the sme server it self (other two disks in raid).

So instead of
//servername/sharename  /mnt/backup  smbfs   username=name,password=pword
in /etc/fstab
I added
/dev/hdg /mnt/backup

The script runs well, mounting and unmounting the third hard disk, but strangely enough it backs up the mounted backup disk itself, resulting in an exponentially growing file until it breaks on the 2 meg limit, and then the process continues until the disk is full with 2 meg files...

Are there any other people having this problem?

I 'll paste the mailed log here, maybe that'll give a clue.

pascal van hecke


flexbackup version 0.9.8
/etc/flexbackup.conf syntax OK

|------------------------------------------------
| Archiving to file; "mt setblk 0" skipped
| Doing level 0 backup of all using dump
| Retensioning tape...
| Archiving to file; "mt retension" skipped
| Rewinding & erasing tape...
| Archiving to file; "mt rewind" skipped
| Archiving to file; "mt rewind" skipped
| Directory's existing key is 200302150042.01
| Tape #0
| Filesystems = / /boot /mnt/backup
|------------------------------------------------
| Archiving to file; "mt tell" skipped
|------------------------------------------------
| File number 10, index key 200302150042.01
| Backup of: /
| Date of this level 0 backup: Tue Feb 25 03:00:01 2003
| Date of last level 0 backup: the epoch
|------------------------------------------------
| (dump -0 -b 10 -a -f - / | gzip -4) | buffer -m 3m -s 10k -t -p 75 -B -o \
|  /mnt/backup/root.0.20030225.dump.gz
|------------------------------------------------
  DUMP: Date of this level 0 dump: Tue Feb 25 03:00:01 2003
  DUMP: Dumping /dev/md1 (/) to standard output
  DUMP: Added inode 8 to exclude list (journal inode)
  DUMP: Added inode 7 to exclude list (resize inode)
  DUMP: Label: /
  DUMP: mapping (Pass I) [regular files]
  DUMP: mapping (Pass II) [directories]
  DUMP: estimated 1412597 tape blocks.
  DUMP: Volume 1 started with block 1 at: Tue Feb 25 03:00:24 2003
  DUMP: dumping (Pass III) [directories]
  DUMP: dumping (Pass IV) [regular files]
  DUMP: Volume 1 completed at: Tue Feb 25 03:03:07 2003
  DUMP: Volume 1 1472890 tape blocks (1438.37MB)
  DUMP: Volume 1 took 0:02:43
  DUMP: Volume 1 transfer rate: 9036 kB/s
  DUMP: 1472890 tape blocks (1438.37MB)
  DUMP: finished in 163 seconds, throughput 9036 kBytes/sec
  DUMP: Date of this level 0 dump: Tue Feb 25 03:00:01 2003
  DUMP: Date this dump completed:  Tue Feb 25 03:03:07 2003
  DUMP: Average transfer rate: 9036 kB/s
  DUMP: DUMP IS DONE
Kilobytes Out 437140
|------------------------------------------------
| Backup start: Tue Feb 25 03:00:01 2003
| Backup end:   Tue Feb 25 03:03:07 2003
|------------------------------------------------
| Archiving to file; "mt tell" skipped
|------------------------------------------------
| File number 11, index key 200302150042.01
| Backup of: /boot
| Date of this level 0 backup: Tue Feb 25 03:03:08 2003
| Date of last level 0 backup: the epoch
|------------------------------------------------
| (dump -0 -b 10 -a -f - /boot | gzip -4) | buffer -m 3m -s 10k -t -p 75 -B -o \
|  /mnt/backup/boot.0.20030225.dump.gz
|------------------------------------------------
  DUMP: Date of this level 0 dump: Tue Feb 25 03:03:08 2003
  DUMP: Dumping /dev/md0 (/boot) to standard output
  DUMP: Added inode 8 to exclude list (journal inode)
  DUMP: Added inode 7 to exclude list (resize inode)
  DUMP: Label: /boot
  DUMP: mapping (Pass I) [regular files]
  DUMP: mapping (Pass II) [directories]
  DUMP: estimated 4791 tape blocks.
  DUMP: Volume 1 started with block 1 at: Tue Feb 25 03:03:08 2003
  DUMP: dumping (Pass III) [directories]
  DUMP: dumping (Pass IV) [regular files]
  DUMP: Volume 1 completed at: Tue Feb 25 03:03:09 2003
  DUMP: Volume 1 4780 tape blocks (4.67MB)
  DUMP: Volume 1 took 0:00:01
  DUMP: Volume 1 transfer rate: 4780 kB/s
  DUMP: 4780 tape blocks (4.67MB)
  DUMP: finished in 1 seconds, throughput 4780 kBytes/sec
  DUMP: Date of this level 0 dump: Tue Feb 25 03:03:08 2003
  DUMP: Date this dump completed:  Tue Feb 25 03:03:09 2003
  DUMP: Average transfer rate: 4780 kB/s
  DUMP: DUMP IS DONE
Kilobytes Out 2590
|------------------------------------------------
| Backup start: Tue Feb 25 03:03:08 2003
| Backup end:   Tue Feb 25 03:03:09 2003
|------------------------------------------------
| Archiving to file; "mt tell" skipped
|------------------------------------------------
| File number 12, index key 200302150042.01
| Backup of: /mnt/backup
| Date of this level 0 backup: Tue Feb 25 03:03:09 2003
| Date of last level 0 backup: the epoch
|------------------------------------------------
| (dump -0 -b 10 -a -f - /mnt/backup | gzip -4) | buffer -m 3m -s 10k -t -p 75 \
|  -B -o /mnt/backup/mnt-backup.0.20030225.dump.gz
|------------------------------------------------
  DUMP: Date of this level 0 dump: Tue Feb 25 03:03:09 2003
  DUMP: Dumping /dev/hdg1 (/mnt/backup) to standard output
  DUMP: Added inode 8 to exclude list (journal inode)
  DUMP: Added inode 7 to exclude list (resize inode)
  DUMP: Label: none
  DUMP: mapping (Pass I) [regular files]
  DUMP: mapping (Pass II) [directories]
  DUMP: estimated 22815510 tape blocks.
  DUMP: Volume 1 started with block 1 at: Tue Feb 25 03:03:34 2003
  DUMP: dumping (Pass III) [directories]
  DUMP: dumping (Pass IV) [regular files]
  DUMP: 8.14% done at 6194 kB/s, finished in 0:56
buffer (writer): write of data failed: Success
bytes to write=10240, bytes written=2047, total written    2097150K
  DUMP: Broken pipe
  DUMP: The ENTIRE dump is aborted.
|------------------------------------------------
| Backup start: Tue Feb 25 03:03:09 2003
| Backup end:   Tue Feb 25 03:09:14 2003
|------------------------------------------------
| Archiving to file; "mt tell" skipped
|------------------------------------------------
| Rewinding...
| Archiving to file; "mt rewind" skipped
| Compressing log (all.0.20030225.gz)
| Linking all.latest.gz -> all.0.20030225.gz
|------------------------------------------------

File  Contents    (tape index 200302150042.01)
-----------------------------------------------
0  
1   level 0 / Sat Feb 15 00:42:01 2003 from newfabiola (root.0.20030215.dump.gz)
2   level 0 /boot Sat Feb 15 00:44:46 2003 from newfabiola (boot.0.20030215.dump.gz)
3   level 0 /mnt/backup Sat Feb 15 00:44:48 2003 from newfabiola (mnt-backup.0.20030215.dump.gz)
4   level 0 / Sat Feb 15 00:52:01 2003 from newfabiola (root.0.20030215.dump.gz)
5   level 0 /boot Sat Feb 15 00:54:49 2003 from newfabiola (boot.0.20030215.dump.gz)
6   level 0 /mnt/backup Sat Feb 15 00:54:51 2003 from newfabiola (mnt-backup.0.20030215.dump.gz)
7   level 0 / Sat Feb 15 03:00:01 2003 from newfabiola (root.0.20030215.dump.gz)
8   level 0 /boot Sat Feb 15 03:02:47 2003 from newfabiola (boot.0.20030215.dump.gz)
9   level 0 /mnt/backup Sat Feb 15 03:02:48 2003 from newfabiola (mnt-backup.0.20030215.dump.gz)
10  level 0 / Tue Feb 25 03:00:01 2003 from newfabiola (root.0.20030225.dump.gz)
11  level 0 /boot Tue Feb 25 03:03:08 2003 from newfabiola (boot.0.20030225.dump.gz)
12  level 0 /mnt/backup Tue Feb 25 03:03:09 2003 from newfabiola (mnt-backup.0.20030225.dump.gz)

Cyrus Bharda

Re: flexbackup to disk on server is backing up backup files
« Reply #1 on: February 27, 2003, 02:58:49 AM »
2 meg dont you mean 2 GB limit? and this issue was dissucussed in this thread:

http://forums.contribs.org/index.php?topic=6761.msg24312#msg24312

You need to change what flexbackup is backingup so it does not included the backup mount, but that is a bit over my head, have you tryed searching the forums?

Cyrus Bharda

Pascal Van Hecke

Re: flexbackup to disk on server is backing up backup files
« Reply #2 on: February 27, 2003, 12:04:38 PM »
Yes, sorry, I meant  2gig instead of 2 meg.
I was simply explaining that the flexbackup is taking a backup of /mnt/backup itself, so the resulting file is doubled in sieze every time till the 2 gig limit is reached.
I simply followed the instructions in http://mirror.contribs.org/smeserver/contribs/dmay/mitel/howto/flexbackup-to-disk-howto.html, and I do not understand why I get this result.  If I check /mnt/backup on the server, it is not mounted automatically, the third disk is only mounted by the crontab process.  How can I exclude the third disk from the backup?

pascal van hecke

Kelvin

Re: flexbackup to disk on server is backing up backup files
« Reply #3 on: February 27, 2003, 12:43:02 PM »
The flexbackup command issued is

flexbackup -fs all

which I take it to mean backup all mounted filesystems defined in flexbackup.conf.

The filesystems listed in flexbackup.conf are / and /boot.

Therefore if you are mounting something under /, then it gets backed up too. Which I take it to mean that if you mounted a CD-ROM and left it mounted when backup starts, then it probably gets backed up too ?!??

Kelvin

Cyrus Bharda

Re: flexbackup to disk on server is backing up backup files
« Reply #4 on: February 28, 2003, 12:58:53 AM »
You will probably get an answer from the flexbackup list:

flexbackup-help@lists.sourceforge.net

but you'll have to join the list if you want to see the repsonce, which usually happens several minutes after you post, he's relly good like that :-)

Cyrus Bharda