[VU+ Ultimo4K] Image Backups

[birdman]

So this is current ImageManager setup ....

OpenVix 7.1.7103F! Current?

 

[Huevos]

OpenVix 7.1.7103F! Current?

Don't worry about that, it is a personal build.

 

[seagen]

It is pretty easy. In ImageManager.py you set the default prefix in row 50
In the current version you have change the
defaultprefix = getImageDistro() + "-" + getMachineName()
To
defaultprefix = getImageDistro()

So when a user is renaming the backup to lets say. my-latest the Machine Name is removed and of cause the Backup image is not showing.
Machine Name is used to identify the correct image for your Machine. So you want restore the wrong image.

If you chage back to
defaultprefix = getImageDistro() + "-" + getMachineName()
All works just fine.

Of cause there are other solutions to identify and add the machine name. But at the moment they really don't work proper
At least not for Vu+

 

[twol]

It is pretty easy. In ImageManager.py you set the default prefix in row 50
In the current version you have change the
defaultprefix = getImageDistro() + "-" + getMachineName()
To
defaultprefix = getImageDistro()

So when a user is renaming the backup to lets say. my-latest the Machine Name is removed and of cause the Backup image is not showing.
Machine Name is used to identify the correct image for your Machine. So you want restore the wrong image.

If you chage back to
defaultprefix = getImageDistro() + "-" + getMachineName()
All works just fine.

Of cause there are other solutions to identify and add the machine name. But at the moment they really don't work proper
At least not for Vu+

So the machinename is no longer in the prefix - so that cannot happen anymore plus why would you not use the menu key to bring up the options and change teh default prefix?….

 

[seagen]

Don't understand your answer ..... If I open menu and add my personal prefix the machine name is also removed. Only Image distro and date.
How will the ImageManager now that my backup image suits my Machine when there is no machine name in tha backup image?
I assume that the machine name is there to prevent me from installing a backup image from the wrong machine?

 

[ccs]

Have you tried creating an image backup to see what name you end up with?

 

[seagen]

Try your self. Press menu add any prefix and see how it works.
In my test the image backup works just fine, But since the machine name is gone it does not of obviouse reason don't show in the list

 

[ccs]

.... I don't have a problem...

-rw-r--r--    1 root     root     121747446 Feb 20 10:44 openvix-vuultimo4k-developer-6.1.000.000-20220220_104121.zip
-rw-r--r--    1 root     root     121751201 Feb 22 18:46 openvix-vuultimo4k-developer-6.1.000.000-20220222_184317.zip
-rw-r--r--    1 root     root     121801209 Feb 22 18:52 [COLOR="#FF0000"]xxx[/COLOR]-vuultimo4k-developer-6.1.000.000-20220222_184909.zip
root@vuultimo4k:/media/hdd/imagebackups#

 

[Huevos]

Try your self. Press menu add any prefix and see how it works.
In my test the image backup works just fine, But since the machine name is gone it does not of obviouse reason don't show in the list

If you have a problem you are not using the current version.

 

[birdman]

.... I don't have a problem...

-rw-r--r--    1 root     root     121747446 Feb 20 10:44 openvix-vuultimo4k-developer-6.1.000.000-20220220_104121.zip
-rw-r--r--    1 root     root     121751201 Feb 22 18:46 openvix-vuultimo4k-developer-6.1.000.000-20220222_184317.zip
-rw-r--r--    1 root     root     121801209 Feb 22 18:52 [COLOR=#FF0000]xxx[/COLOR]-vuultimo4k-developer-6.1.000.000-20220222_184909.zip
root@vuultimo4k:/media/hdd/imagebackups#

Well, you might - as that name doesn't mention Vix at all, so you don't know which distro it refers to.
This was mentioned in the discussion about backup names (see this entry). Perhaps we should be doing the same for image backups as for normal backups?

 

[twol]

Well, you might - as that name doesn't mention Vix at all, so you don't know which distro it refers to.
This was mentioned in the discussion about backup names (see this entry). Perhaps we should be doing the same for image backups as for normal backups?

Well if somebody is removing the openvix prefix then hopefully they know they are doing it for a reason that identifies the backup to them … or why do it

 

[twol]

I think the answer is that we just remove the changeable prefix - then I have no doubt some people will want to argue about that as well

 

[ccs]

Well if somebody is removing the openvix prefix then hopefully they know they are doing it for a reason that identifies the backup to them … or why do it

I've never changed the prefix, can't really see the point, and if did, like you say, I'd make sure I knew what it referred to.

 

[Huevos]

Well, you might - as that name doesn't mention Vix at all, so you don't know which distro it refers to.
This was mentioned in the discussion about backup names (see this entry). Perhaps we should be doing the same for image backups as for normal backups?

If you made the backup with image manager surely it must come from OpenViX.

Anyway the whole point of Image Manager is it can flash images from other distros and even directly download them.

When you start using a multislot box it will all fall into place.

 

[birdman]

Anyway the whole point of Image Manager is it can flash images from other distros and even directly download them.

Good point.
(Meanwhile it's only useful for the BackupManageer to see the Vix ones.)

 

[Ev0]

If you made the backup with image manager surely it must come from OpenViX.

Could be from OpenBh though

 

[abu baniaz]

So, we need a whitelist for Settings Backup Manager backups that Settings Backup Manager can see for restoration as OBH and ViX should be interoperable

Going back to my rejected suggestion from a long time ago about Image Manager, I would like to re-suggest that we are able to sort the images by name as well as by date. I suppose image types too where they are available.

 

[Huevos]

In ten years we have never had a complaint from a user about this.

This is a solution waiting for a problem.

Do we really need to assume our users are complete cretins?