Hallo Team,
Hope you can help me this simple doubt.
I have new storage provisioned.
we have to migrate to new storage.
I've created a test pool.
My master and replica is out OLD_Datastore.
I'm following the article here. (VMware Knowledge Base )
What is unclear to me is do I have to select datastore even for Replica ?
As we have more than three pools I would like to know if the others pools will be impacted as well?
If this is a completely new array, then yes, I would absolutely move your replicas over to the new storage. However if this is just an additional LUN/Volume, you should probably be adding this to your linked-clone storage.
After changing the storage you need to run the "Rebalance Storage" composer operation which is essentially a Recompose. Composer will build out the pool on the newly selected storage.
I'd like to add, if your new storage is All-Flash or a Hybrid array - you may have a better experience not separating your replicas from the linked-clones.
If this is a completely new array, then yes, I would absolutely move your replicas over to the new storage. However if this is just an additional LUN/Volume, you should probably be adding this to your linked-clone storage.
After changing the storage you need to run the "Rebalance Storage" composer operation which is essentially a Recompose. Composer will build out the pool on the newly selected storage.
I'd like to add, if your new storage is All-Flash or a Hybrid array - you may have a better experience not separating your replicas from the linked-clones.
After changing the storage you need to run the "Rebalance Storage" composer operation which is essentially a Recompose. Composer will build out the pool on the newly selected storage.
Thanks a lot. Are you saying recompose operation will rebuild VMs again? We have a little problem here.
when we recompose we might loose some settings because we have dedicated desktops
we have to have desktop because of Special printers connected to the desktops.
Can you please clarify if it really going to recompose?
Is the only reason for dedicated desktops your printers? How are they "special"?
Unless you are using persistent disks or a profile/setting management tool your users will lose any customizations.
If the only thing impacted is printers then there are ways to address that either natively with login scripts/GPO/print servers or with third-party tools like PrinterLogic. If more than that is impacted you need to invent in a profile/setting management tool.
They are special just because these are our customers connecting over internet and redirecting their printer over USB.
And USB keep enumerating as result printer name is changing.
Printer name must match including the caps with our internal app.
Just for others, it is recompose operation.
So if you something persistent and not part of master image you will loose all this data.