• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Problem: No backup/migration of data stored in roundcube

PHornburg

Basic Pleskian
Ubuntu 12.04.4 LTS
Panel version 11.5.30 Update #45

The data stored in roundcube webmail (like contacts and signatures ), located in the database table "roundcubemail", is not transferred when migrating the whole server, customer or the domain that uses it. Also in the backup server, account, domain this data is not included.

I think it´s a real problem if a customer with many mailboxes, who only uses roundcube, needs a backup or wants to migrate to another server. Ok, this data could be exported in rounbcube with a few mouse clicks, but it´s not very comfortable. In my opinion this should be included in the backup and also in the migration process (migration manager).

Best regards
Peter
 
sure. But it should be included in backups. When providing products with Plesk, they also should be included in the backup and migration process. Is there a plan to include it in the next panel version?

What about migration - I didn´t read anything about the point that the roundcube database is not included.
 
We will not include Roundcube or Horde database in backup because vendors does not provide any tools to import/export these settings, and the their database format differs significantly from version to version and we can not constantly rewrite Plesk code to meet these changes.
 
Back
Top