Install everything locally vs. over network

[brrian]

Our server died today. It's where we keep all of our project files, as well as our SolidWorks templates, toolbox database, etc.

All the files are backed up, so it's not too big of a deal to get the project files. However, since all of the files that SW references are on the network, SW doesn't work properly (I can't see my templates, the Hole Wizard doesn't work, etc.).

I wonder if a better option might be to install SolidWorks so that everything is local to each users' hard drive, then maintain those files/folders with periodic updates to ensure everybody is working with the same information. For example, if I update a template on the network, everybody sees the new template immediately, since they're all linked to it. If templates were stored locally, I'd have to 'batch' update everybody's folder to get them the new template.

The benefit is simply that if the server goes down (as it has today), SolidWorks still functions properly.

Any comments? Does anybody work like this? Pros and cons? I look forward to your responses. Thanks,

Brian

 

[J-C]

That's the way we did it. I created a batch file to copy the templates, data files, etc. to a local read-only folder. This was mostly for laptop users so they could use swx offline. I then setup everyone that way so they could at least work on something if the server was down for whatever reason.

There is also the option to use "Offline Folders" which I haven't got around to looking into yet. Basically it caches specified folder locally. You still see the network and thoses specific folders even unplugged. When you reconnect it resyncs the files.

Jason

 

[waynewalker]

Brian & Jason,
Is either of these configurations you describe useing PDM Works and a Network Toolbox?
If not, can they work with PDM & a common Toolbox?

We have separate servers for Licenses, Files, Vault and Toolbox.

The only time we have an outage is when the License server won't manage licenses and I or the other IT guys are not available to manually restart it.

Many thanks,
Wayne

Wayne Walker
Information Systems Administrator
Photonics Division
General Atomics
858-457-8784

 

[brrian]

No PDMWorks, and toolbox is on the network, but we don't use it.

 

[J-C]

PDM/Works downloads files you're working on locally so it's not a problem. If you are using a shared toolbox on the network, the only problem with using offline folders is the Access database. I've heard that it doesn't sync well if at all. Especially problematic if everyone has write access to the database. I think the only the way to possible handle this is to give no one write access to toolbox which means no one can add new toolbox part sizes except for an administrator(s).

Still, this would require testing to make sure it will work.

The file references to the toolbox part files should work fine with offline folders.

Jason

 

[waynewalker]

Thanks Jason,

The key to using a shared toolbox appears to be setting the parts files as well as the folders to Read Only for users, and let SW change to Write when new sizes are added. I'm still in research on this for a Linuus File server, not as easy as for a Windows file server.

Wayne

 

[phreaq]

here's my 2 cents.

keep everything on the server, its WAY easier to maintain one set of files as opposed to dozens. Need a new profile/template/whatever? everybody has it instantly!

now, to fix the downed server side of things. you could always use offline files on the clients. if the server isn't there for whatever reason, the offline files take over, and the user won't even notice (aside from the offline file notifier, which can be turned off).

I have notebook and am constantly away from the office, so the offline file method is perfect for me. slight overkill in an office environment, but it'll be the best of both worlds