@Dashrender
I am really new to the whole Hyper-V stuff so I don't really understand what you are implying.
The 512MB is the RAM memory. I do not understand how is that matter at all but it seem it matter. I might be on the wrong universe here but somehow it is working and I am happy.
@Dashrender
yes. but previously I set it with 512MB which fit into the 1GB storage
@Dashrender
previously it failed because of Kerboros credential. After giving it delegate rights the live migration works.
@Dashrender
currently 125GB (starting size) on Disk 3 of 1TB.
@Dashrender
Actually you were right! Not with the comma part, but the problem is I gave it 1TB size but linked it to 1GB partition. I didn't show the resource down belong it it only show 883MB out of 1GB
Now it pointed to 1TB partition so it is working now.
LOL!!!! I am pretty sure it is a comma
@Dashrender
From your previous message currently I am redoing the whole iscsi and volume clustering. I will report back if the problem resolved.
@Dashrender
here is the mountvol.exe result.
@Dashrender
Now that you mentioned that. somehow the drives on both server (which should be identical) is not.
@travisdh1
The VM reside on the cluster drive on C:\clusterstorage\volume1
I might be overlooking this and screwed up somewhere along the way.. but shouldn't C:\clusterstorage\volume1 be a virtual drive? connected by iscsi?
@Dashrender
The cluster storage space is configured with starWind vSAN. I gave it a good 1TB (1,0001GB)
So after the whole Live Migration failure, I have managed to bring it online, as screen shot above. Now all the setting should be set correctly, however it still failed on me when I try to create a VM with 2GB memory. I named it Zeus (stole the idea from the naming server idea).
At this point I am dumbfold and confused. Life as a sole admin is hard.
Helo me MangoLassi, you are my only hope.
@scottalanmiller
How do you name it now with multiple servers? I have 5 and it is going by numerical.
I am curious how do you name your servers? I saw some named as Server1, Server2 to Mars, Venus, Jupiter, or just plain random like Server1, COD13, I79sdH12...
What do you use as a guideline, if any, to name the servers. If you have something else to name workstation I like to know as well. Cheers!
@Lakshmana
This article pointed out problem with authentication http://www.virtualizationadmin.com/articles-tutorials/microsoft-hyper-v-articles/general/diagnosing-live-migration-failures-part2.html
This article resolved the problem http://www.hyper-v.nu/archives/pnoorderijk/2013/03/microsoft-virtual-system-migration-serviceservice-is-missing/
Also, my Active Directory is a bit of a mess so there are multiple security setup that inherited when it should not. Restore to default and unchecked inherited resolve that.
Thank you for the article!
EDIT: Just to be clear when I first started the troubleshooting I had 1 problem. After the first problem cleared I encountered with the second problem. So if you skim through the thread you may get confused very quickly.
I have been trying to configure a vSAN by StarWind with 2 node for the past weeks. With multiple guides and help from the community, still I cannot test LIVE MIGRATION. Quick Migration does works so I do not quite understand Why?
note: Quick Migration works. Force migration via restarting the server works. Live Migration failed confused
From my initial research I know the cause is probably something to do with setting or naming. Something is not identical and is causing the failure between the node. I configure the server mirroring each other from scratch and still the problem exist.
Here are some screenshots. Hopes it helps to narrow down the cause
I did not expected to get so many feedbacks. Go MangoLassi!
@Dashrender
For our environment it cost roughly 45K(it's 4.5K not 45K) to migrate all data out of our third party Exchange server. This include 5 years worth of compliance achived data.
EDIT: Just went through the quote again and it was 4.5K. wow... 45K... LOL
@scottalanmiller said:
@LAH3385 said:
They just.. don't like OWA.
At some point you have to decide what to present and not to present as options. If what they want doesn't meet their needs, take it off of the table.
Present it to management with the costs, limitations, issues, etc. Don't hold back, let them back the decision. If things corrupt, hold them accountable.
Let people move person by person. Those with OWA can mock their Luddite brethren until more switch out of embarrassment.
Do you have to manually point to Outlook file to Document or is there a general setting something I can tweak with?
@scottalanmiller said:
@dafyre said:
At my last employer, we did store the PST files in the End-User's Redirected Documents folder. To my knowledge, we never had any Outlook issues that were caused by that.
If they are small, the network is fast and the NAS never disconnects, it often works.
We are <100 users. Out network is 1Gb. We do not experience issue that often.
