Need details on what server works best.

[JBEDsol]

I've recently been asked to get details on a server for the 3D work in my office.  Problem is I'm completely in the dark as to what's needed.  Right now a file w/ about 5000 parts takes 20min to load from the server we're using.  This simply can't continue and we may need to buy/setup a new server, find ways to use the existing servers that aren't currently being used etc.   I don't use vault right now but plan to eventually use vault w/ FDS, Content Center, Frame Generator, etc.  I'm stabbing in the dark and wonder if anyone has some advice on what might be needed or helpful. 

[Frederick_Law]

Switch to Vault and problem solved.

Opening/saving files on Window network is always slow.  You need a really good IT, Windows network Pro to get it running smooth.

Vault remove this because it copy files to local computers.

[JBEDsol]

I suppose I just need to rip off the bandaid and dive into vault. 

So our IT knows less than I do about vault.  So what do I need to tell him in terms of needs, like do we need a designated server or use our current servers?  Does speed matter?  Do certain servers work better than others for vault? 

[Frederick_Law]

You can test Vault on current server.

I think it works on non-server Windows OS.

I think Vault Basic come with Inventor.

I think Vault work best with single Project.

Check Vault hardware, OS requirements.

[Mark.Lancaster]

@JBEDsol 

If you are seriously thinking about the Vault path then you should start inquiring with those in the Vault forum and not through the Inventor forum

https://forums.autodesk.com/t5/vault-forum/bd-p/101

The hardware is going to depend on what your goals are and how you are going to manage the data.   Yes Vault basic can be run on a Windows/PC operating system but even if under a server OS, its not designed for groups of 5 or more concurrent users of Vault.   If you are seriously you should find a local reseller in your area and let them point you in the right direction or provide that information.

[swalton]

Our Vault setup:

1. Windows Server 2016 running on a Virtual Machine (VMWare ESXI).  
   1. Microsoft SQL (not sure the version)
   2. 10 GB Ram
   3. 500 GB harddrive space for the Vault Filestore and Databases
   4. 2 cores of the host server assigned to this VM
2. Vault Professional.
   1. We use it for site to site replication, not for any of the lifecycle workflows
   2. Local site has 1-2 users
   3. Remote site had 10-15 users.
      1. I don't know the remote site server hardware specifications.  OS and SQL are the same, down to the update/patch level. 

You may want to take a look at the Vault forum or contact your reseller for more information.  

[mcgyvr]

If you are a single user and have no plans to change that anytime soon then I recommend skipping Vault (unless you want its revision control functionality) and just storing all of your cad data on your local computer and using a nightly backup to the server to store data there for disaster recovery should your PC crap out..

I did that for years and the performance is far better than a single user working over the network..

We used robocopy to just do a nightly backup from my hard drive to the server and never had a problem..

I could run the robocopy job manually if I ever needed to sync files before I went home for the day..

Vault ain't cheap and requires extra steps/management,etc... 

[JBEDsol]

Thank you, this is exactly the kind of stuff I need.  Few questions,

site to site replication vs lifecycle workflow???  What is that? 

Local site vs remote?  I'm not sure what you mean.  Does that mean there's 10-15 people using the server and 1-2 people using the individual computers?  We plan to have around 20+ people working off vault but currently only have about 3-4.  Each person will access via their own dedicated computer.

We'll be using vault basic for the time being.  I can't really justify spending on vault pro until I at least cut my teeth on basic.  Not sure if that changes any of your advice.

[swalton]

Glad to help:

You might review the About Vault section of the Vault Online Help file here: http://help.autodesk.com/view/VAULT/2019/ENU/?guid=GUID-87D9CA09-9881-4506-9465-0677392BCD7E

Site -to-Site replication: 

We have two offices, about 60 miles apart.  We use full replication between two Vault Servers so that each site has a full copy of the filestore (all the CAD files and other things stored in Vault) and the databases (Vault's records of all the activities done by users to those files, and other information).  This gives us the best performance when sharing CAD data between the two offices.  Vault automatically manages keeping the two sites in sync.  This requires Vault Professional.

Lifecycle States:

Vault users may set up Lifecycle States that track the progression of a file from Concept, Prototype, Released, Under Review, and Obsolete.  The intent is to capture the document control/revision steps that are used by the company through the design and manufacturing process.  Users are free to create their own states and progression.  Each of these states can have different security requirements to control which users can read, edit, and delete the various files.  There is a Job Processor that can be triggered on state changes to create viewable or manufacturing files.  Lifecycle state changes can require approval by others.  All changes are tracked by Vault.  Lifecycle States require any of the paid Vault versions.

Local vs Remote:

I was discussing our particular setup with two offices working from the same Vault data at the same time.  My office has 1-2 people using Vault (on a server machine in my office) and Inventor (installed on individual workstations, working on data copied from the Vault server to each C: drive).  The remote site, about 60 miles away, has 10-15 people using Vault (on a server machine in their office) and Inventor on each of their workstations.  This may not be required in your situation.

Vault Basic is a good place to start.  I would hire the local reseller to help you develop your implementation plan.  The goal would be to avoid common missteps that can make it harder to move to the paid Vaults in the future.

If you want to control and capture Revisions and Lifecycle States, you will need Vault Workgroup or Professional.  Vault Pro is also required if you want to link the Vault data with an external ERP system.