<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Migrating complicated windows fileservers from vmware quickly?]]></title><description><![CDATA[<p dir="auto">We have several large file servers (each has 20+ disks that are from 2-4TB in size). VMWare is currently connecting via iSCSI to the SAN they are on and exposing them as virtual disks to the VM.... and therein is the problem.  VMFS <img src="https://xcp-ng.org/forum/assets/plugins/nodebb-plugin-emoji/emoji/android/1f615.png?v=1d3f495298e" class="not-responsive emoji emoji-android emoji--confused" style="height:1.4em;width:auto;vertical-align:middle" title=":/" alt="😕" /> I can't just attach those iSCSI targets to XCP-NG and have them as happy disks on the new system.</p>
<p dir="auto">I have room on other SANs or on XOSTOR for the new disk.... but I can think of only one (sketchy) way to do a conversion that won't take DAYS of downtime to complete.  I'm wondering, even if I changed datastores from the external SANs to vSan, if the migration process would even have a prayer of completing at all.</p>
<p dir="auto">The only idea I have come up with, and yes.. this seems VERY stupid,  is to:<br />
Expose some iSCSI targets from a SAN directly to the files server VM<br />
Setup an OS RAID mirror for each disk<br />
Let them complete mirroring in the OS<br />
Remove the old drives from the mirror<br />
Shutdown the VM<br />
Migrate the VM to our XCP cluster<br />
Bring up the VM<br />
Add new disks coming from XOSTOR to the VM<br />
Add the new disks as mirror members in the OS raid mirror<br />
Wait for the mirror to complete<br />
Remove the iSCSI disks on the SAN from the mirror<br />
Destroy the mirror and return it to a standard disk setup</p>
<p dir="auto">Looking for feedback on my level of stupidity <img src="https://xcp-ng.org/forum/assets/plugins/nodebb-plugin-emoji/emoji/android/1f605.png?v=1d3f495298e" class="not-responsive emoji emoji-android emoji--sweat_smile" style="height:1.4em;width:auto;vertical-align:middle" title=":sweat_smile:" alt="😅" /> and wondering if someone has been down this road before.</p>
]]></description><link>https://xcp-ng.org/forum/topic/9760/migrating-complicated-windows-fileservers-from-vmware-quickly</link><generator>RSS for Node</generator><lastBuildDate>Wed, 07 Oct 2026 16:48:52 GMT</lastBuildDate><atom:link href="https://xcp-ng.org/forum/topic/9760.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 09 Oct 2024 01:01:07 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Migrating complicated windows fileservers from vmware quickly? on Wed, 09 Oct 2024 19:47:45 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/vaewyn" aria-label="Profile: vaewyn">@<bdi>vaewyn</bdi></a> another reason for leaving vmware <img src="https://xcp-ng.org/forum/assets/plugins/nodebb-plugin-emoji/emoji/android/1f609.png?v=1d3f495298e" class="not-responsive emoji emoji-android emoji--wink" style="height:1.4em;width:auto;vertical-align:middle" title=";-)" alt="😉" /> in would go for robocopy then.</p>
]]></description><link>https://xcp-ng.org/forum/post/83964</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/83964</guid><dc:creator><![CDATA[rtjdamen]]></dc:creator><pubDate>Wed, 09 Oct 2024 19:47:45 GMT</pubDate></item><item><title><![CDATA[Reply to Migrating complicated windows fileservers from vmware quickly? on Wed, 09 Oct 2024 19:45:18 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/rtjdamen" aria-label="Profile: rtjdamen">@<bdi>rtjdamen</bdi></a> Correct...  in VMWare RDMs created quite a few issues so they are all as VMFS datastores with VMDKs inside them that are then exposed to the VM as drives.</p>
<p dir="auto">Unfortunately, this is like the ONLY thing that RDMs would actually shine for <img src="https://xcp-ng.org/forum/assets/plugins/nodebb-plugin-emoji/emoji/android/1f61f.png?v=1d3f495298e" class="not-responsive emoji emoji-android emoji--worried" style="height:1.4em;width:auto;vertical-align:middle" title=":worried:" alt="😟" /></p>
]]></description><link>https://xcp-ng.org/forum/post/83963</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/83963</guid><dc:creator><![CDATA[vaewyn]]></dc:creator><pubDate>Wed, 09 Oct 2024 19:45:18 GMT</pubDate></item><item><title><![CDATA[Reply to Migrating complicated windows fileservers from vmware quickly? on Wed, 09 Oct 2024 19:40:40 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/shufflebox" aria-label="Profile: Shufflebox">@<bdi>Shufflebox</bdi></a> agree</p>
]]></description><link>https://xcp-ng.org/forum/post/83962</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/83962</guid><dc:creator><![CDATA[rtjdamen]]></dc:creator><pubDate>Wed, 09 Oct 2024 19:40:40 GMT</pubDate></item><item><title><![CDATA[Reply to Migrating complicated windows fileservers from vmware quickly? on Wed, 09 Oct 2024 19:40:30 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/vaewyn" aria-label="Profile: vaewyn">@<bdi>vaewyn</bdi></a> so they are not raw device maps? if they were the disks are allready ntfs formatted and mapping them directly should not be an issue. i am not familiar with an other option for this is vmware. maybe it is worth a try to create a testcase for it.</p>
]]></description><link>https://xcp-ng.org/forum/post/83961</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/83961</guid><dc:creator><![CDATA[rtjdamen]]></dc:creator><pubDate>Wed, 09 Oct 2024 19:40:30 GMT</pubDate></item><item><title><![CDATA[Reply to Migrating complicated windows fileservers from vmware quickly? on Wed, 09 Oct 2024 19:35:00 GMT]]></title><description><![CDATA[<p dir="auto">I like the idea of exposing a new LUN to the VMware guest via iSCSI.  That would get you around the 2TB vdi limitation on your xcp-ng cluster, and let you just detach from the old and reattach on the new all via iSCSI.</p>
<p dir="auto">The part that feels a bit risky is setting up the Windows RAID mirror with an existing drive with data.  I don't work with Windows Server all  that often, so maybe it's easy and knows not to risk the existing data.<br />
I would probably replace that step with some Robocopy tasks.</p>
]]></description><link>https://xcp-ng.org/forum/post/83960</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/83960</guid><dc:creator><![CDATA[Shufflebox]]></dc:creator><pubDate>Wed, 09 Oct 2024 19:35:00 GMT</pubDate></item><item><title><![CDATA[Reply to Migrating complicated windows fileservers from vmware quickly? on Wed, 09 Oct 2024 10:45:07 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/rtjdamen" aria-label="Profile: rtjdamen">@<bdi>rtjdamen</bdi></a> They are currently VMware datastores (VMFS)  that have drives on them (vmdks) attached to the VMs so <img src="https://xcp-ng.org/forum/assets/plugins/nodebb-plugin-emoji/emoji/android/1f61e.png?v=1d3f495298e" class="not-responsive emoji emoji-android emoji--disappointed" style="height:1.4em;width:auto;vertical-align:middle" title=":(" alt="😞" />  I can easily expose the iSCSI targets but neither Windows or XCP-NG understands what to do with a datastore target from VMware</p>
]]></description><link>https://xcp-ng.org/forum/post/83923</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/83923</guid><dc:creator><![CDATA[vaewyn]]></dc:creator><pubDate>Wed, 09 Oct 2024 10:45:07 GMT</pubDate></item><item><title><![CDATA[Reply to Migrating complicated windows fileservers from vmware quickly? on Wed, 09 Oct 2024 04:44:59 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/vaewyn" aria-label="Profile: vaewyn">@<bdi>vaewyn</bdi></a> so your disks are not vmdk but direct attached to the vm? wouldn't it work to just connect those iscsi targets direct from the san to the vm itself? if i understand your situation correct there wouldn't be a reason of migrating them? otherwise your idea of creating a mirror could work as well.</p>
<p dir="auto">We did have the same issue and we decided to create a new machine and use robocopy for migration... not ideal but this way it did take only a few days of preseeding the fileserver and a quick last synch when do the migration itself.</p>
<p dir="auto">it's a hard one but i believe it would be possible</p>
]]></description><link>https://xcp-ng.org/forum/post/83870</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/83870</guid><dc:creator><![CDATA[rtjdamen]]></dc:creator><pubDate>Wed, 09 Oct 2024 04:44:59 GMT</pubDate></item></channel></rss>