If the controller is installed on a different machine,
the postgresql backuper wont work because it needs the
postgres binaries (i.e., pg_dump). This means an
*identical* version of postgres needs to be installed
(the reason why the versions needs to be the same is
because the pg_dump will complain about it unless a -i
parameter is passed onto it).
Here is the log (from full_cluster.log)
2007-09-26 19:49:26,093 INFO
backup.backupers.NativeCommandExec Starting execution
of "pg_dump -h 192.168.5.141 -p 5432 -U postgres -f
test1.dump/pgtest1dump.sql sq"
2007-09-26 19:49:26,120 INFO
backup.backupers.NativeCommandExec Command "pg_dump -h
192.168.5.141 -p 5432 -U postgres -f
test1.dump/pgtest1dump.sql sq" logged 2 errors and
terminated with exitcode 1
2007-09-26 19:49:26,121 INFO
backup.backupers.AbstractPostgreSQLBackuper pg_dump:
server version: 8.2.4; pg_dump version: 8.2.3
2007-09-26 19:49:26,121 INFO
backup.backupers.AbstractPostgreSQLBackuper pg_dump:
aborting because of version mismatch (Use the -i
option to proceed anyway.)
2007-09-26 19:49:26,125 ERROR
backup.backupers.PostgreSQLPlainTextBackuper Error
while performing backup
org.continuent.sequoia.common.exceptions.BackupException:
pg_dump execution did not complete successfully!
In summary the following should be an ideal design:
The backuper should use the binary on the database
server. This also simplifies the installation
(install postgres on the db node only), as well as
eliminates the version problem.
If that is not possible, at least allowing to pass
extra parameters to the backuper would be a temporary
solution.
Christopher Gorge A. Marges
[EMAIL PROTECTED](recommended)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
____________________________________________________________________________________
Check out the hottest 2008 models today at Yahoo! Autos.
http://autos.yahoo.com/new_cars.html
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
