What will be appstack and writable behavior during refresh recompose and re balance horizon view pool and desktop ? have you ever face any issues , your recommendation , suggestion if any ?.
Note : Certainly I am plan to check this in my lab environment but your suggestions and recommendations are most welcome .
I'm not quite sure were your aiming at here but here goes
Anyways. when you refresh or recompose a machine a user first needs to be logged off, after that the machine can be recomposed, that's how View works.
If, for some reason, an appstack or writable volume is still attached to a machine, if you recompose or refresh the appstacks and writable volumes will be detached after the machine has been reconfigure.
If you remove the machine after use and the appstack and writable volume is still attached, writable volume will be deleted (because it is read/write) and appstack will simply be detached because it is read-only.
When a user logs off the machine is reconfigured and thus now writable volumes and appstacks arent attached anymore.
After the disks are removed from the machine it is recomposed or refreshed as usual.
In a scenario I have attached writable and appstack to machine name I mean.
I'm not quite sure were your aiming at here but here goes
Anyways. when you refresh or recompose a machine a user first needs to be logged off, after that the machine can be recomposed, that's how View works.
If, for some reason, an appstack or writable volume is still attached to a machine, if you recompose or refresh the appstacks and writable volumes will be detached after the machine has been reconfigure.
If you remove the machine after use and the appstack and writable volume is still attached, writable volume will be deleted (because it is read/write) and appstack will simply be detached because it is read-only.
I have tested app-stack behavior during refresh and recompose and as you said as a default behavior horizon view recompose and refresh , machine will be auto powered off for doing the refresh / recompose , by this time attached app-stack will detach , then the refresh and recompose will go forward . Once it complete while powering on the VM , app stack will re-attached to VM.
If appstacks are not detached automatically during the poweroff , refresh and recompose will do the reconfiguration based on the pool settings and it will remove it safely.
In the case appstacks assigned to user , it will detach once the user is logout.
Do keep in mind though that writable volumes can get deleted by an automated process.
If the machine is scheduled to recreate after logoff it could be that the remove machine command is send to VCenter before the reconfigure command is being send thus removing the machine with writable volume attached.
Appstacks will never be deleted as they are secured and read only.
I noticed that time to time some users find their writable volumes deleted when View Server delete Instant Clones. For example it happened today after Image Push operation. Is there any solution to prevent writable volumes from deletion during automated process?
No there isn't. Bottom line is that when the writable is being detached it is deletable. If you were to change the vmx file to make it undeletable i believe you can't use it anymore.
Why not refresh the machine after use instead of delete it? This way if the writable is attached during refresh it will eventually be removed due to the recompose process.