PSCS Wiki

User Tools

Site Tools

Trace: • Sender Policy Framework / SPF • How do I write an email to technical support? • "Error Sending Message After Authentication" in Webmail • Import Users From File • Initial Configuration Tasks • Delete OutQueue messages directly from the database • Database Maintenance • Restore a database backup • SMTPClientBlocks Replacement • How to automatically forward spam to the PSCS spamtrap
how_to:database_maintenance

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
how_to:database_maintenance [2013/09/09 09:16] – [Freeing disk space] paulhow_to:database_maintenance [2018/11/14 10:45] (current) – external edit 127.0.0.1
Line 27: Line 27:
   * Stop the VPOP3 service, //not// the VPOP3DB service   * Stop the VPOP3 service, //not// the VPOP3DB service
   * Go to a command prompt in the VPOP3 directory   * Go to a command prompt in the VPOP3 directory
-  * Backup the database to a file, eg 'database.dmp', using, eg: **pgsql\bin\pg_dump -p 5433 -v -F c -U vpop3 -f database.dmp vpop3** +  * Backup the database to a file, eg 'database.dmp', using, eg: **pgsql\bin\pg_dump -p 5433 -v -F c -U postgres -f database.dmp vpop3** 
-  * Remove the old database using **pgsql\bin\dropdb -U postgres -p 5433** +  * Make sure there were no errors reported during the backup! 
-  * Restore the database backup using, eg: **pgsql\bin\pg_restore -U -v -j 4 postgres -p 5433 -C -d postgres database.dmp**+  * Remove the old database using **pgsql\bin\dropdb -U postgres -p 5433 vpop3** 
 +  * Restore the database backup using, eg: **pgsql\bin\pg_restore -v -j 4 -U postgres -p 5433 -C -d postgres database.dmp**
   * Restart the VPOP3 service   * Restart the VPOP3 service
  
Line 41: Line 42:
 ====Alternative to backup/restore==== ====Alternative to backup/restore====
  
-If you are very short of free disk space, then you can use the 'vacuumdb' program, but this is not recommended except as a last resort. To do this, stop[ VPOP3, then run **vacuumdb -f -U vpop3 -p <portnumber> vpop3**. After you have run this you will need to reindex the database as well - use **reindexdb -U vpop3 -p <portnumber> vpop3**. This "vacuum full" operation will generally take a lot longer than a backup/restore program.+If you are very short of free disk space, then you can use the 'vacuumdb' program, but this is not recommended except as a last resort. To do this, stop VPOP3, then run **[[http://www.postgresql.org/docs/9.1/static/app-vacuumdb.html|vacuumdb]] -f -U vpop3 -p <portnumber> vpop3**. After you have run this you will need to reindex the database as well - use **[[http://www.postgresql.org/docs/9.1/static/app-reindexdb.html|reindexdb]] -U vpop3 -p <portnumber> vpop3**. This "vacuum full" operation will generally take a lot longer than a backup/restore program.
 =====Rebuilding Indexes===== =====Rebuilding Indexes=====
 If you suspect that indexes have become damaged, then you can reindex the database. Again, this requires VPOP3 to be stopped first. If you suspect that indexes have become damaged, then you can reindex the database. Again, this requires VPOP3 to be stopped first.
how_to/database_maintenance.1378718196.txt.gz · Last modified: 2018/11/14 10:44 (external edit)

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki