Pbackup 3.1.9-1
zigbert
I have a small problem, pbackup has stopped working . I was using version (?) and it all worked OK. I upgraded to 2.4.4 and it stopped working. I upgraded to 2.5.0 and it still won't work.
There is plenty of space on the destination drive.
By not working I mean - it goes through all its routines and appears to work. At the end it displays the backup directory but there are no new files in it. I've searched elsewhere and they have not gone anywhere else .
I suspect this maybe critical - I am backing up to a VFAT partition.
If I make it work (see comments at the end) the Rox file display comes up in 8.3 format.
The history file is never updated.
It makes no difference if the device is mounted or not, however when I manage to make it run (see comments at the end) the partition is always unmounted by pbackup at the finish.
The GUI display tells lies and says it was successful.
The following is my daily backup profile:-
every copy produces
then after I click on 'finished' I get
I hope there is enough information
Cheers
Geoff
Running Puppy 2.16.1.
I have a small problem, pbackup has stopped working . I was using version (?) and it all worked OK. I upgraded to 2.4.4 and it stopped working. I upgraded to 2.5.0 and it still won't work.
There is plenty of space on the destination drive.
By not working I mean - it goes through all its routines and appears to work. At the end it displays the backup directory but there are no new files in it. I've searched elsewhere and they have not gone anywhere else .
I suspect this maybe critical - I am backing up to a VFAT partition.
If I make it work (see comments at the end) the Rox file display comes up in 8.3 format.
The history file is never updated.
It makes no difference if the device is mounted or not, however when I manage to make it run (see comments at the end) the partition is always unmounted by pbackup at the finish.
The GUI display tells lies and says it was successful.
The following is my daily backup profile:-
Running pbackup from a console I get the following:-#Pbackup - profile
#[MAIN SETTINGS]
CHKINCREMENTAL=true
CHKFULLBACKUP=false
CHKMIR=false
INCLUDE="/root/|/mnt/hda5/|/gnucash/|"
SAVEMODE=HD
BCKDEV="/mnt/hdd5/PuppyBackup/"
BCKDATE_FROM=20/07/2007
FTPSERVER=
FTPSERVERDIR=
FTPUSERNAME=
FTPPASSWORD=
#[BACKUP]
CHKREC=true
CHKSYMLN=false
CHKMULTISESSION=false
CHKCOMPRESS=false
CHKJOLIET=false
EXCLUDE_BACKUP=""
FIND_NAME="*"
MNTPNT="/mnt/cdrom/"
#[SYNC]
CHKMIRSYMLN=false
CHKMIRATTRIBUTES=true
CHKMIRUPDATESYM=false
CHK_WRITEHIST=true
CHKTRASH=true
CHKLEADING_PATH=true
SYNCACTION=1
EXCLUDE_MIRROR=""
TRASHDIR="/tmp/pbackupTRASH/"
#[JOBS]
LASTSUCCESS=1184924332
LASTRUNTXT=""
LASTSTATUS=""
SCHEDULE="---"
#[MISC]
CHKAUTOMOUNT=true
WARN_FS=true
WARN_LEADPATH=true
WARN_MOUNT=true
every copy produces
then the usual couple of comments about 'locale'cp: when preserving paths, the destination must be a directory
then after I click on 'finished' I get
One other item that is significant. If I remove the final '/' from the 'BCKDEV' the backup runs. However it creates a directory called 'puppybac' (8 chars?) and does not add the 'to' & 'from' dates to the directory name. At the finish the directory names in the display are in 8.3 format. The partition is unmounted at the finish even if it was mounted at the start./usr/local/pbackup/pbackup: line 905: /root/.pbackup/history/history: Not a directory
/usr/local/pbackup/pbackup: line 908: /root/.pbackup/history/20.Jul 19:23:29: Not a directory
/usr/local/pbackup/pbackup: line 909: /root/.pbackup/history/20.Jul 19:23:29: Not a directory
sh-3.00#
I hope there is enough information
Cheers
Geoff
Running Puppy 2.16.1.
Hi Sigmund
Backup worked and it did not unmount the partition at the finish.
Congrats on your prompt efforts.
Sorry to hear about your dead laptop but that is when backups are VERY nice.
Now I'll have to try it with a drive that is NOT mounted before I do the backup - have to wait until I have something to backup .I know, I was the one who suggested that using an unmounted drive is a good idea but I'm actually not doing it
Thanks again
Geoff
ADDED half an hour later
Sorry, bad news, I hadn't checked the history file - It is still not updated.
Cheers
Geoff
Backup worked and it did not unmount the partition at the finish.
Congrats on your prompt efforts.
Sorry to hear about your dead laptop but that is when backups are VERY nice.
Now I'll have to try it with a drive that is NOT mounted before I do the backup - have to wait until I have something to backup .I know, I was the one who suggested that using an unmounted drive is a good idea but I'm actually not doing it
Thanks again
Geoff
ADDED half an hour later
Sorry, bad news, I hadn't checked the history file - It is still not updated.
Cheers
Geoff
GeoffS
Nice to hear the good part of your story.
I have now tried a backup to vfat, and it writes to history. I need more info.
- What info when running from terminal?
- Are you using the same config-file as shown in earlier post. (is 'write history log' checked)?
- Are the problem with 8.3 names fixed.
- Does the file /root/.pbackup/history/history exist?
- Does it write to history if backup to ext2/3?
Sigmund
Nice to hear the good part of your story.
I have now tried a backup to vfat, and it writes to history. I need more info.
- What info when running from terminal?
- Are you using the same config-file as shown in earlier post. (is 'write history log' checked)?
- Are the problem with 8.3 names fixed.
- Does the file /root/.pbackup/history/history exist?
- Does it write to history if backup to ext2/3?
Sigmund
Hi Sigmund
Don't you sleep or do you just get up early?
I'm back on the laptop so don't have access to pbackup but I can answer some questions.
Cheers
Geoff
(I'm going to bed soon )
Don't you sleep or do you just get up early?
I'm back on the laptop so don't have access to pbackup but I can answer some questions.
I haven't run it from a console so can't answer that - try tomorrow.What info when running from terminal?
Exact same config file.Are you using the same config-file as shown in earlier post. (is 'write history log' checked)?
File view was in 'long name' or vfat format.Are the problem with 8.3 names fixed.
Yes, the history file is in correct spot, exactly where I've always found it. Last update shown is 17th July 2007 prior to my first update of pbackup.Does the file /root/.pbackup/history/history exist?
I have not done a backup to an ext2/3 so can't answer that - will try tomorrow.Does it write to history if backup to ext2/3?
Cheers
Geoff
(I'm going to bed soon )
Hi Sigmund
When I read the following question from you and looked at some console output daylight dawned
**Problem solved ********
I renamed the old history file to history-old
Created a directory 'history'
Moved history-old to new directory
Renamed history-old to history
It all ran OK.
Maybe I missed the version of pbackup which created the history directory. Anyway, the history is now working OK.
Tried the automounting ---
Oh dear I tried it with an unmounted ext2 partition on 1st drive.
It provided the nice error box - 'I can't access the /mnt/hda8/tmp'.
Then I tried it on my normal backup vfat partition hdd5 on my 2nd drive but unmounted.
No messages, it did not mount it but did the backup to /initrd/mnt/hdd5 - ouch!!!
Automounting is NOT working - sorry.
After a bit more experimenting:-
Sometimes hdd5 (a vfat partition) gets mounted as msdos and that's when the filenames appear as 8.3. This doesn't always occur, sometimes as described above, the backup goes to /initrd/---. I can't see what I do that makes this change.
The rest of it appears to be working fine and I have backups again - great.
Cheers
Geoff
When I read the following question from you and looked at some console output daylight dawned
My history file is /root/.pbackup/history i.e. there is no history directory.- Does the file /root/.pbackup/history/history exist?
**Problem solved ********
I renamed the old history file to history-old
Created a directory 'history'
Moved history-old to new directory
Renamed history-old to history
It all ran OK.
Maybe I missed the version of pbackup which created the history directory. Anyway, the history is now working OK.
Tried the automounting ---
Oh dear I tried it with an unmounted ext2 partition on 1st drive.
It provided the nice error box - 'I can't access the /mnt/hda8/tmp'.
Then I tried it on my normal backup vfat partition hdd5 on my 2nd drive but unmounted.
No messages, it did not mount it but did the backup to /initrd/mnt/hdd5 - ouch!!!
Automounting is NOT working - sorry.
After a bit more experimenting:-
Sometimes hdd5 (a vfat partition) gets mounted as msdos and that's when the filenames appear as 8.3. This doesn't always occur, sometimes as described above, the backup goes to /initrd/---. I can't see what I do that makes this change.
The rest of it appears to be working fine and I have backups again - great.
Cheers
Geoff
Hi Sigmund
I've made one test with my 2nd drive - vfat - unmounted, running from the console. Used a smaller but very similar config file. It only backsup the /gnucash/ directory.
I did get the error message about trying to backup to the /initrd/ etc directory when I had NOT told it to automount. That was good.
BUT when I checked the automount option I got this:-
I will try some other tests later today.
Cheers
Geoff
I've made one test with my 2nd drive - vfat - unmounted, running from the console. Used a smaller but very similar config file. It only backsup the /gnucash/ directory.
I did get the error message about trying to backup to the /initrd/ etc directory when I had NOT told it to automount. That was good.
BUT when I checked the automount option I got this:-
It did the backup but had mounted the drive as msdos therefore lost most of the file name in the 8.3 filename format.sh-3.00# pbackup
/usr/local/pbackup/pbackup: line 1328: 9178 Terminated $PROG_PATH/func -logbox
cp: omitting directory `/gnucash/'
(process:9436): Gdk-WARNING **: locale not supported by Xlib
(process:9436): Gdk-WARNING **: cannot set locale modifiers
I will try some other tests later today.
Cheers
Geoff
Sigmund, your screenshot of pbackup 2.5.0 shows a date format like "12.Jul 21:40" in the job list, but "15/07/2007" in the from date. Unfortunately the latter format is ambiguous since Americans (maybe others) use month first, while Europeans use date first. Could we go always with "12 Jul 2007" everywhere, or something like that? In other words, don't use numerals for the month? Of course the backup saveset names also ought to be reworked. I know I have to stare at the saveset names for a while to figure out what dates were actually saved...
What about using this crap in another distro?
There has been some rquests of this lately, and I'm doing some loud thinking here. At this stage this is not much tested. - I'm just too happy with my Puppy. I have ran it in ubuntu and grafpup. First of all you must match the dependecies. Then you are ready for a linux system with roots rights. But most common, you run another distro as user, and you have limited rights. Now it depends on how strickly the users permissions are set. In grafpup it seems ok. In ubuntu user are not allowed to kill a process it has started. This will not close the box that shows progress during backup. User that are not allowed to delete files in /tmp/ which makes Pbackup leave its trashfiles. User maybe doesn't have rights to set a scheduled backup in /var/spool/cron/crontabs/$USER. In some multiuser system user should set this tasks in /etc/crontabs/. At last Pbackup can't start cron by default at boot in a system that need superuser rights to start services at boot.
1-2-3-GO
1. Copy Pbackup directory somewhere in your system. Helpfile(s) goes to /usr/share/doc/pbackup/.
2. Make link /usr/bin/gtkdialog3 to whereever gtkdialog was installed.
3. If user aren't owner of Pbackup files, the progress box won't be deleted after backup. To change owner of files:
Example: chown james -R /usr/local/pbackup
GO. (Scheduling must be set manually.)
Do you strugle to get it work, please share your effort to help your friends.
Requirements:
- bash, busybox (or similar)
- gtkdialog 0.7.15, xdialog
Optional:
- cdrtools (mkisofs, cdrecord) for CD-burning
- dvd+rwtools (growisofs) for DVD-burning
- curl for transferring via FTP
- cron for scheduling
All these are Puppy builtin
Sigmund
There has been some rquests of this lately, and I'm doing some loud thinking here. At this stage this is not much tested. - I'm just too happy with my Puppy. I have ran it in ubuntu and grafpup. First of all you must match the dependecies. Then you are ready for a linux system with roots rights. But most common, you run another distro as user, and you have limited rights. Now it depends on how strickly the users permissions are set. In grafpup it seems ok. In ubuntu user are not allowed to kill a process it has started. This will not close the box that shows progress during backup. User that are not allowed to delete files in /tmp/ which makes Pbackup leave its trashfiles. User maybe doesn't have rights to set a scheduled backup in /var/spool/cron/crontabs/$USER. In some multiuser system user should set this tasks in /etc/crontabs/. At last Pbackup can't start cron by default at boot in a system that need superuser rights to start services at boot.
1-2-3-GO
1. Copy Pbackup directory somewhere in your system. Helpfile(s) goes to /usr/share/doc/pbackup/.
2. Make link /usr/bin/gtkdialog3 to whereever gtkdialog was installed.
3. If user aren't owner of Pbackup files, the progress box won't be deleted after backup. To change owner of files:
Example: chown james -R /usr/local/pbackup
GO. (Scheduling must be set manually.)
Do you strugle to get it work, please share your effort to help your friends.
Requirements:
- bash, busybox (or similar)
- gtkdialog 0.7.15, xdialog
Optional:
- cdrtools (mkisofs, cdrecord) for CD-burning
- dvd+rwtools (growisofs) for DVD-burning
- curl for transferring via FTP
- cron for scheduling
All these are Puppy builtin
Sigmund