DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:user-agent:mime-version:to:cc:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	b=CZxSXky7QpcD4ejVHSD3HUIBm71OVUdIq/kpF/R5S8yr26Lj8Xu1lHIJsFm8Pf+6Ov
	7ZPYTmI7xNrO2M367nu+/12G8wmjLbEDoBBsVRcLEotGr5gUddpJlKvSbiSlOznYIUb2
	R9vwQ2ow9+pn9O8z8LgmQdvBf9IwWry6mmWOc=
Message-ID: <4CA5C0F7.8040407@gmail.com>
Date: Fri, 01 Oct 2010 13:07:35 +0200
From: Michal Glowacki <mg.scandic@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; pl;
	rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: Guillaume Lelarge <guillaume@lelarge.info>
CC: Fujii Masao <masao.fujii@gmail.com>, pgsql-admin@postgresql.org
Subject: Re: Hot standby server does not start
References: <4CA2F025.3010508@gmail.com>
	<AANLkTim8eZ3nMPN3_1Au1pb32Rfv6v2NtifmCu0OCf6u@mail.gmail.com>
	<4CA2F5ED.3000209@gmail.com> <4CA2FF32.6070002@lelarge.info>
In-Reply-To: <4CA2FF32.6070002@lelarge.info>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

  hi,

     it's fine now - the problem was WinRAR which reported that he can't 
access some files and I ignored that - big mistake :)

     Thanks for help - working fine now.

Michal
> Le 29/09/2010 10:16, Michal Glowacki a écrit :
>>   Fujii, I believe I should follow this (from documentation):
>>
>> ************************
>>
>> The procedure for making a base backup is relatively simple:
>>
>>    1.
>>
>>       Ensure that WAL archiving is enabled and working.
>>
>>    2.
>>
>>       Connect to the database as a superuser, and issue the command
>>
>>       SELECT pg_start_backup('label');
>>
>>       where label is any string you want to use to uniquely identify
>>       this backup operation. (One good practice is to use the full path
>>       where you intend to put the backup dump file.) |pg_start_backup|
>>       creates a /backup label/ file, called backup_label, in the cluster
>>       directory with information about your backup.
>>
>>       It does not matter which database within the cluster you connect
>>       to to issue this command. You can ignore the result returned by
>>       the function; but if it reports an error, deal with that before
>>       proceeding.
>>
>>    3.
>>
>>       Perform the backup, using any convenient file-system-backup tool
>>       such as tar or cpio. It is neither necessary nor desirable to stop
>>       normal operation of the database while you do this.
>>
>>    4.
>>
>>       Again connect to the database as a superuser, and issue the command
>>
>>       SELECT pg_stop_backup();
>>
>>       This should return successfully.
>>
>>    5.
>>
>>       Once the WAL segment files used during the backup are archived as
>>       part of normal database activity, you are done.
>>
>>
>> **********************************
>>
>> BUT I have some questions:
>>
>> 1. I connect to database using psql and issue command SELECT
>> pg_start_backup('my_backup'); The result (in less than second) is:
>>
>>   pg_start_backup
>> -----------------
>>   4/DA000020
>> (1 row)
>>
>> Is it correct it goes that fast?
>>
> Yes.
>
>> 2. Now I proceed to step 3 - perform the backup using file system
>> backup. Could you assist me on this one? I should archive what?The
>> '/data' folder (please note I use Windows)? Should I just compress it
>> into rar file and transfer to standby server and overwrite it's '/data'
>> folder?
>>
> Using rar on the data folder should work if you don't have tablespaces.
> If you have some, add them to your data rar archive.
>
> And instead of overwriting the data folder on the slave, wipe out your
> old data folder and recreate it by restoring your rar archive.
>
> BTW, pgAdmin backup and restore facilities use pg_dump/pg_restore. So
> it's not really surprising that you get the same results :)
>
>