1 Topic by cedbiella

  • cedbiella
  • Member
  • Offline
  • Registered: 2012-06-14
  • Posts: 65

Topic: Move IredAdmin Pro-Pgsql 1.4.2 to 2.3.1 - Restore DB

My previous topic was closed so i open this.
The previou was :
"Topic: Move IredAdmin Pro-Pgsql 1.4.2 to 2.3.1
==== Required information ====
- iRedMail version (check /etc/iredmail-release): 1.4.2
- Linux/BSD distribution name and version: Ubuntu Server 14.04 LTS
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):  PGSQL
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? Y
- Related log if you're reporting an issue:
====
Hello, i'm plannig to move my production server 1.4.2 to a new machine and i want to install the new version 2.3.1.
I've installed Ubuntu server in a new one machine, but i want to know if it's possible to migrate the PGSQL db and mail from older server to new, without user's password lost.
May you help me?
P.S. Sorry for my english"

I've followed the tutorial but when in tutorial say restore backup i've this error

"[Msg] ERROR:  cannot drop sequence deleted_mailboxes_id_seq because other objects depend on it
DETAIL:  default for table deleted_mailboxes column id depends on sequence deleted_mailboxes_id_seq
HINT:  Use DROP ... CASCADE to drop the dependent objects too."

What's is wrong?

Thanks in advance.

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,770

Re: Move IredAdmin Pro-Pgsql 1.4.2 to 2.3.1 - Restore DB

cedbiella wrote:

"[Msg] ERROR:  cannot drop sequence deleted_mailboxes_id_seq because other objects depend on it
DETAIL:  default for table deleted_mailboxes column id depends on sequence deleted_mailboxes_id_seq
HINT:  Use DROP ... CASCADE to drop the dependent objects too."

What command did you run to get this error?

Also, it's better to migrate SQL database by just exporting required SQL columns since your old and new server are running different iRedMail releases, they have different SQL structure, so a direct export/import is not working.

For MySQL, it's command like this:

insert into admin (username, password, name, language, passwordlastchange, created, modified, expired, active) select username, password, name, language, passwordlastchange, created, modified, expired, active from old_db.admin;

3 Reply by cedbiella

  • cedbiella
  • Member
  • Offline
  • Registered: 2012-06-14
  • Posts: 65

Re: Move IredAdmin Pro-Pgsql 1.4.2 to 2.3.1 - Restore DB

ok, i'll try it, infact after a restore it's not possibile to enter in iredadmin,roundcube,sogo, even if i roll back the entire newly created DB ( i'll make backup before initiate every operation).