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

    Burned by Eschewing Best Practices

    IT Discussion
    best practices
    38
    1.0k
    331.2k
    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.
    • scottalanmillerS
      scottalanmiller @coliver
      last edited by

      @coliver said in Burned by Eschewing Best Practices:

      @scottalanmiller said in Burned by Eschewing Best Practices:

      @thwr said in Burned by Eschewing Best Practices:

      @DustinB3403 said in Burned by Eschewing Best Practices:

      OP was working in a Hyper-V cluster and needed to migrate his VM's over to the other node. The transfer failed for one VM, and the VM is lost.

      Didn't take a backup prior to beginning work.

      Why should the VM be lost? It will be copied and when every bit is over at the new place, it gets deleted on the original location. Maybe it's just not registered anymore on both hosts?

      That is very odd as there should be shared storage via the iPOD, so nothing was ever "moved".

      Even the metadata would have stayed put in this case.

      Yeah, should have.

      1 Reply Last reply Reply Quote 0
      • dafyreD
        dafyre
        last edited by

        It seems I heard about a bug in Hyper-V under certain circumstances this would happen... I can't remember where I heard it from though.

        scottalanmillerS 1 Reply Last reply Reply Quote 1
        • scottalanmillerS
          scottalanmiller @dafyre
          last edited by

          @dafyre said in Burned by Eschewing Best Practices:

          It seems I heard about a bug in Hyper-V under certain circumstances this would happen... I can't remember where I heard it from though.

          Ouch, that is one scary bug. People get WAY too callous about vmotioning servers. They treat it like a guaranteed safe operation. But in reality it's like a RAID 5 resilver... the chances of failure are still pretty high.

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

            @scottalanmiller Yeah. I've done a number of live migrations, and have seen random failures, but never actually completely lost a VM like that.

            scottalanmillerS 1 Reply Last reply Reply Quote 1
            • scottalanmillerS
              scottalanmiller @dafyre
              last edited by

              @dafyre said in Burned by Eschewing Best Practices:

              @scottalanmiller Yeah. I've done a number of live migrations, and have seen random failures, but never actually completely lost a VM like that.

              True, this is even more dramatic than I have seen before.

              1 Reply Last reply Reply Quote 0
              • DustinB3403D
                DustinB3403
                last edited by DustinB3403

                I'm sure this has been discussed before, but don't store user passwords, don't request them, don't mandate users tell them, and don't set them to something and never allow them to be changed.

                If as a domain administrator you need to get into a user profile to "have access" use your administrative credentials.

                Passwords.

                RojoLocoR 1 Reply Last reply Reply Quote 0
                • RojoLocoR
                  RojoLoco @DustinB3403
                  last edited by

                  @DustinB3403 said in Burned by Eschewing Best Practices:

                  I'm sure this has been discussed before, but don't store user passwords, don't request them, don't mandate users tell them, and don't set them to something and never allow them to be changed.

                  If as a domain administrator you need to get into a user profile to "have access" use your administrative credentials.

                  Passwords.

                  That thread makes me think that after all is said and done, bad management + spineless IT guy = they will keep on having that master list of passwords.

                  DustinB3403D 1 Reply Last reply Reply Quote 0
                  • DustinB3403D
                    DustinB3403 @RojoLoco
                    last edited by

                    @RojoLoco Yeah I figure as much, which this will just open a "he said she said" issue if something with legal ramifications occurs.

                    1 Reply Last reply Reply Quote 0
                    • DustinB3403D
                      DustinB3403
                      last edited by

                      Um... why is this a question again? Decision: To stay physical or move to vitual

                      RojoLocoR 1 Reply Last reply Reply Quote 0
                      • DashrenderD
                        Dashrender
                        last edited by

                        I had a client that maintained a password list for every employee once. I showed the boss how this was completely unnecessary, she didn't change.

                        coliverC 1 Reply Last reply Reply Quote 0
                        • DashrenderD
                          Dashrender
                          last edited by

                          That question reminds me of a post yesterday or so about a PCI auditor claiming to need that same info... WTF?

                          1 Reply Last reply Reply Quote 1
                          • RojoLocoR
                            RojoLoco @DustinB3403
                            last edited by

                            @DustinB3403 said in Burned by Eschewing Best Practices:

                            Um... why is this a question again? Decision: To stay physical or move to vitual

                            Posts like that make me think SW makes their staff create puppet accounts to post such nonsense so they will have something to feature, because apparently they have been scrambling for feature worthy posts lately.

                            1 Reply Last reply Reply Quote 1
                            • brianlittlejohnB
                              brianlittlejohn
                              last edited by

                              I like the first line of the post... "I didn't find much searching..." I call BS... lol

                              scottalanmillerS travisdh1T 2 Replies Last reply Reply Quote 2
                              • scottalanmillerS
                                scottalanmiller @brianlittlejohn
                                last edited by

                                @brianlittlejohn said in Burned by Eschewing Best Practices:

                                I like the first line of the post... "I didn't find much searching..." I call BS... lol

                                LOL. There is a lot of that.

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

                                  @brianlittlejohn said in Burned by Eschewing Best Practices:

                                  I like the first line of the post... "I didn't find much searching..." I call BS... lol

                                  If they only tried the search available on the site rather than a Google site search, I might not outright laugh at them, only on the inside.

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

                                    @Dashrender said in Burned by Eschewing Best Practices:

                                    I had a client that maintained a password list for every employee once. I showed the boss how this was completely unnecessary, she didn't change.

                                    At my last position they wouldn't let me enforce password complexity because there was a password list the managers wanted to keep to.

                                    1 Reply Last reply Reply Quote 0
                                    • DustinB3403D
                                      DustinB3403
                                      last edited by

                                      Keeping systems and data around for extremely long periods of time leads to major issues. Like having to keep all records available..

                                      "As long as records are retained, they are legally discoverable, regardless whether their retention period has expired." - from the American Bar Association.

                                      DashrenderD 1 Reply Last reply Reply Quote 1
                                      • DashrenderD
                                        Dashrender @DustinB3403
                                        last edited by Dashrender

                                        @DustinB3403 said in Burned by Eschewing Best Practices:

                                        Keeping systems and data around for extremely long periods of time leads to major issues. Like having to keep all records available..

                                        "As long as records are retained, they are legally discoverable, regardless whether their retention period has expired." - from the American Bar Association.

                                        yeah, people just don't get that until they get burned by it. We have people who have email that goes back 20 years... it's just crazy to me.

                                        But when my boss goes and digs out some email from 5+ years ago.. she loves to come and say.. See I needed this thing from 5+ years ago, it's a good thing I kept it.

                                        DustinB3403D scottalanmillerS 2 Replies Last reply Reply Quote 0
                                        • DustinB3403D
                                          DustinB3403 @Dashrender
                                          last edited by

                                          @Dashrender said in Burned by Eschewing Best Practices:

                                          @DustinB3403 said in Burned by Eschewing Best Practices:

                                          Keeping systems and data around for extremely long periods of time leads to major issues. Like having to keep all records available..

                                          "As long as records are retained, they are legally discoverable, regardless whether their retention period has expired." - from the American Bar Association.

                                          yeah, people just don't get that until they get burned by it. We have people who have email that goes back 20 years... it's just crazy to me.

                                          But when my boss goes and digs out some email from 5+ years ago.. she loves to come and say.. See I needed this thing from 5+ years ago, it's a good thing I kept it.

                                          Exactly, but the thing that immediately comes in in court is "oh hey you have evidence that shows favor in this light etc, give us everything from then?"

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

                                            @Dashrender said in Burned by Eschewing Best Practices:

                                            But when my boss goes and digs out some email from 5+ years ago.. she loves to come and say.. See I needed this thing from 5+ years ago, it's a good thing I kept it.

                                            And you should properly respond "We got lucky that no one did a legal discovery, too." Remind her, every time, that she's "gotten lucky" from being risky. It's not just that keeping data makes you vulnerable, it also means that you HAVE to keep all data. You can't pick and choose what gets kept. It's all or nothing.

                                            1 Reply Last reply Reply Quote 1
                                            • 1
                                            • 2
                                            • 25
                                            • 26
                                            • 27
                                            • 28
                                            • 29
                                            • 50
                                            • 51
                                            • 27 / 51
                                            • First post
                                              Last post