Skip site navigation (1) Skip section navigation (2)

Re: win32: how to backup (dump does not work)

From: "Joris Dobbelsteen" <Joris(at)familiedobbelsteen(dot)nl>
To: <fkater(at)googlemail(dot)com>
Cc: "Gevik Babakhani" <pgdev(at)xs4all(dot)nl>,<pgsql-general(at)postgresql(dot)org>
Subject: Re: win32: how to backup (dump does not work)
Date: 2008-02-26 23:51:34
Message-ID: E4953B65D9E5054AA6C227B410C56AA9C3BC@exchange1.joris2k.local (view raw, whole thread or download thread mbox)
Lists: pgsql-general
>-----Original Message-----
>From: pgsql-general-owner(at)postgresql(dot)org 
>[mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Gevik 
>Sent: Tuesday, 26 February 2008 22:30
>To: fkater(at)googlemail(dot)com; pgsql-general(at)postgresql(dot)org
>Subject: Re: [GENERAL] win32: how to backup (dump does not work)
>> AFAIK stopping the server, zipping data dir, and restarting 
>the server 
>> creates a zip file which is not easily portable to other 
>computers due 
>> to some ntfs file system permission problems.
>IIRC you have to re-assign owner and change permissions after 
>you copy your data dir to the new server.

I believe something like NTBackup (or any decent windows backup tool)
can properly restore permissions. However, this will only work with
centralized authentication (with NT domain) and NO local computer
accounts used, when moving between servers (for obvious reasons). I
think even WinRAR contains an option to do so, but cannot remember for
sure and I never tried it anyways.

In cause you mean the permissions prevent you from making a backup, this
should be a smaller problem if you are infact a backup operator and use
a windows backup tool (they get more rights when requested).

- Joris

In response to


pgsql-general by date

Next:From: craigpDate: 2008-02-27 00:27:26
Subject: bug in 8.3? foreign key refers to different type
Previous:From: Tom LaneDate: 2008-02-26 23:24:08
Subject: Re: v7.4 pg_dump(all) need to encode from SQL_ASCII to UTF8

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group