Pbackup 3.1.9-1

[zigbert]

Gekko
Yes you can.
And, it's the only way to chain several ( max 8 ) backups.

Code: Select all

pbackup -q "job1" "job2" 

But remember to test the backup in gui first. I could be some warnings that should have been turned off.

[Gekko]

Alright, I wont be using this for quite some time, but I'll keep it in mind. Does it have a config file in which it stores backup profiles? If so, upload a sample to www.pastebin.ca or somewhere for me to analyze, I could write a command line script to set up pbackup (Please note "could," I have been very busy of late, I even have a Puppy To-Do list on my PDA with about 20 things on it, 3 high priority)

[zigbert]

Does it have a config file in which it stores backup profiles? If so, upload a sample to www.pastebin.ca or somewhere for me to analyze

You already got one on your computer. Each backup job has a config-file, and there is a default one. But, they are not made for reading, they are made for execution. Look at /root/.pbackup/profiles/default.

Sigmund

[Gekko]

I haven't got pbackup installed you see, could you just paste one please?

[zigbert]

This is my file /root/.pbackup/Pbackup_default

Code: Select all

#Pbackup - profile


#[MAIN SETTINGS]
CHKINCREMENTAL=true
CHKFULLBACKUP=false
CHKMIR=false
INCLUDE="/root/my-documents/|"
SAVEMODE=CD
BCKDEV="/dev/hdc"
BCKDATE_FROM=01/01/1970

#[BACKUP]
CHKREC=true
CHKSYMLN=false
CHKMULTISESSION=false
CHKCOMPRESS=false
CHKJOLIET=false
EXCLUDE_BACKUP=""
FIND_NAME="*"
MNTPNT="/mnt/cdrom/"
TMPDIR="/tmp/"

#[SYNC]
CHKMIRSYMLN=false
CHKMIRATTRIBUTES=true
CHKMIRUPDATESYM=false
CHK_WRITEHIST=true
CHKTRASH=true
CHKLEADING_PATH=true
SYNCACTION=1
EXCLUDE_MIRROR=""
TRASHDIR="/tmp/pbackupTRASH/"

#[JOBS]
LASTSUCCESS=---
LASTRUNTXT="11.Jun 18:13"
LASTSTATUS="Error"
SCHEDULE="---"

#[MISC]
CHKAUTOMOUNT=false
WARN_FS=true
WARN_LEADPATH=true
WARN_MOUNT=true

[PaulBx1]

Did I misunderstand? Do you have other files in dev_save directory that you want to save. Are these ordinary files which changes fileattributes, or are they sfs filesystems or similar. If so, they should be included in the full backup.

I have ordinary files in subdirectories of dev_save that I am changing, AND I have the content of my pup_save which is on dev_save that also is changing.

If I understand you correctly, I must have two jobs. One, to back up the pup_save by itself, the other to back up the other files on dev_save that are changing. Each of those will be a one-button backup. Is that the plan?

In other words, what I really have is a two-button backup.

[zigbert]

PaulBx1
I'm afraid thats the truth. BUT, you can chain several jobs in one operation. This is not possible in GUI (yet), but with command pbackup -q "job1" "job2".

Well, well. One button here, one button there...

Sigmund

[zigbert]

New stable release. See main post.

[zigbert]

Bugfix release.
Download from main post.

Bugfix: choosing HD-path for backup target.

[zigbert]

Bugfix release.
Download from main post.

Minor bugfixes.

[PaulBx1]

Sigmund, have you given up on the changelog (2nd post in this thread)? Last one done was 2.4.0. I usually like looking at those to see if I need to upgrade or not.

Also, I don't know if you mentioned it earlier (the thread is getting pretty long) but for upgrades, do we just write over the previous version, or should we remove the earlier version first?

[zigbert]

PaulBx1
I'll update the changelog

Update: Just install the new pet package. The only thing you'll loose is the job called 'default'. It will be overwritten by a fresh one.

When 2.50 arrive, you'll be able to combine jobs. Let's try to keep it a 'one-button-backup'

Sigmund[/b]

[zigbert]

Version 2.4.4 is uploaded. See main post.

[zigbert]

Version 2.5.0 is uploaded. See main post.

[veronicathecow]

Hi Zigbert, gone but not totally forgotten, missing puppy speed and tools like yours!
Will be trying 2.17 beta soon. PC linux works very well but is slooooow compared to Puppy.
Probably will boot to puppy for most and then PClinux for what Puppy can't
Thanks for all the hard work
Tony

[zigbert]

Hi Tony

Nice to see you around. I have now got myself a FTP-account. (thanks to your request). It is a very powerful backup solution, because the backup stays on another physical place. I only got 30 mb on my free account, but I have made a Pbackup-job for the most critical datas.

Sigmund

[GeoffS]

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:-

#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

Running pbackup from a console I get the following:-
every copy produces

cp: when preserving paths, the destination must be a directory

then the usual couple of comments about 'locale'
then after I click on 'finished' I get

/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#

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.
I hope there is enough information
Cheers
Geoff
Running Puppy 2.16.1.

[zigbert]

GeoffS

Very helpful to see your config-file.

Thanks for bugreport. I've looked at the code, and there has been changes in the backup-to-HD-engine. I'll make an update and post it as soon as it is ready.

I'.ll also take a look at the auto-UN-mounting.

Sigmund

[zigbert]

Version 2.5.1 is ready for downloading. See main post.

[GeoffS]

Hi zigbert
If 2.5.1 is a fix for my problem (you don't say) - wow, that is service . Two hours turnaround. Thank you very much for the quick reply and when I'm working on the correct computer later today I'll give it a try.
Thanks again
Geoff