Re: How to switch file systems with least downtime?

CS DBA <cs_dba@xxxxxxxxxxxxxxxxxxx> · Sat, 14 Sep 2013 09:26:31 -0600



    We've done this across servers, maybe
      it would work for you:

      
      1) rsync the entire db to the second file system

      
      2) do another rsync each day until you are ready to swap (of
      course only changed files will be moved)

      
      3) before the swap do another rsync to bring the db as close to
      sync'ed as possible

      
      4) shut down the primary db

      
      5) do a final rsync (should have little to nothing to sync)

      
      6) start the secondary db

      
      7) Validate the new db

      
      On 9/14/13 7:46 AM, Moshe Jacobson wrote:

    
        On Sat, Sep 14, 2013 at 9:40 AM,
          Michael Nolan <htfoot@xxxxxxxxx>
          wrote:

          
            Have
              you considered setting up a synchronously replicated slave
              database on the new file system (using a port other than
              5432), getting it in sync, then shutting both databases
              down (master first), switching the slave over to become
              the master and restarting just that database on port 5432?
          
          
          Not a bad idea, but in this case, a small amount of downtime
          is preferable over going to that level of effort.

          
                  Moshe
                          Jacobson

                        Nead Werx, Inc. | Manager of
                        Systems Engineering
                  2323
                        Cumberland Parkway, Suite 201 | Atlanta, GA
                        30339

                      moshe@xxxxxxxxxxxx | www.neadwerx.com
                  

                  "Quality is not an act, it is a habit." --
                    Aristotle