Link to home
Start Free TrialLog in
Avatar of Michael McGuire
Michael McGuireFlag for United States of America

asked on

VMware setting for Server 2022 File Server

I need a recommendation on VMware ESXi 7.0 settings for a Server 2022 Datacenter VM.  The VM will be used for a File Server.  We have about 50 users in our domain.  Need to figure out what CPU & Cores per Socket to use.  Also, How much RAM to use.  It's is going to have a C & D partition.  C for O/S and D for Files.  I just don't want to set it too high, I know I can always adjust this in the VM setting later.  

ASKER CERTIFIED SOLUTION
Avatar of Lee W, MVP
Lee W, MVP
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Michael McGuire

ASKER

Sorry I stated that wrong.  The C & D disks are not partitioned, they are separate Virtual Disks.  
Yes, this will only be a File Server.  I may possible setup replication to another server for availability (not sure if that will affect the CPU &^ RAM), but this is definitely only going to be used as a FIle Server.  

Replication should not impact the guest resources.  Just keep in mind replication is disaster recovery, not availability.  Availability is a cluster where the VM moves between hosts automatically if a host goes offline.  Typically, at worst, a blip in connectivity occurs.  Replication would allow recovery if the main host failed, but tends to be more complicated to start and move the VM, so you don't do it just because you need to patch the host.  (at least in the Microsoft world).


If you want high availability, consider a cluster or possibly DFS.  There's also storage replica since you're using Datacenter.


This VM will already be part of a 3 Host Cluster.  All VM's are Stored on a Storage Array, so in that sense it will still run if one of the Host go down.  I was thinking of replication just as an additional point in case the Storage Array ever went down.  

Make sure the Windows Search Service is enabled and then set up via Indexing Options.


Make sure File Server Resource Manager is set up.


I suggest 4 vCPUs and 8GB vRAM if the file repository is over 500GB to 750GB and the users are fairly active on the file share(s).


Access-based Enumeration is a great feature too.

Thanks for the advice! I will move forward with this VM.

Setting up a DFS Namespace and the DFS Replication between the clustered VM and a secondary VM off the cluster would work pretty good. There are some issues with DFS-R around file locks which means the loss of the primary may mean some files are not up to date.


How things are backed up becomes a key in this.