XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    "Orphan VDIs" and "VDIs attached to Control Domain" Safe to delete all?

    Scheduled Pinned Locked Moved Xen Orchestra
    11 Posts 6 Posters 2.1k Views 3 Watching
    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.
    • J Offline
      jweez
      last edited by

      Hey,

      Is it safe to forget all "Orphan VDIs" and "VDIs attached to Control Domain" under Dashboard/Health?

      Can it hurt any running vm's?

      tjkreidlT 1 Reply Last reply Reply Quote 0
      • DanpD Offline
        Danp Pro Support Team
        last edited by

        You should be fine deleting orphan VDIs. This isn't the case with VDIs attached to Control Domain, which likely belong to an active VM.

        J 2 Replies Last reply Reply Quote 0
        • J Offline
          jweez @Danp
          last edited by

          Danp Why do them show up there?

          /John

          1 Reply Last reply Reply Quote 0
          • J Offline
            jweez @Danp
            last edited by

            Danp Everyone have this snapshot "camera" to the right of there name.

            Capture.PNG

            DanpD 1 Reply Last reply Reply Quote 0
            • DanpD Offline
              Danp Pro Support Team @jweez
              last edited by

              jweez So you have 115 snapshots attached to the control domain?! That isn't normal behavior. If this were my host, I would be investigating why this is occurring.

              What version of CH / XCP-ng are you running? Is it fully patched?

              1 Reply Last reply Reply Quote 0
              • DarkbeldinD Offline
                Darkbeldin Vates 🪐 Pro Support Team
                last edited by

                Just to give context, VDI attach to the domain are backup related. During backup process the VDI need to be downloaded by XOA so it is attached to dom0 and downloaded from there. Normally this VDI should be detached after the backup is finished but if you have backup error the VDI could stay stuck attached to dom0.

                So in your case if you have backup Running be careful with this VDI but if they are old VDI you can safely remove them.

                1 Reply Last reply Reply Quote 2
                • J Offline
                  jshiells
                  last edited by

                  I know this is an old topic but i have a quick followup question... in regards to "You should be fine deleting orphan VDIs."

                  don't VID's show up as "orphan"'ed during a cross pool migration? if that's the case a person should make sure no migration or backup tasks are running before deleting. correct?

                  1 Reply Last reply Reply Quote 0
                  • olivierlambertO Offline
                    olivierlambert Vates 🪐 Co-Founder CEO
                    last edited by

                    During a backup or storage migration, you should be careful yes.

                    1 Reply Last reply Reply Quote 0
                    • tjkreidlT Offline
                      tjkreidl Ambassador @jweez
                      last edited by tjkreidl

                      jweez Something similar to this might be useful. I would think it would work on XCP-ng, as well. https://raw.githubusercontent.com/deepix/shell-fu/master/orphan_vdi.bash

                      1 Reply Last reply Reply Quote 1
                      • J Offline
                        jshiells
                        last edited by

                        so here is where i'm going with this and why this "Orphan VDIs" section scares the pee out of me.

                        so as far as i am aware there are three situations where a VDI should show up on this "Orphan VDIs" list when its not actually Orphaned.

                        1. during a cross pool migration (maybe normal disk migrations?)
                        2. during some types of backups
                        3. fast cloning a VM
                        4. maybe more?

                        so lets just say someone thinks they are being "helpful" and wants to clean up what they think is a mess in this "Orphan VDIs" section.. and just deletes everything in it.... and now people are going to have a bad day if any of the above situations were listed...

                        please feel free to correct me if I am wrong here.

                        and if i'm not wrong, can there be some checks put in XOA to NOT allow deletion of "Orphan VDIs" that are not actually orphaned?

                        1 Reply Last reply Reply Quote 0
                        • olivierlambertO Offline
                          olivierlambert Vates 🪐 Co-Founder CEO
                          last edited by

                          Nothing like that could happen. If your orphaned VDI is in use, it will error out with "VDI in use".

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