Pbackup 3.1.9-1

Message

zigbert · #161 Post by **zigbert** » Mon 11 Jun 2007, 12:24

PaulBx1
I've made an experiment that maybe will solve your request. It's very easy to permit files (not only directories) in the field 'Save from'. Change the line number 1602 in /usr/local/pbackup/pbackup from:

Code: Select all

	13)	CHOOSEDIR="true"; TITLE="$LOC121"; DIR=/; chooser

to:

Code: Select all

	13)	CHOOSEDIR="false"; TITLE="$LOC121"; DIR=/; chooser

Now you can choose to backup only the file /initrd/mnt/dev_save/pup_save.2fs. (or any other file or dir.)
You have to choose 'Full backup' to pass the date-check.
Note that files in 'Save from' will crash a sync. I have made an errorcheck for the next release.

Are you pleased, or still a helping pain.

Sigmund

PaulBx1 · #162 Post by **PaulBx1** » Mon 11 Jun 2007, 13:24

OK, let me see if I understand. After I make this change, every time I back up I am supposed to run pbackup first, with "backup recent files" and from initrd/mnt/dev_save, then run pbackup again with "full backup" from /initrd/mnt/dev_save/pup_save.2fs?

I am still in pain.

It would be easier to simply run pbackup with "backup recent files", then manually copy the pup_save into the incremental save_set just created. That way the pbackup stage remains a one-button backup.

Maybe I have not understood what you are suggesting.

zigbert · #163 Post by **zigbert** » Mon 11 Jun 2007, 14:16

No no, this is easy. - Only one button.

I have made a predefined job that will follow next release - Puppy_System_Recovery.
After the codehack of line 1602. Do as follow:

Step 1: Choose 'Full Backup'.
Step 2: Include only /initrd/mnt/dev_save/pup_save.2fs in 'Save from'.
Step 3: Save Job (if you want to give it another name than 'Default').
Step 4: Backup.

Next run it is a real "One-Button-Backup".

Sigmund

zigbert · #164 Post by **zigbert** » Mon 11 Jun 2007, 16:03

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.

Sigmund

Gekko · #165 Post by **Gekko** » Tue 12 Jun 2007, 07:10

zigbert wrote:Gekko
The only available commandline option is -q (quiet), which Pbackup uses for scheduled backups.

Sigmund

So you're saying I could set a backup in the GUI, then call the backup to start via the command line?

zigbert · #166 Post by **zigbert** » Tue 12 Jun 2007, 09:25

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 · #167 Post by **Gekko** » Tue 12 Jun 2007, 09:57

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 · #168 Post by **zigbert** » Tue 12 Jun 2007, 10:29

Gekko wrote: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 · #169 Post by **Gekko** » Tue 12 Jun 2007, 10:39

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

zigbert · #170 Post by **zigbert** » Tue 12 Jun 2007, 12:00

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 · #171 Post by **PaulBx1** » Thu 14 Jun 2007, 13:59

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 · #172 Post by **zigbert** » Thu 14 Jun 2007, 14:31

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 · #173 Post by **zigbert** » Sat 30 Jun 2007, 11:29

New stable release. See main post.

zigbert · #174 Post by **zigbert** » Sun 01 Jul 2007, 19:51

Bugfix release.
Download from main post.

Bugfix: choosing HD-path for backup target.

zigbert · #175 Post by **zigbert** » Mon 02 Jul 2007, 19:34

Bugfix release.
Download from main post.

Minor bugfixes.

PaulBx1 · #176 Post by **PaulBx1** » Mon 02 Jul 2007, 21:00

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 · #177 Post by **zigbert** » Tue 03 Jul 2007, 15:03

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 · #178 Post by **zigbert** » Wed 04 Jul 2007, 19:37

Version 2.4.4 is uploaded. See main post.

zigbert · #179 Post by **zigbert** » Sun 15 Jul 2007, 12:36

Version 2.5.0 is uploaded. See main post.

veronicathecow · #180 Post by **veronicathecow** » Tue 17 Jul 2007, 19:07

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

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Pbackup 3.1.9-1