Jump to content
Welcome to our new Citrix community!
  • 0

Manifest file is invalid. Can't add vdisk PVS 7.6


Trea Adams

Question

Hi All,

 

I'm trying to import a vDisk version from our production environment.  The avhd and pvp files have been copied over to the DR PVS server, and manifest file in the same location as the vDisks.  When trying to add vDisk Versions I get an error message "Manifest file for <vDisk name> is invalid.  Cannot add vDisk" and "The scan did not find any new vDisks."

 

The old versions have been removed and matches the versions in the manifest file.  I've had a look at this article but am still getting the same error -

https://support.citrix.com/article/CTX138465?_ga=1.2938610.313232373.1491819498

 

 

Any help would be greatly appreciated.

 

Thanks

Link to comment

5 answers to this question

Recommended Posts

  • 1

Hi Trea,

 

Try to follow the below mentioned steps one by one,it works for us:

 

  • Copy the versioned vDisk including all *.vhd, *.ahvd, and *.pvp files. (Don’t copy *.lok files).
  • Rename or label the copied files as required.
  • Open the PVS console, right click the source vDisk, and choose ‘Export vDisk…’. A dialog appears.
  • In the export dialog, choose the the latest version in the drop-down menu named ‘Export versions starting at’, then click OK. After a short delay the dialog closes. In the source vDisk’s store you’ll find a manifest file containing the entire information about the versions of that vDisk. The manifest file name matches with the name of the vDisk and it has a .xml suffix
  • Rename the manifest file using the name of the copied vDisk.
  • Open the manifest file in a text editor and accurately replace all references to the name of the source vDisk with the name of the copied vDisk. Double-check the changes, then save the file.
  • Now, you should have a set of VHD/AVHD/PVP file and an XML file with the same base file name. And the manifest/XML refers to the new VHD and AVHD files.
  • In the PVS console, right click the vDisk store, and choose ‘Add or Import Existing vDisk…’. A dialog appears.
  • In the import dialog, check the settings for Site, Store, and Server, then click Search. After a short delay the copied vDisk will be displayed.
  • Check the vDisk, check/uncheck the load balancing option as wanted, then click Add. After a short delay a popup appears saying that the import was successful. Click OK, then click Close in the import dialog.

 

Hope this helps.

  • Like 1
Link to comment
  • 0

Hi Trea, occasionally similar issues need resolving and manifest file is not available, such as when vdisk and versions needed to be imported from shared storage after reverting to very old snapshot of database which doesnt have vdisk or versions.

 

One method to achieve this is to:

  1. Via file browser -> Move all files except for the base vdisk file from the store path.
  2. Via PVS console ->Import vdisk, you will be prompted to create new pvp file.
  3. Via PVS console ->Create a version, promote to production 
  4. Via file browser -> Move original version file (.1.avhd/.1.avhx) back to store path, over writing only the the corresponding "new blank version file", dont change the pvp or lok files.

  5. Via PVS console ->Create another version, promote to production 

  6. Via file browser -> Move corresponding original version file back to store-path, over writing only the corresponding "new blank version file", , dont change the pvp or lok files.

  7. Repeat 5& 6 until all versions are restored.

Usually this would only fail to work if there was some corruptions between avhd/avhx chains, and would only be visible failing when attempting to boot.

 

 

 

 

 

 

Link to comment
  • 0
On 4/26/2017 at 2:14 AM, JAYESH SHRINGARPURE said:

Hi Trea,

 

Try to follow the below mentioned steps one by one,it works for us:

 

  • Copy the versioned vDisk including all *.vhd, *.ahvd, and *.pvp files. (Don’t copy *.lok files).
  • Rename or label the copied files as required.
  • Open the PVS console, right click the source vDisk, and choose ‘Export vDisk…’. A dialog appears.
  • In the export dialog, choose the the latest version in the drop-down menu named ‘Export versions starting at’, then click OK. After a short delay the dialog closes. In the source vDisk’s store you’ll find a manifest file containing the entire information about the versions of that vDisk. The manifest file name matches with the name of the vDisk and it has a .xml suffix
  • Rename the manifest file using the name of the copied vDisk.
  • Open the manifest file in a text editor and accurately replace all references to the name of the source vDisk with the name of the copied vDisk. Double-check the changes, then save the file.
  • Now, you should have a set of VHD/AVHD/PVP file and an XML file with the same base file name. And the manifest/XML refers to the new VHD and AVHD files.
  • In the PVS console, right click the vDisk store, and choose ‘Add or Import Existing vDisk…’. A dialog appears.
  • In the import dialog, check the settings for Site, Store, and Server, then click Search. After a short delay the copied vDisk will be displayed.
  • Check the vDisk, check/uncheck the load balancing option as wanted, then click Add. After a short delay a popup appears saying that the import was successful. Click OK, then click Close in the import dialog.

 

Hope this helps.

Hi jayesh  do u have any sop documentation prepared if yes plz share.

Link to comment
  • 0

Team,

 

When trying to add vDisk Versions I get an error message "Manifest file for <vDisk name> is invalid.  Cannot add vDisk" and "The scan did not find any new vDisks."

 

Copied AVHD ; PVP and XML file from LAB store location to Production store location (Lab and Prod environment has different servers)

 

please suggest

 

 

Capture.PNG

Capture 1.PNG

Capture error.PNG

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...