Patching Microsoft Storage Server 2012 R2 - VMware storage on a NAS

Hi,
We just purchased an AberNAS NAS device which runs on Windows Storage Server 2012 R2.  I'm trying to figure out the best use case for it since applying Windows patches it will cause downtime.  We were going to use it as an NFS datastore in our VMware environment, and move archive data to it.  Then we realized that any VM which uses it will suffer an outage when we patch and reboot the OS that runs it.

Any suggestions on how to make it available  in a cluster or something which will give us availability during patching?

Thanks!
svillardiAsked:
Who is Participating?
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes just create shares on the NAS and move Archive data to it

No need for VMs
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Any suggestions on how to make it available  in a cluster or something which will give us availability during patching?

Not without additional third party software, I'm afraid you are stuck with Windows OS limitations
0
 
andyalderCommented:
WSS Standard can be clustered, but you would need to buy another one of course to cluster it with.
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
if it's only archive data, why would this matter restarting it ?

it means the Archive Data will not be available during the reboot ?

how often do you need access to Archive Data ?
0
 
svillardiAuthor Commented:
The idea was to create volumes and present them to VMware in chunks as needed.  500 GB here, 2 TB there, etc.  When a VM has a drive used only for archiving, migrate the drive to the new, cheaper storage in this NAS.

Then, we started thinking, how will these datastores react during a reboot of the storage server/NAS?  My guess is that VMware won't be too happy about this.

And, we were also thinking, if I have 20-30 volumes (an arbitrary number as an example), presented as datastores, eventually, I may not be able to schedule a reboot of the NAS without affecting the ability to write to the archive drive during the reboot.

Looking for ideas.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
So what you mean is a VM used for Archive!

Why not just move data Archive to a Windows Native share on the NAS
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
NFS datastores are okay to reboot. If nothing mounted

But VM disks in USE - not really!
0
 
svillardiAuthor Commented:
The VMs are not archive VMs, they are application servers which purge to archive drives.

Let's say I was able to figure out a schedule where no servers were actively writing to their archive drives?  What would be the process to safely reboot the WSS without adversely affecting the environment?  Would I just have to shut down the VM accessing the WSS?  Would I have to do something in VMware first?

Would it make sense just to map a drive to the share on the WSS instead?
0
 
svillardiAuthor Commented:
Is that what you mean by a Windows Native share?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.