ML
    • Register
    • Login
    • Search
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups

    LAMP replication to DR site

    IT Discussion
    mysql lamp disaster recovery linux replication backup and disaster recovery
    4
    16
    3201
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Ambarishrh
      Ambarishrh last edited by

      So in the case of backup, what would be the best option? I still need to get info if they have virtualised servers, if so was thinking about Veeam

      scottalanmiller 1 Reply Last reply Reply Quote 0
      • scottalanmiller
        scottalanmiller @Ambarishrh last edited by

        @Ambarishrh said in LAMP replication to DR site:

        So in the case of backup, what would be the best option? I still need to get info if they have virtualised servers, if so was thinking about Veeam

        No, just use MySQL's own backup. Veeam would product a backup of the whole system. You just one a single file.

        1 Reply Last reply Reply Quote 2
        • scottalanmiller
          scottalanmiller last edited by

          THis is all that you need. Take the backup and SCP it over to the other machine or Rsync it over.

          https://dev.mysql.com/doc/refman/5.7/en/mysqldump.html

          A 1 Reply Last reply Reply Quote 3
          • Ambarishrh
            Ambarishrh last edited by

            Ok, so rsync for the files+mysqldump and rsync that too. So just save the mysqldumps on dr location and when something happens, just restore the last backup and bring the server live?

            travisdh1 scottalanmiller 2 Replies Last reply Reply Quote 1
            • A
              Alex Sage @scottalanmiller last edited by

              @scottalanmiller What about the files?

              travisdh1 1 Reply Last reply Reply Quote 0
              • travisdh1
                travisdh1 @Ambarishrh last edited by

                @Ambarishrh said in LAMP replication to DR site:

                Ok, so rsync for the files+mysqldump and rsync that too. So just save the mysqldumps on dr location and when something happens, just restore the last backup and bring the server live?

                Yep

                1 Reply Last reply Reply Quote 0
                • travisdh1
                  travisdh1 @Alex Sage last edited by

                  @aaronstuder said in LAMP replication to DR site:

                  @scottalanmiller What about the files?

                  That's the "rsync"

                  1 Reply Last reply Reply Quote 2
                  • Ambarishrh
                    Ambarishrh last edited by

                    How about setup MySQL replication to remote site and then enable MySQLdump local backup on the DR site as well with increased frequency than daily ( may be twice a day). This way we have an up to date/latest copy and in case let's say there was a drop table command on master, and primary site failed, I can still switch to secondary, use the latest mysql backup to restore and make it up and running.

                    scottalanmiller 1 Reply Last reply Reply Quote 1
                    • scottalanmiller
                      scottalanmiller @Ambarishrh last edited by

                      @Ambarishrh said in LAMP replication to DR site:

                      Ok, so rsync for the files+mysqldump and rsync that too. So just save the mysqldumps on dr location and when something happens, just restore the last backup and bring the server live?

                      Yes. But do a restore from time to time to test them, of course.

                      1 Reply Last reply Reply Quote 1
                      • scottalanmiller
                        scottalanmiller @Ambarishrh last edited by

                        @Ambarishrh said in LAMP replication to DR site:

                        How about setup MySQL replication to remote site and then enable MySQLdump local backup on the DR site as well with increased frequency than daily ( may be twice a day). This way we have an up to date/latest copy and in case let's say there was a drop table command on master, and primary site failed, I can still switch to secondary, use the latest mysql backup to restore and make it up and running.

                        Yup, that's what I would do. Get HA and DR all in one setup. Have it take backups 24 times a day if you want. The impact is pretty much zero.

                        1 Reply Last reply Reply Quote 4
                        • First post
                          Last post