LUN/Datastore is used as persistent scratch location for serveral hosts.
In order to upgrade VMFS3 to VMFS5 (i know there is a possibility to make an in-place upgrade, but i want to create a new vmfs5 datastore) the attached LUN/Datastore must be deleted from the hosts.
Is it necessary to reconfigure the "ScratchConfig.ConfiguredScratchLocation" for all hosts to another LUN/Datastore or is it possible to delete the Datastore and recreate it after the upgrade to VMFS5?
Thanks for your help.
The question you have to ask yourself, is the information in the scratch location important to yourself. Its used for temporary information such a system swap, diagnostic information and logs. Also if you change the scrach location you are going to have to restart your host for the changes to take.
You could change the scratch location to an alternate LUN/Datastore (as long as all host have their own scratch folder and not shared) reboot, receate your VMFS5 datastore, then switch the scratch location back, and reboot once more for the changes to take.
You probably should recreate the scratch config location. This should not cause any problems since it is mostly just log files. the configuration files are not stored on the scratch config space. I helped a customer who tried to move the folders and it didn't work very well, he decided just to recreate after making the change to the new datastore.
Thanks for your answers.
I moved the persistent scratch location to another LUN/Datastore.
(Maintenace mode and reboot for every ESXi host)
I tought this would be the best solution for me.
The persistent scratch location uses the UUID from the volume as part of the folder path.
By adding new storge a new UUID will be created. This was the reason for me to move the persistent scratch location to another LUN/Datastore.
In my case for the same LUN:
/vmfs/volumes/482ad53f-150a1320-86cf-001e4f38cb49 (old UUID)
/vmfs/volumes/4fc76096-933e0970-7aa3-d067e5e901cd (new UUID)