Thread: Backup strategy
Hi, I am setting up the backup strategy for my database. The database contains around 25 tables containing quite a lot of data that does not change very much (and when it does it is changed by me). And around 20 tables containing data which will be created and updated by the users regularly. I would like to backup the two sets of data separately at different intervals. The first set only when I update it and the second set several times per day. Would it be best to set up a separate schema for the "static" tables? If so what would be the simplest and safest way to transfer these tables into a new schema? Thanks for any help Adam -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
On Tue, 18 Jan 2005 18:23:23 +0000, Adam Witney <awitney@sghms.ac.uk> wrote: > > Hi, > > I am setting up the backup strategy for my database. > > The database contains around 25 tables containing quite a lot of data that > does not change very much (and when it does it is changed by me). And around > 20 tables containing data which will be created and updated by the users > regularly. > > I would like to backup the two sets of data separately at different > intervals. The first set only when I update it and the second set several > times per day. > > Would it be best to set up a separate schema for the "static" tables? If so > what would be the simplest and safest way to transfer these tables into a > new schema? > > Thanks for any help pg_dump allows you to backup individual tables. Once you do that, you could import them into a new database. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ L. Friedman netllama@gmail.com LlamaLand http://netllama.linux-sxs.org
On 18/1/05 8:38 pm, "Lonni J Friedman" <netllama@gmail.com> wrote: > On Tue, 18 Jan 2005 18:23:23 +0000, Adam Witney <awitney@sghms.ac.uk> wrote: >> >> Hi, >> >> I am setting up the backup strategy for my database. >> >> The database contains around 25 tables containing quite a lot of data that >> does not change very much (and when it does it is changed by me). And around >> 20 tables containing data which will be created and updated by the users >> regularly. >> >> I would like to backup the two sets of data separately at different >> intervals. The first set only when I update it and the second set several >> times per day. >> >> Would it be best to set up a separate schema for the "static" tables? If so >> what would be the simplest and safest way to transfer these tables into a >> new schema? >> >> Thanks for any help > > pg_dump allows you to backup individual tables. Once you do that, you > could import them into a new database. Would this take care of sequences and any other associated objects also? -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
On Tue, 18 Jan 2005 22:31:43 +0000, Adam Witney <awitney@sghms.ac.uk> wrote: > On 18/1/05 8:38 pm, "Lonni J Friedman" <netllama@gmail.com> wrote: > > > On Tue, 18 Jan 2005 18:23:23 +0000, Adam Witney <awitney@sghms.ac.uk> wrote: > >> > >> Hi, > >> > >> I am setting up the backup strategy for my database. > >> > >> The database contains around 25 tables containing quite a lot of data that > >> does not change very much (and when it does it is changed by me). And around > >> 20 tables containing data which will be created and updated by the users > >> regularly. > >> > >> I would like to backup the two sets of data separately at different > >> intervals. The first set only when I update it and the second set several > >> times per day. > >> > >> Would it be best to set up a separate schema for the "static" tables? If so > >> what would be the simplest and safest way to transfer these tables into a > >> new schema? > >> > >> Thanks for any help > > > > pg_dump allows you to backup individual tables. Once you do that, you > > could import them into a new database. > > Would this take care of sequences and any other associated objects also? I assume so, however I've honestly never backed up individual tables in a production setting before. Its always been an entire db for me. Unless someone else speaks up, you could prolly verify this on your own on a test box. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ L. Friedman netllama@gmail.com LlamaLand http://netllama.linux-sxs.org