Hi Stefano! I have not run this particular scenario on Windows, but on Linux you normally have to set up a .pgpass file to allow login without a password. Otherwise the controller gets a password prompt from pg_dump and hangs.
I assume this is possible to set up in Windows as well. Cheers, Robert On 1/14/08 6:50 AM, "Stefano Nichele" <[EMAIL PROTECTED]> wrote: > Hi Emmanuel, > small step done... > Now the backuper seems stuck. In the controller console I have: > > 15:42:55,906 INFO controller.RequestManager.test Starting backup of > backend localhost > 15:42:55,921 DEBUG backup.backupers.PostgreSQLBinaryBackuper Backing up > database 'test_seq1' on host 'localhost:5432' > 15:42:55,937 INFO backup.backupers.NativeCommandExec Starting execution > of "pg_dump -h localhost -p 5432 -U test --format=c -f > .\init_test_dump2 test_seq1" > 15:42:55,937 DEBUG backup.backupers.NativeCommandOutputThread Starting > NativeCommandOutputThread: Thread-3 > 15:42:55,937 DEBUG backup.backupers.NativeCommandOutputThread Starting > NativeCommandOutputThread: Thread-4 > > and in the window where I'm running the console.bat file I have: > > G:\Sequoia\sequoia-2.10.9-bin>bin\console.bat > Launching the Sequoia controller console > Initializing Controller module... > Initializing VirtualDatabase Administration module... > Initializing SQL Console module... > Sequoia driver (Sequoia core v2.10.9) successfully loaded. > localhost:1090 > admin test > Virtual database Administrator Login > test > Virtual database Administrator Password > > Ready to administrate virtual database test > test(test) > backup localhost init_test_dump2 pgdump . > Backend login for backup process > test > Backend password for backup process > > Backup backend localhost in dump file init_test_dump2 > No last known checkpoint for backend localhost > test(test) > initialize localhost force > Virtual Database test has been successfully initialized from backend > localhost > test(test) > backup localhost init_test_dump2 pgdump . > Backend login for backup process > test > Backend password for backup process > > Backup backend localhost in dump file init_test_dump2 > > and no other output. > > In the virtualdatabase file definition I added: > > <Backuper backuperName="pgdump" > > className="org.continuent.sequoia.controller.backup.backupers.PostgreSQLBinary > Backuper"/> > > Note that running manually: > pg_dump -h localhost -p 5432 -U test --format=c -f .\init_test_dump2 > test_seq1 > a prompt for the password is shown and after that, the dump is performed. > Maybe the backuper is waiting for the password ? > > Thanks again > ste > > Emmanuel Cecchet wrote: >> Hi Stefano, >> >> You should use the PostgreSQL backuper instead of Octopus. >> The PostgreSQL backuper relies on pg_dump to perform the dumps and >> should be able to dump/restore your entire database. >> >> Hope this helps, >> Emmanuel >>> I'm trying sequoia and I found an issue with tables with binary data >>> on postgresql. >>> >>> My db is: >>> >>> CREATE TABLE photo >>> ( >>> id bigint NOT NULL, >>> photo bytea, >>> CONSTRAINT photo_pkey PRIMARY KEY (id) >>> ); >>> >>> CREATE TABLE test >>> ( >>> id bigint NOT NULL, >>> name character varying(255), >>> CONSTRAINT test_pkey PRIMARY KEY (id) >>> ); >>> >>> (it is not my real db but I wanted isolate the issue). >>> I'm able to backup the db from a backend, but restoring it on another >>> backend, just the table "test" is created. I'm using postgres and in >>> attachment the full_cluster log. >>> Sequoia console contains the output on the console. >>> init_test_dump contains the backup (it's just 10kb since there are >>> not data). >>> >>> Any suggestion ? Is it a issue with binary data ? My real db has 33 >>> tables and just the one with binary data is missing. >> >> > -- Robert Hodges, CTO, Continuent, Inc. Email: [EMAIL PROTECTED] Mobile: +1-510-501-3728 Skype: hodgesrm _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
