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

    Best Practices

    Scheduled Pinned Locked Moved IT Discussion
    12 Posts 4 Posters 1.4k Views
    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.
    • s.hacklemanS
      s.hackleman
      last edited by

      My problem is we have several critical DB servers gathering data 24/7. I have to be vague, but bear with me. So we have a server and we will call it History1. There are tons of small apps, spreadsheets, web pages all over the company that look at the data on History1. It has a single IP, and is added into Active Directory with the name History1. Now with all this traffic eventually we have to upgrade our old History1. So what is the best practice here?

      1. We make a History2, then track down every item that pointed to History1, and update it to point to History2. However user apps, and spreadsheets become overwhelming.

      2. We make History2, then wile trying to have 0 downtime, rename it to History1, and hope that active directory propagates the name change right.

      I have tried it both ways, and both ways suck. Is there a better way?

      JaredBuschJ 1 Reply Last reply Reply Quote 0
      • JaredBuschJ
        JaredBusch @s.hackleman
        last edited by

        @s.hackleman said in Best Practices:

        My problem is we have several critical DB servers gathering data 24/7. I have to be vague, but bear with me. So we have a server and we will call it History1. There are tons of small apps, spreadsheets, web pages all over the company that look at the data on History1. It has a single IP, and is added into Active Directory with the name History1. Now with all this traffic eventually we have to upgrade our old History1. So what is the best practice here?

        1. We make a History2, then track down every item that pointed to History1, and update it to point to History2. However user apps, and spreadsheets become overwhelming.

        2. We make History2, then wile trying to have 0 downtime, rename it to History1, and hope that active directory propagates the name change right.

        I have tried it both ways, and both ways suck. Is there a better way?

        Make History2, then when you offline History1, add a DNS entry for History1 as a CNAME that points to History2

        1 Reply Last reply Reply Quote 5
        • JaredBuschJ
          JaredBusch
          last edited by JaredBusch

          I think, beyond that, you are getting into near HA needs.

          1 Reply Last reply Reply Quote 1
          • coliverC
            coliver
            last edited by

            Could you set it up with a DFS namespace? Or is this not file share data and only database data?

            JaredBuschJ 1 Reply Last reply Reply Quote 0
            • JaredBuschJ
              JaredBusch @coliver
              last edited by

              @coliver said in Best Practices:

              Could you set it up with a DFS namespace? Or is this not file share data and only database data?

              He said DB

              s.hacklemanS coliverC 2 Replies Last reply Reply Quote 0
              • s.hacklemanS
                s.hackleman @JaredBusch
                last edited by

                @JaredBusch said in Best Practices:

                @coliver said in Best Practices:

                Could you set it up with a DFS namespace? Or is this not file share data and only database data?

                He said DB

                Right, critical data is DB

                1 Reply Last reply Reply Quote 0
                • coliverC
                  coliver @JaredBusch
                  last edited by

                  @JaredBusch said in Best Practices:

                  @coliver said in Best Practices:

                  Could you set it up with a DFS namespace? Or is this not file share data and only database data?

                  He said DB

                  If that's the case then doing @JaredBusch original suggestion would make the most sense.

                  1 Reply Last reply Reply Quote 0
                  • scottalanmillerS
                    scottalanmiller
                    last edited by

                    I'm with @JaredBusch this is what DNS aliases are for.

                    1 Reply Last reply Reply Quote 0
                    • JaredBuschJ
                      JaredBusch
                      last edited by

                      Prior to the changes, update your DNS TTL to be extremely short.

                      That way there will truly be little downtime for any properly configured system.

                      1 Reply Last reply Reply Quote 2
                      • s.hacklemanS
                        s.hackleman
                        last edited by

                        Could I make a DNS alias called HistoryServer Then point it to both History1? Then point all apps to HistoryServer. When ever an upgrade comes due, I can just update the DNS alias in one place?

                        JaredBuschJ scottalanmillerS 2 Replies Last reply Reply Quote 0
                        • JaredBuschJ
                          JaredBusch @s.hackleman
                          last edited by

                          @s.hackleman said in Best Practices:

                          Could I make a DNS alias called HistoryServer Then point it to both History1? Then point all apps to HistoryServer. When ever an upgrade comes due, I can just update the DNS alias in one place?

                          That wold be the better thing, yes.

                          1 Reply Last reply Reply Quote 1
                          • scottalanmillerS
                            scottalanmiller @s.hackleman
                            last edited by

                            @s.hackleman said in Best Practices:

                            Could I make a DNS alias called HistoryServer Then point it to both History1? Then point all apps to HistoryServer. When ever an upgrade comes due, I can just update the DNS alias in one place?

                            Yes, but if you can do that, you could just rename, too. This is the better way to go, and ideally should be done from the start.

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