SAN LUNs Do Not Act Like NAS Shares
-
@ntoxicator said:
Thank you again Scott!
Now... what you think would be more reliable or simpler solution?
Use XenServer to migrate(move) the disk to the new Storage Repository (NFS)? This will take several hours.. And I'm worried that if something fails the entire disk migration will be lost.. or will XenServer do block by block and if any fail, it will keep on the original SR?
Or should I just attach a new disk to the Windows Server VM (From the NFS Storage Repository) and manually copy all the files over using Microsofts data copy utility.. so the share folders & file permissions are carried over
As I'll need the keep the same drive letter
Are you currently not doing backups of this system? While losing the data is an understandable concern that risk should be tempered by having an offline copy of it somewhere.
-
The windows DC is backed up to Carbonite.
I am backing up the LUN's on the Synology Rackstation a remote disk.
-
@ntoxicator said:
The windows DC is backed up to Carbonite.
I am backing up the LUN's on the Synology Rackstation a remote disk.
Could you restore from that backup to the NFS storage and then add that to Windows? Still would have a potential network bottleneck and would still require downtime but you wouldn't be as concerned about data dropping.
-
I probably could pull down the backup from carbonite as its backing up the entire data partition. However, then comes the restore time.
The Synology LUN backup is just LUN. cannot export to NFS. So would have to use Carbonite to restore.
I suppose all the options have their issues. no clean cut solution
-
Why does the XenMotion approach not work?
-
I have no experience with XenMotion?
-
@ntoxicator said:
I have no experience with XenMotion?
That's realistically the only tool to be looking at here. It will "just do what you want." It will move the storage over, while everything is running, without downtime or extra tools.
-
XenMotion is paid product / support. Again right now we're using XenServer Free edition.
Great it can move the storage disk over while its running. However, users are constantly writing data to it as its an SMB Share from Windows Domain controller
Folders are on this drive "data disk" and windows domain controller handles the folder shares & file permissions.
-
@ntoxicator said:
XenMotion is paid product / support. Again right now we're using XenServer Free edition.
XenMotion is available in XenServer... I can do it in my home lab without any issues.
Check out the wiki link I posted earlier.
https://wiki.xenserver.org/index.php?title=Storage_XenMotion
-
@ntoxicator said:
Great it can move the storage disk over while its running. However, users are constantly writing data to it as its an SMB Share from Windows Domain controller
Folders are on this drive "data disk" and windows domain controller handles the folder shares & file permissions.
That's the point... it was literally designed for this.
It writes all new changes to the new location and merges the unchanged data into the new location. You won't risk downtime or losing writes with this technology.
-
@ntoxicator said:
XenMotion is paid product / support. Again right now we're using XenServer Free edition.
I know nothing of the non-free version. I would never buy that or recommend a paid version. XenMotion is free.
-
@ntoxicator said:
Great it can move the storage disk over while its running. However, users are constantly writing data to it as its an SMB Share from Windows Domain controller
That is exactly what XenMotion is for. If users were not writing to it, you would have no need for XenMotion, you could just copy.
-
Thank you. I will look into it?? As Within XenCenter, I click the XenServer node and the disk attached and when I click "move" it throws me an error.
however, when the VM is shut down - i can move the disk without problem..
Its just concerning that its a Windows Server domain, with shares. How would it still be able to write the data to the new Storage Repository and put it back together and be fine? meh
-
@scottalanmiller said:
XenMotion
Article I found
https://www.citrix.com/blogs/2012/08/24/storage_xenmotion/ -
@ntoxicator said:
Thank you. I will look into it?? As Within XenCenter, I click the XenServer node and the disk attached and when I click "move" it throws me an error.
however, when the VM is shut down - i can move the disk without problem..
Its just concerning that its a Windows Server domain, with shares. How would it still be able to write the data to the new Storage Repository and put it back together and be fine? meh
It's all block data. It doesn't really care what is sitting on top of it. What version of XenServer are you running?
-
@ntoxicator said:
@scottalanmiller said:
XenMotion
Article I found
https://www.citrix.com/blogs/2012/08/24/storage_xenmotion/2012... back when it was a Citrix product. We mean XenMotion now, not then
Citrix donated the entire XenServer project to Linux Foundation since 2012. -
@scottalanmiller said:
@ntoxicator said:
@scottalanmiller said:
XenMotion
Article I found
https://www.citrix.com/blogs/2012/08/24/storage_xenmotion/2012... back when it was a Citrix product. We mean XenMotion now, not then
Citrix donated the entire XenServer project to Linux Foundation since 2012.This information, or rather the lack of knowing it, has been the cause for countless misunderstandings in the hypervisor world!
-
Same with any products, really. Outdated information whether by time or product version is always confusing. Things change over time. 2012 is a generation ago in IT time.
-
Great info... I've been using Citrix XenServer since around 2012. The Free version. Had the Enterprise version with HA and other features in the small datacenter I helped manage. it was $$$$$$$$$$$$$ along with using Citrix XenApp $$$$$$$
Probably why I had the bad taste in my mouth.. better feeling now they passed it to Linux foundation.
-
For most of a decade, people tried to promote KVM as open source because Xen wasn't exactly open for the first couples years back in like 2003. That legacy lasted for something like five times the length of the software actually not being open. Once someone had written it down, everyone just kept repeating it.
