Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove Legacy migrate backup file types #872

Closed
shoulders opened this issue Jul 28, 2024 · 3 comments
Closed

Remove Legacy migrate backup file types #872

shoulders opened this issue Jul 28, 2024 · 3 comments

Comments

@shoulders
Copy link

shoulders commented Jul 28, 2024

SYSTEM INFORMATION
OS type and version Ubuntu Linux 22.04.4
Webmin version 2.111
Usermin version 2.010
Virtualmin version 7.20.2  
Theme version 21.10
Package updates All installed packages are up to date

background

You can import backups from other platforms using the following

Virtualmin --> Add Servers --> Migrate Virtual Server --> Backup file type

image

the issue

the following types of backup file are probably that old they should be removed because not one is using them any more:

  • Ensim - I don't think this is developed anymore, i cant find it's home page
  • Plesk 7 - Is anyone still using this version, Plesk is now version 18
  • Plesk 8 - Is anyone still using this version, Plesk is now version 18
  • LXadmin (beta) - this was renamed to kloxo and that has not been delvoped since 2020

additional

  • should Plesk 9+ backup be renamed Plesk so it has parity with cPanel

links

@jcameron
Copy link
Collaborator

I get that those are obsolete, but on the other hand we don't know what old systems users might still have out there that they want to migrate from. And it's very low overhead for Virtualmin to continue to maintain those options..

@shoulders
Copy link
Author

@jcameron you are right, people are still using old versions of Plesk, how old I cannot say.

I would remove LXadmin (beta) and Ensim. These probably have not been used for years.

If the Plesk imports become unmanageable from your end it will be at that time they should be removed 😄 , but I suspect they are very old.

@jcameron
Copy link
Collaborator

jcameron commented Oct 6, 2024

There's not much maintenance overhead in keeping support for those old migration types..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants