BackupSuite

[fushkrujs]

After the next build of the Pli-images there will be a new BackupSuite (version 6.1. beta) available in the feed.
This new BackupSuite will make back-ups following the new rules if you installed the bootloaders from > 23-09-2011
So the folders will be named according to the series where the box belongs to
The et9000, et9100 and et9500 will be back upped to et9x00
The et6000 to et6x00
The et5000 and the et5500 to et5x00 etc.

For the time being the back-up will be also made following the "normal/old" way, so in the folders according to the model.

So to summarize: The back-up will be placed in 2 places, in one folder following the range numbering of the receiver, e.g. et9x00, and the other place is in the folder according the modelnumber.

If you want to try the BackupSuite already just replace the file /usr/bin/build-combi.sh with the attached one

[fushkrujs]

I noticed there are some questions about the structure of the back-up proces, I shall try to explain a little. Where I speak about an et9000 you can also read of course an et9100, et9500, et5000 etc.

In this example we make a full backup on HDD (The option Full back-up on HDD/USB), also there is an USB-stick present in the receiver containing a FILE with the name backupstick or backupstick.txt or whatever file containing the word backupstick! Even when the USB-stick contains a file with the name: "this_is_my_backupstick_so_keep_your_han ds_off" is a valid USB-stick.

When you start the plugin "Full back-up on HDD/USB" you'll have to be patient, it will take about 5-7 minutes to complete.
What happens is:

• There are taken some tests to see if you're using this plugin on a supported receiver (of course it is, otherwise it wouldn't install)
• Tested is if your machine uses the jffs2 filesystem or ubifs
• Tested is if all "building blocks" are present, so the files which are used to build the image, like mkfs.ubifs, mkfs.jffs2, ubinize etc.
• There is made a temporary folder to work with
• All the necessary files are collected and assembled to form the image (takes a little while)
• The image is assembled in the right form and placed in the folder et9000
• A copy of the images is copied to the folder with the name: fullbackup-et9000, the folder gets the name of the date-time when the back-up is started, so if the backup is started on 29-09-2011 on 17.15 hrs the name is: 20110929-1715. In this folder is the folder et9000
• When a valid USB-stick was found at the end of the back-up process then also a copy will be placed in the folder et9000 on the stick, so ready to use to restore the image.

I tried to make a little scheme for the process


At the moment we are in a period of transition to a new approach to build the images for the et receivers. Therefore at the moment the back-ups are build to be on 2 ways, this is to be compatible with the old and the new bootloaders, it takes some extra space but it is for a short period of time, naturally the user can delete the unnecessary back-up folders if wanted.

In the near future there will be no separate images for et9000, et9100, et9200, et9500, et5000 etc.
The new nomenclature will be et9x00 for the 9000 series, et5x00 for the 5000 series etc., so 1 image for every serie receivers

So all the back-ups will be build in the old fashioned way as following the new method.

Also the partitionstructure will be changed, making it necessary to build a new BackupSuite, therefore in the coming days the BackupSuite will undergo some changes, not visible for the user, the BackupSuite will function as usual.

Also the new structure requires a new flash, when it will be necessary to flash I assume there will be some announcements made on this site or on open-pli.org.

The plugin Full back-up to USB works similar with the same folders and files.

I hope this explanation gives some insight in the back-up procedure.

And last but not least: To restore the image you'll have to place the folder et9000 (or et9x00) on the USB-stick and flash the receiver like a new image.
If you made the back-up directly on the USB-stick, or on HDD with the stick inserted in the receiver, then this stick is ready yo use.

[fushkrujs]

In the feed today are new versions of the backupsuite, however these contains errors.

The corrected version are in this message.

[fushkrujs]

BackupSuite 6.7


Here is a new version of the backup suite based on a new concept. The code had to be cleaned up, because it was hard to let it run cleanly.
Some things you should know:
- First remove the old version that can be done as follows:
Menu -> Remove red button Plugins - -> Extensions> system plugins -> backup suite <language>

If this does not work, you can try it with telnet
opkg remove "eni gma2-plugin-system-backup suite *" - force-removal-of-dependent-packages
or
opkg remove "eni gma2-plugin-system-backup suite *" - autoremove

You should look on the box if the folders are gone, they are usually in
/ usr / lib / eni gma2/python/Plugins/SystemPlugins/Combi-HDD-Backup /
and
/ usr / lib / eni gma2/python/Plugins/SystemPlugins/Combi-USB-Backup /
These two folders should now be gone.

Restart after uninstalling the box please once again with "Restart eni gma2"

Then install the new version. The new folder for the backup suite can be generated in
/ usr / lib / eni gma2/python/Plugins/Extensions/BackupSuite-HDD /
and
/ usr / lib / eni gma2/python/Plugins/Extensions/BackupSuite-USB /

There are now only one package called backup suite (eni gma2-plugins-extensions-backupsuite_ <version>, currently V6.7), there are no more different languages​​.
Please feel free you to test this new version, I'm open to suggestions and changes to the German translation.

A final word: this version needs to install an Internet connection to necessary files such as. mkfs.ubifs reload.

[fushkrujs]

And yet another new version, version 7.0. This time some corrections in the languagefile(s) and an new translation, French! (Thanks Demosat!) It could be that some é è á ü etc leters are still missing because of the first versions a wrong code was used and the special character got lost in translation.

If there are persons who want to add another language feel free, in the folder locale is a .po file with the name Default.po, this file can be used to add a language. The file can be edited by any texteditor or with the program Poedit which can make a translated file (.mo) Poedit can be found at: http://www.poedit.net/download.php

I also forgot to thank Biki3 and Bonsai Baum for their German translations.

The new version is attached at the end of this message.

Here are some screens from the French version

[fushkrujs]

Here you always find the latest version, now it is version 7.4

BackupSuite with the newest version 7.4.
Very minor adjustment.
Now at the end of the process the total duration time is reported (the time it is shorter than it feels on the VU+ Duo it takes only about 2:28)

[fushkrujs]

Just for testing: BackupSuite 7.4a
I added the search-path /media/net to the plugin "Full back-up to USB"

If you add a file with the name backupstick or backupstick.txt to the root of your NAS you could try to make a back-up on your NAS with the plugin "Full back-up to USB"

[Saxon Lassiter]

Backupsuite 14.6

Changed in version 14.6

• Completed all languages, thanks to the translators: DE Biki3, FR Demosat, IT Matrix64, TR SSD, RU Odyssey, SK Dym1, PL Blzr, ES agmuser
• Added a temporary routine to detect if a back-up is made on one of the new machines et8000 or et10000, if so the program aborts because it is still unknown (to me) if there are any changes in the use of the mtd's, so to avoid problems it is better to abort the program. When these machines hits the market the support will be added as soon as possible. Also it isn't clear yet if the maximum size of the back-up, ~128MB, to restore is also the case for these new machines.

Thx to Pedro_Newbie

[Saxon Lassiter]

Backupsuite 16.5

Changed in version 16.5
Adjusted some parameters in the lookuptable.txt (only VU+ models)

Thx Pedro_Newbie