1 2 Previous Next 19 Replies Latest reply on Aug 13, 2019 11:03 AM by Alhazred242 Go to original post
      • 15. Re: VSCA Update failed again. (6.7.0.2xxx->6.7.0.32...)
        Amin Masoudifard Enthusiast

        And Also if you cannot remove it with ESXCLI, you can try this if you connect to the VCSA DB by management tools like PgAdmin and remove the specified datastore object.

        I explained how to do it in the following link:

        Connect and Manage VCSA Database (PostgreSQL)

        Please mark my comment as the Correct Answer if this solution resolved your problem
        • 16. Re: VSCA Update failed again. (6.7.0.2xxx->6.7.0.32...)
          Alhazred242 Novice

          I need to try it with the DB connect. The host with the Datastore are no exist anymore and I don't have esxcli on the VCSA right? I have found also some Networks, which are no more attached to anything and I cannot remove then.

          After I remove the datastore, it is the same. I cannot remove the Datacenter and the Update failed.

          I check at this time the Database. Also I check the Backupfiles, when I create a new one, without any stats. I think, it is the best way, to Backup all Settings and deploy a new clean VM, without any Config Errors.

          • 17. Re: VSCA Update failed again. (6.7.0.2xxx->6.7.0.32...)
            Amin Masoudifard Enthusiast

            Yes you don't have ESXCLI in VCSA, it's just for ESXi host. So you have to only remove your ORPHANED objects (like that datastore) from vCenter Server database.  But before that, I guess you know, you can remove datastore with PowerCLI but you need to mentioned host's name (required syntax) , So if you can, please try this PowerCLI too:

            Remove-Datastore -Datastore Datastore -VMHost ESXi_IPAddress -Confirm:$false

            and then you can remove Datacenter object:

            Remove-Datacenter Datacenter

             

            Also in following link describe about how to remove datastore forcefully with PowerCLI

            PowerCLI script to forcibly delete a Datastore that is reported as in use. – The Lowercase w

             

            Please mark my comment as the Correct Answer if this solution resolved your problem
            • 18. Re: VSCA Update failed again. (6.7.0.2xxx->6.7.0.32...)
              Alhazred242 Novice

              esxcli I used in the past for a similar Problem.

              Here its looks like a little bit more chaos.

              The Datastore are not attached to any Host. In the Datacenter are no hosts attached. The hosts that I removed, don't attached to this datastore. The Networks are from an old Project. I cannot remove the Networks, the option is not active. I think, the other guys just shutdown the Hosts and don't cleanup the environment. No VMs are attached to the datastore/network (the lists are empty).

              I check the folders with the apiexplorer for the Datastore. I think I try to remove the artifacts from the DB, but IMHO it is the best, I save the Configs, Keys, DRS Settings and Setup a new VCSA. The VCSA was in the past a Windows System (since v5) and we have so many changes since then.

              • 19. Re: VSCA Update failed again. (6.7.0.2xxx->6.7.0.32...)
                Alhazred242 Novice

                I give it up. I remove the datastore from the DB, and can't remove the Datacenter. Try to remove the Networks (also refresh the PG Views for entity and so), the Appliance are broken.

                I setup my new VCSA (with the evaluation License), apply my ESXi Server License and move all active Hosts (create the Clusters, Resource Pools and so on) After then, I only change the IP.

                I think now the Config is clean (I check the datastores and VM for old ISO mounts etc.).

                I take my initial Backup. Tomorrow I only need add IBM Spectrum Protect. and then everything is work back again.

                Thanks for your your help.

                1 2 Previous Next