Facebook
TwitterI used to be a happy owner of the Plesk Power Pack upgrade which includes PostgreSQL management. But I am no longer happy, as today I have realized that the PostgreSQL Databases are _NOT_ backed up via the standard backup manager. This is a real bummer. Is there any way to get this fixes sometimes soon?
-
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.
PostgreSQL Backups
- Thread starter clops
- Start date
abdi
Platinum Pleskian
I once lost so much client data that was in PostgreSQL database, you see the server had issues and since I had a full backup of the server, I just formated it and restored the backup ...
ONLY to realize the PostgreSQL folder was EMPTY!! There were no dump files as was with MySQL ..
...DO NOT TRUST PLESK PostgreSQL BACKUP PROCEDURES ...
You can easily backup PostgreSQL dbs with a single command such as pg_dumpall | gzip -c > all.dbs.out.gz . You would rather have that cron-ed once in a while just incase history repeats it self ..
ONLY to realize the PostgreSQL folder was EMPTY!! There were no dump files as was with MySQL ..
...DO NOT TRUST PLESK PostgreSQL BACKUP PROCEDURES ...
You can easily backup PostgreSQL dbs with a single command such as pg_dumpall | gzip -c > all.dbs.out.gz . You would rather have that cron-ed once in a while just incase history repeats it self ..
