Whole Disk Backup 2.0 released

[Dan Lawrence]

afio: "//tmp.mondo.11378/tmp.mondo.6726/tmpfs/347.afio.bz2" [offset 46m+896k+0]: No space left on device

Any chance your SMB share is formatted FAT32 and you are trying to write a file larger then 2GB to it?

 

[tracker925]

The install of mondo is great. The restore by mondo really does not work for bare metal restore.
I now use clonezilla for such.

 

[foneman]

I sort of disagree.
I have had 3 brand new machines that I have used the same backup on. Worked like a charm. Of course, the 3 machines are all identical to the original machine that was backed up.

 

[david-au]

Upgraded to

Any chance your SMB share is formatted FAT32 and you are trying to write a file larger then 2GB to it?

Following advice I started looking at mondoarchive as the issue and deinstalled the version installed by the script and compiled mondoarchive v2.2.5-r1883 after changing PPCFG_RAMDISK_SIZE to 2048 in src/common/my-stuff.h

Running mondoarchive on the CLI saw a sucsessful backup completed direct to a NFS share dir

I tried once more with the cron backup script and only the first and last ISO's were written. I am trying it a second time at the moment.

 

[darmock]

what version of the cron script are you using? My guess is a motherboard specific related problem. I know it took me several months to get Mondo working *AT ALL* on centos 5.

Tom

 

[david-au]

what version of the cron script are you using? My guess is a motherboard specific related problem. I know it took me several months to get Mondo working *AT ALL* on centos 5.

Hi Tom...... the stock standard one that installs itself from what I downloaded last week, v2.0. I deleted it all a couple of times as per the instructions at the beginning of this thread, and re-installed.

 

[darmock]

Hi Tom...... the stock standard one that installs itself from what I downloaded last week, v2.0. I deleted it all a couple of times as per the instructions at the beginning of this thread, and re-installed.

Sounds about right. I get a couple of emails a week complaining about free software and how I need to fix it for them right now These people get bent when I tell them to go buy a different motherboard. Then they get more inflamed when I tell them that mondo is someone elses program .. I just write control scripts.

In reality the mondo program seems to be the problem as it is not 100% compatible on all systems. It works flawlessly on all Intel and Supermicro motherboards *I have tested*. Anything else is problematic.

I have also noticed Mondo goes in cycles of it works great then an upgrade comes along and it stops.... I also notice they don't develop on the Centos 5 platform which leads to further problems. Good for you using the development version of mondo I have never been that brave. Once I found a version of mondo that works I do not upgrade to anything newer on my commercial installs.

I also send these guys a few bucks for each install I use just to keep them going. I am always open to other programs that do something similar and can be run from the command line easily but the few I have reviewed just are not up to mondo's features even with it's bugs.

Oh well keep trying

Tom

 

[david-au]

Sounds about right. I get a couple of emails a week complaining about free software and how I need to fix it for them right now

Hi Tom;

Never will be a complaint from moi! Just a request of fellow pbxinaflash users for assistance with any issues as we need to be as much 'self-help' than anything else.

My second run of the disk-backup script, after a fresh reboot, was 100% successful. I have one emergency boot iso and a nice collection of data iso's

Thanks heaps for your assistance and we have both an issue, and a resolution now documented here in the forum! Your efforts are greatly appreciated.

 

[darmock]

Nope wasn't c/a you at all mostly just venting as I had just finished an annoying call from a chap who wanted me to help him install a commercial PIAF system with 400 extensions. Of course help meant me doing the complete install and commercial meant he made money and I had to do it for free. His primary argument was "you wrote it so you should install it" Typical shark like business guy who does not understand what open source is and how it generates revenue. :icon_bs:

Be happy

Tom

 

[The Deacon]

I've run into a head scratcher with Whole Disk backup that I can't quite seem to figure out.

I installed the WDB to create an .ISO that I can restore to a VM machine.

So, I ran it from the command line and went to work. When I got home, the script was still running (or at least hung).

When I looked at the /var/log/disk-backup.cron.log script, all I saw was this:

=======================================================
disk-backup.cron - Finished Log 200807201122
=======================================================
=======================================================
disk-backup.cron - Begin Log 200807201449
Released on Date 042608 Version 2.2.1
=======================================================
=======================================================
Now starting mondo. This will be a very long log!
Creating DVD sized ISO images has been choosen


When I tailed the /var/log/mondoarchive.log I saw this:

Done.
Done.
[Main] libmondo-archive.c->backup_data#655: Creation of archives... complete.
Writing boot+data floppy images to disk
No Imgs
No regular Boot+data floppies were created due of space constraints. However, you can burn /var/cache/mindi/mondorescue.iso to a CD and boot from that.

So, I'm confused as to how the drive can be out of space, when it has 28GB free...

 

[darmock]

vmware can be problematic at times i am afraid. so how big is your vmware harddrive set to? As i recollect vmware calculates free disk space slightly different. i seem to remember something on the mondo dev list about it. i would suggest you check on the mondo site as this is problem with mondo and not the control script

tom

 

[The Deacon]

Tom:

Will check out the VMware site, because I'm sure I'll have a problem or two there, but the part I'm struggling with is when I run the script on my real pbx and the script doesn't seem to finish. Even after 10 hours... The real server is the one complaining about not having enough room...

I eventually end up hitting Ctrl-C to abort it...

-Rick

 

[darmock]

Ah Sorry I thought you were referring to the vmware image. I would request at this time you try to do a backup "by hand" to see if there is a problem with mondo. Use the following directions

http://pbxinaflash.org/docs/manualdiskbackup.pdf

If that does not work then there is a problem with mondo and you might want to try updating to the latest version from the repo.

Also if the manual one fails there is a place to upload the mondo log on their website for help. I just checked my logs on a number of my commercial systems and the logs are backing up just fine at the moment even on my own pbx running PIAF 1.3 on an intel atom under centos 5.2

Tom

 

[euser4life]

I noticed something similar

Whenever I try to run the Daily Disk Backup manually to test via:

./disk-backup.cron

I see similar messages as Deacon. I'm using a USB flash drive. I do see the .iso files in the /backup directory, many hours later the commandline still has not return and the files have not been written to the usb thumbdrive. (Also I made sure that the usb flash drive was unmounted before beginning)

The wierd part is that when the whole disk backup runs automagically (This morning between 4 - 4:30 am) the backup ran fine and also mounted the usb flash drive, copied the files from /backup, and deleted them from /backup once they were written to /mnt/usbmondo. Then it unmounted it.

 

[The Deacon]

Tom:

I can get the mondo backup to run manually, but when I try to run the disk-backup script, it continues to hang. Any suggestions?

-Rick

 

[wjms]

Hi Tom,

Just a quick note to say thank you for producing such a good script and great documentation. Installed flawlessly and working fine on both my test box at home and a box I'm putting together for my father-in-law.

Although I did mis-read your instructions on the first box and installed the backup program from source - didn't realise that your script did it for me...

Thanks again.
Jim

 

[didopido]

Error message

I am getting this message when running the script:

install-diskbackup Version 2.2.3 released on Date 080208
CentOS release 5 (Final) - 32 Bit
***************************************************************
*This script will only run on PBX in a Flash! You appear not *
*to be running a valid PBX in a Flash system. Attempts to run *
*this program on a non PBX in a Flash install contravenes the *
*terms of use *
***************************************************************

I have PIAF 1.4 and all other scripts work just fine. Do you have any ideas why I can't run the script?

 

[Saqqara]

problems with orgasmatron install of whole disk backup

(I moved this from the Help section where it was getting no answers, sorry for the double post)

I hope someone can give me some advice.

When I run disk-backup.cron it comes back after only a minute or two. No mondo logfiles are created, but I get a short 331 line disk-backup.log. Early in the log it states

"mondoarchive: invalid option -- F
Initializing...
See /var/log/mondoarchive.log for details of backup run.
Checking sanity of your Linux distribution
Done.
Errors were detected in the command line you supplied.
Please review the log file - /var/log/mondoarchive.log
Execution run ended; result=1"


It doesn't create any ISO's. Later when it goes to move them to the USB, they aren't there.

I have tried running mondo archive manually. I couldn't get it to back up to USB but it did back up to files to disk, which is further than the script takes me.


Background:

I have the exact hardware specified in the Orgasmatron build: GPC2, Kingston 4gb usb, and the 1gb ram upgrade. I do NOT have the second drive installed for a RAID yet.

A few days ago I did the installation, then update-scripts, update-fixes, update-source, update-scripts, update-fixes. I had the missing pear db problem, which I fixed after viewing a forum thread.

My USB flash drive is formatted per the instructions. It's at sdb. The configuration file reflects this.

I've read Tom's advice to someone with a different problem to update Mondo from the repository. I don't know exactly how to do that, if that advice applies here.


Thanks
Greg


Status Version 1.2.5 released on Date 072508
pbx.dyndns.org on 192.168.0.15
********************************************************************
* PBX in a Flash Version 1.2 Daemon Status *
* Running Asterisk 1.4 *
********************************************************************
* Asterisk * ONLINE * Zaptel * ONLINE * MySQL * ONLINE *
* SSH * ONLINE * Apache * ONLINE * Iptables * ONLINE *
* Fail2ban * ONLINE * Ethernet0 * ONLINE * IP Connect * ONLINE *
* BlueTooth * ONLINE * Hidd * ONLINE * NTPD * ONLINE *
* Sendmail * ONLINE * Samba * ONLINE * Webmin * ONLINE *
********************************************************************
* Running Asterisk Version : LOADING
* Asterisk Source Version : 1.4.21.2
* Zaptel Source Version : 1.4.11
* Libpri Source Version : 1.4.7
* Addons Source Version : 1.4.7
********************************************************************
CentOS release 5.2 (Final) - 32 Bit ** Kernel: 2.6.18-92.1.10.el5

 

[darmock]

You seem to be running the old version of the backup program. The -F command line was redacted and no longer exists in the current version of the backup program. Version 2.2.3 released on 080208.

I would try to reinstall the latest version of the install-diskbackup. If this doesn't work I am afraid there is more wrong than meets the eye.

Unfortunately I am still out of town so unable to assist you. Running the 1.2 and 1.3 piaf installs and then running the install-diskbackup program does not show the problems you are experiencing. Mondo quite successfully runs under the controller program and produces iso's and copies them from a vmware vm to an attached 8gb usb key. I took the time over lunch to actually do the installs onto new VM's for both 32 and 64 bit on PIAF 1.2 and 1.3 and all of them created the ISO's correctly.

If it still does not work for you then you will need to run the mondoarchive by hand and generate your backups that way. Sometimes mondo just will not work on a particular piece of hardware and that is that.

When I return from out of town I will be finishing up Version 3.0 of the whole disk backup program and am hopeful to release it before 2010 8^) No there is no ETA so don't ask.

Rerunning the install-diskbackup should refresh the versions of mondo. If it doesn't then I have no other advice to offer sorry.


Tom

 

[wardmundy]

Just to be clear... Tom's Full Disk Backup software works perfectly on the WalMart Special running the Orgasmatron build. We use it every night on several machines.

If it's not working for you with the Orgasmatron build, then you didn't load it into an Everex gPC2.