{"id":5978,"date":"2024-11-18T12:07:34","date_gmt":"2024-11-18T20:07:34","guid":{"rendered":"https:\/\/jetstreamsoft.com\/portal\/?post_type=ht_kb&p=5978"},"modified":"2025-02-24T18:13:57","modified_gmt":"2025-02-25T02:13:57","slug":"vm-protection-fails-virtual-disks-already-has-a-storage-policy-attached","status":"publish","type":"ht_kb","link":"https:\/\/jetstreamsoft.com\/portal\/jetstream-knowledge-base\/vm-protection-fails-virtual-disks-already-has-a-storage-policy-attached\/","title":{"rendered":"VM Protection Fails: “Virtual Disk(s) already has a Storage Policy attached”"},"content":{"rendered":"\n

This article applies to all JSDR software versions.<\/p>\n\n\n\n

Problem<\/h2>\n\n\n\n

Attempting to start VM protection with JetStream DR is unsuccessful and the following error message is reported: \u201cVirtual Disk(s) already has a Storage Policy attached. Cleanup the Virtual Disk state and try again\u201d<\/em>.<\/p>\n\n\n\n

\"\"
Storage policy attached error message.<\/figcaption><\/figure>\n\n\n\n

Troubleshooting<\/h2>\n\n\n\n
    \n
  1. Validate the status of the VM to ensure there are no underlying issues related to its virtual disks.

    <\/li>\n\n\n\n
  2. Ensure the VM intended for protection has no snapshots or pending snapshot consolidation, and that it is not using any snapshot disks.

    <\/li>\n\n\n\n
  3. From vCenter<\/em> select the problematic VM than navigate to: Configure \u2192 Policies<\/strong>\n
      \n
    • Validate any assigned storage policies.<\/li>\n\n\n\n
    • If no storage policy is currently assigned, the default <\/em>storage policy should be manually assigned to the VM.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
      \"\"
      Check assigned storage policies.<\/figcaption><\/figure>\n\n\n\n
        \n
      1. The VM storage policy can also be validated and set from the VM\u2019s Virtual Hardware<\/em> settings screen.<\/li>\n<\/ol>\n\n\n\n
        \"\"
        Check\/set storage policy from the Virtual Hardware screen.<\/figcaption><\/figure>\n\n\n\n
          \n
        1. If the VM is part of an AVS environment, validate the storage policy using the Run command: set-VMStoragepolicy<\/strong>.<\/em><\/li>\n<\/ol>\n\n\n\n
          \"\"
          Azure Run command set-VMStoragepolicy<\/em>.<\/figcaption><\/figure>\n\n\n\n
            \n
          1. Properly assigned storage polic(ies) should display a \u201cCompliant\u201d status.<\/li>\n<\/ol>\n\n\n\n
            \"\"
            All storage policies of the VM are compliant.<\/figcaption><\/figure>\n\n\n\n
              \n
            1. After the VM\u2019s storage polic(ies) have been reset to \u201cdefault\u201d try re-protecting the VM.\n
                \n
              • No error should be triggered when default storage policies are used.

                <\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n

                This problem typically occurs for VMs that have been restored from a backup or migrated, or for VM\u2019s that were manually unregistered and then re-registered (to address other issues).

                JetStream DR protection should be disabled for virtual machines before initiating migration across<\/strong> clusters or datacenters<\/em>. However, JetStream DR protection can remain enabled while using vMotion within<\/strong> the cluster<\/em>.<\/p>\n\n\n\n

                If VM protection is initiated while a VM is concurrently undergoing migration, the JetStream DR protection task will likely fail and report the error “Failed to apply the Storage Policy change.<\/em>“
                VM protection should not be operated while VMs are undergoing any migration tasks.<\/p>\n","protected":false},"excerpt":{"rendered":"

                Problem Attempting to start VM protection with JetStream DR is unsuccessful and the following error message is reported: \u201cVirtual Disk(s) already has a Storage Policy attached. Cleanup the Virtual Disk state and try again\u201d. Troubleshooting<\/p>\n","protected":false},"author":1,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":{"nf_dc_page":"","footnotes":""},"ht-kb-category":[92],"ht-kb-tag":[214],"class_list":["post-5978","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-troubleshooting","ht_kb_tag-vmprotection"],"_links":{"self":[{"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb\/5978","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/comments?post=5978"}],"version-history":[{"count":3,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb\/5978\/revisions"}],"predecessor-version":[{"id":6685,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb\/5978\/revisions\/6685"}],"wp:attachment":[{"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/media?parent=5978"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb-category?post=5978"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb-tag?post=5978"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}