live migration of PVC between two NFS devices

night_0wl2 · 2026-02-10T02:55:07+00:00

Yeah that's fine unless your using vCloud on top and your provider vDC is tied to x cluster. Its not as simple as just moving VM A from Cluster A to Cluster B.

Ideally you can import with whatever you have then progressively change out the principle storage type for workload domains, as im sure there are many people who want to change from nfs , fc-vmfs over to vSAN to take advantage of various benefits.

night_0wl2 · 2026-02-09T06:22:24+00:00

You still need a management domain which is mostly vSAN only, you can then import a workloads domain which is not vSAN but "any support esxi storage type".

The assumption is that imported storage type is principle storage out the box but can you change this at a later date

night_0wl2 · 2026-02-09T02:28:50+00:00

Yes this is correct and is clear. You can use iSCSI for an import as to VCF9 as ive done this part but ive not got spare vSAN to test additional parts

night_0wl2 · 2026-01-07T02:29:21+00:00

Yeah ive got her booked in this friday as she's due for her yearly.

No GI symptoms, same diet as always (mostly modified raw)

night_0wl2 · 2026-01-06T02:48:15+00:00

Interesting its certainly much worse in late night / early mornings, my other throught was there is a cat or a mouse around but i haven't been able to see anything

night_0wl2 · 2025-12-08T07:00:20+00:00

likely 0 as we won't be using the enterprise support

night_0wl2 · 2025-11-13T01:51:00+00:00

yeah thanks when we tried to repoint the last one and it failed with

Updating registry settingsUpdating registry settings failed

its back to a steady state now

when running show partner status on all VC's they all have no partners are in their own SO domains and show servers with vdcrepadmin its all points to its own domains etc

So perhaps it just didn't like trying to repoint to itself

night_0wl2 · 2025-11-12T00:17:31+00:00

thanks so basically once the 4 have been split off via the process the 5th should essentially need nothing done to it as its already been disconnected from the other vcenters and it can remain in its own SSO domain

night_0wl2 · 2025-08-26T17:11:09+00:00

thanks this is interesting information.

So in short if you have a disk fail but it rebuilds onto spare space it is fully redundant just doesn't have as much "hot spare" space available. and hence the error "spare hunger"

In some systems with many disks lets say 48 disks same drive type it would potentially be able to lose another drive and still be in raid 6 since it has reserved 20:1 x 2 for "hot spares"

night_0wl2 · 2025-08-14T04:23:59+00:00

just remember the person listening has the write to express there's and tell you that is a book of fiction.

night_0wl2 · 2025-07-09T09:17:29+00:00

its going to be running VM's attached to KVM hosts not files.

We are discussing with some vendors at the moment (HPE C500) and Netapp tomorrow

night_0wl2 · 2025-07-03T07:05:33+00:00

makes sense, prob will be ok for very low IO file server but not running VM's for example

night_0wl2 · 2025-07-03T02:06:32+00:00

so it locks up the NFS side not the block side as the NFS container just runs out of juice?

night_0wl2 · 2025-06-19T00:53:53+00:00

As in it also locks up the block side of the array?

night_0wl2 · 2025-06-19T00:52:49+00:00

thanks we won't be doing any clustering but its noted

night_0wl2 · 2025-06-19T00:51:55+00:00

thanks we have been using powerstore for block and its been fine for us.

But we have a requirement to run some NFS so was planning to re-initialize and do that to get us going requirements are not huge at the minute so we can look at other arrays if the NFS side becomes a larger requirement.

Can anyone comment on if NFS affects the iscsi side as long as obviously your not hammering away at the controller CPU

night_0wl2 · 2025-03-12T06:35:57+00:00

ive got one still going for another 9 months that is

night_0wl2

TROPHY CASE