(old)Puppy Linux Discussion Forum

For me, living out in the bundu, momentary power interruptions causing loss of RAM contents are a great vexation (BTW my UPS cuts in too slowly to overcome this).

I've taken to running in multisession (i.e. no pupsave), and also keeping a manual backup on HD of selected important files, like bookmarks. Trouble is, one does not wish to shutdown multisession too often and fill up the disk ..... and Sod's Law generally ensures that the next power blip happens just before I was about to do one or the other saving process.

Although this thread started specifically about frugals=pupsaves, I can't help thinking that a means of keeping a backup (other than pupsave?) on HD would be very useful, and would not need to be 'hot=continuous' if the user could, say, hit a button now and then or request periodic automatic backups. I can't however see how this could be made to play nicely in PUPMODE=77, multisession, which has that great advantage of insurance value against the HD self-destruct event ... but it sure would be nice if it could.

Something STRANGE!

1. I just now restored a hot backup of Lupu-528.002 that was an update of Lupu-526.

2. When I then booted using the Lupu-528 live CD...
It reported that the lupusave file had previously been a 526 lupusave, and did I want to update it.
I hit enter, it updated, and all is as I'd expect after this update.

3. So how come?
I definitely made of hot backup of a lupusave that had already been updated from version 526 to 528.

Hi Sylvander,

(a) I have not tried this "hot" backup program, but I have the impression, perhaps wrongly, that a backup would need to be renamed (and possibly moved) before use.

(b) It seems that you frequently choose not to save; so is your "strange" event possibly a combination of not saving since 10th November and (a) above?

Your use of "nosave" options is probably somewhat unusual - so that may make it harder for others to comment.

My regards

1. "a backup would need to be renamed (and possibly moved) before use"
Agreed.
(a) I save the backup on a USB2 connected external HDD.
(b) The pupsave+SFS filepair are held on my 2nd internal HDD.
(c) To restore, I boot to a 2nd Puppy that doesn't use the pupsave to be replaced by the backup.
(d) Then I use Xfe to display [side-by-side in its twin file panes]...
The pupsave to be deleted [and I delete that]...
And...
The pupsave which is to replace it...
(I copy that into place, and rename it by removing the date & time extension, so as to leave the name as lupusave.3fs)

2. "is your "strange" event possibly a combination of not saving since 10th November"
(a) Not possible; having updated the lupu-526 version of the pupsave to make it a 528 version..
I MUST have saved as soon as I got to the desktop...
So that the changes to the pupsave would be saved back to the pupsave.
Not just completed in RAM, and then discarded.
Only then would the pupsave be a 528 version.
Don't know for sure if I'm right in thinking that, but I would act upon that belief.
(b) And anyway, there would almost certainly have been good reasons to save the session since then.

3. "Your use of "nosave" options is probably somewhat unusual - so that may make it harder for others to comment"
I think in practice, the difference is that there would be no instant auto-saves every time the smallest change is made...
But there would indeed be saves...
Done manually now and then during the session.
I normally fetch my emails using smm...
View each notification in turn, of posts at the Puppy-forums...
Copy the numbers into the address, and view each post.
Then I would probably save that latest arrangement of Firefox windows....
With that sequence of viewed posts following one-after-the-other in a single window, that could be viewed by using the back/forward arrows.
Hence, I probably save at least once in a session.
Depends whether they're important or interesting posts.
I'll save this.

Hi Sylvander,

Doubtless you are sure that your restore was not of a pre-528-update backup - so I have no other thoughts about your interesting puzzle, but at least all appears to be normal again.

My regards

Yet another twist!

The speaker icon disappeared yet again...

So I restored the backup pupsave yet again...

And all appears well yet again...

I'll keep a close watch on the speaker icon to see if I can notice what it is that makes it disappear.

Sylvander et al,

PHB is a simple utility. It does not do anything tricky when performing a backup. It is just a straight copy (cp) of the save file, followed by a sync and e2fsck. That’s all. If the data exists on disk in the active save file then it exists in the backup.

Any idea why the Lupu-528.002 disk would see the [backup and restored copy of the] lupusave as a 526 version, and update it...
When the original from which the backup copy was made was not treated so?

Puzzles me.

Nope, not a clue, unless that info was either stored outside the save file or covered up by a whiteout file ( I think that's what they're called ). Did your restored backup have a different name? Just curious.

No, the name of the restored lupusave was identical to the original.
Both lupusave.3fs...
Both 1GB in size.
As you'd expect.

See this post by rerwin offering a patch PET file that applies some fixes to Lupu-528.002.

And this subsequent post by me reporting HOW I got it to work by restoring a Pupsave Hot Backup, then applying his PET.

I've been using Pupsave Hot Backup on my Lupu 5.1 and it's performed excellently. It allows backing up a pupsave while in use, and I've never gotten a corrupted pupsave with it. I used to get corruptions often when trying to just copy the pupsave while it's in use.

I noticed, though, that .XLOADED always makes it into my backup somehow. It gets moved to xloadedx as it's supposed to during the backup, but the new pupsave still has .XLOADED in it (causing the warning screen at first boot about X exiting uncleanly).

But I found that if I edited phb_core, adding a "sync" after it moves .XLOADED, it works as it's supposed to. Then .XLOADED doesn't make it into the backup. So this works right for me (starting at line 135):
I'm guessing this forces xloadedx to be saved to disk before the savefile is copied.

PupsaveHotBackup-1.4_20140515 # added gettext # added version # improve GUI
Tested with Puppy Precise 5.7.1
Cordialement,

ASRI éducation wrote

PupsaveHotBackup-1.4_20140515 # added gettext # added version # improve GUI
Tested with Puppy Precise 5.7.1
Cordialement,

Please ASRI check your .desktop file

[Desktop Entry]
Encoding=UTF-8
Name=Pupsave hot backup: backup pupsave file
Name[fr]=Pupsave hot backup : sauvegarder le fichier pupsave
Comment=Pupsave hot backup: backup pupsave file
Comment[fr]=Pupsave hot backup : sauvegarder le fichier pupsave
Icon=mini-diskette.xpm
Exec=pupsaverestore
Terminal=false
Type=Application
Categories=Archiving
GenericName=Pupsave hot backup: backup pupsave file

Exec=pupsaverestore Here i guess is pupsave-hot-backup
cheers.

nilsonmorales wrote:Exec=pupsaverestore Here i guess is pupsave-hot-backup
cheers.

You obviously right.
It is surprising that no user has reported before that error.

I sometimes have short memories, I had completely forgotten the pup_save-hot-backup utility.
I took the opportunity to retest.
This works perfectly with a backup file, but it is not compatible with a backup folder.
It would be necessary to update some of the functions.
But I do not believe to be competent enough for this.
2byte no longer present on the forum since 2013, we should find a new competent developer.

Regards,

Hi folks.

Bumping up an old but useful thread, with many thanks
to forum member r__hugues for remembering

(Suggestion: Browse the thread backwards, if you wish
to get the updates, the corrections and the locales.)

BFN.

Hi guys.

A few notes --

1) Double-checking, I realized the *.desktop file had not been corrected
with nilson morales' correction. So here goes.

Please install ASRI's version of the pet, then squish the original
"Pupsave-hot-backup.desktop" file at /usr/share/applications with
the following:

[Desktop Entry]
Encoding=UTF-8
Name=Pupsave hot backup: backup pupsave file
Name[fr]=Pupsave hot backup : sauvegarder le fichier pupsave
Comment=Pupsave hot backup: backup pupsave file
Comment[fr]=Pupsave hot backup : sauvegarder le fichier pupsave
Icon=mini-diskette.xpm
Exec=pupsave-hot-backup
# pupsaverestore
Terminal=false
Type=Application
Categories=Archiving
GenericName=Pupsave hot backup: backup pupsave file

2) For modern Pups (i.e. Pups since late 2014), this utility does not know
what to do with the /mnt/home symlink.

In the 2nd line (please see screen capture above), i.e. the destination line,
the user has to specify the partition if the entry says "/mnt/home".

E.g. if your /mnt/home is /mnt/sda1, you have to fetch sda1 plus the
proper destination directory in the GTK file list, by clicking on the folder
icon at the right. Similarly, if your /mnt/home is at /mnt/sdb2, you have to
fetch /mnt/sdb2, and so on.

3) This utility copies a live pupsave and adds a time and date stamp to it:
that's all it does. If you need to save space, you have to use zip or PackIt
or your favorite archiver to compress the BCK file it creates, as an
additional step.

4) Finally, as ASRI mentioned above, please keep in mind this utility is for
pupsave files, NOT folders.

BFN.

###########################
# pupsave-back-2-tar ("B2T")
# runs on saveFILES and saveFOLDERS.
###########################

Redacted: 200225

Guys,
... BackUp FileSystem Utility for Puppy Linux.
.
We transferred BackUp-2-Tar Script "B2T"
to
Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Filesystem
with the title
BackUp Script "pupsave-back-2-tar"
at
http://murga-linux.com/puppy/viewtopic. ... 4#1050224.
.
"B2T" our simple, readable, modifiable backup routine
based on the ideas of "Hot Backup" v.1.2 .
PUPSTATE now controls the program !
B2T will backup both saveFOLDER and saveFILE.4fs frugal systems.
...
We have transferred files to
http://murga-linux.com/puppy/viewtopic. ... 24#1050224.
.
.
Comments are welcome.

An excellent extension of this utility would be to back up the saved save file to an online host, eg your google drive, using the drive command or rclone