working on servers

[tanticapelli]

Bye to all,

in the company where I work, as I think in many, all the works I do are saved on servers in specific shared folders.

I would like to know if it is convenient to work together with all its parts, sub-axis, drawings, directly by launching the files saved on the server or if it is better to make a copy on hard drive of my location and update the package present on the server only at the end of the day.

Sorry about the paranoia but I'm afraid you're going to drop off the connection or stacking the server that can ruin my job.

if you have to make a copy on the temporary pc you could indicate a safe and fast way (also to update the server at the end of the day)?

thanks to all, as always

so many hairs

 

[MassiVonWeizen]

working on the network, apart from the risk of blocks caused by connection problems, is decidedly slower due to data transfer.
working locally is preferable.
copies of the files must be made via pack&go, taking care to use or not flattening in single folder; About this last attention that these days I noticed a single folder flattening operation in 2016 sp3 equal to that reported in this post on 2017 (which they solved with sp4.1) https://forum.solidworks.com/thread/199013

 

[cacciatorino]

Bye to all,

in the company where I work, as I think in many, all the works I do are saved on servers in specific shared folders.

I would like to know if it is convenient to work together with all its parts, sub-axis, drawings, directly by launching the files saved on the server or if it is better to make a copy on hard drive of my location and update the package present on the server only at the end of the day.

Sorry about the paranoia but I'm afraid you're going to drop off the connection or stacking the server that can ruin my job.

if you have to make a copy on the temporary pc you could indicate a safe and fast way (also to update the server at the end of the day)?

thanks to all, as always

so many hairs

If you are in different ways to access the archive, I do not see any other practical way than to work by opening the files on the server, otherwise among colleagues you would not see the updated situation of the project. then the practice of pouring projects on the server at the end of the day would be delegated to the good will of the single: Just that someone does not do it and goodbye to synchronization and especially to the daily backups of the archive.

If you have a decent network and server the time problem in uploads and saves I don't think it's real, in the face of the advantages of having a centralized archive and shared by all users. in my personal experience I have never seen any company work the way you say.

 

[tanticapelli]

If you are in different ways to access the archive, I do not see any other practical way than to work by opening the files on the server, otherwise among colleagues you would not see the updated situation of the project. then the practice of pouring projects on the server at the end of the day would be delegated to the good will of the single: Just that someone does not do it and goodbye to synchronization and especially to the daily backups of the archive.

If you have a decent network and server the time problem in uploads and saves I don't think it's real, in the face of the advantages of having a centralized archive and shared by all users. in my personal experience I have never seen any company work the way you say.

I only work

 

[re_solidworks]

if you work there only you can work locally and you can implement a serious backup strategy to have the data always updated, preferably with copies that remain for at least 2 weeks. you can also do it with cobian backup (free). If you do not want to have copies that allow you to return to the previous days you can also use the robocopy command of windows to sync the archive. In this case you can also make a batch file that at the end of the day starts alone, syncs the archive and then turns off the pc. It would be good to have a copy not accessible from the local pc, if you take a cryptolocker in this way save the data, if the copy is always accessible they are encrypted too. it would not be bad to have the local disk in raid 1 or raid 5 to prevent the loss of local data in case of a disk failure.

 

[New Rider]

working on the network, apart from the risk of blocks caused by connection problems, is decidedly slower due to data transfer.
working locally is preferable.
copies of the files must be made via pack&go, taking care to use or not flattening in single folder; About this last attention that these days I noticed a single folder flattening operation in 2016 sp3 equal to that reported in this post on 2017 (which they solved with sp4.1) https://forum.solidworks.com/thread/199013

if you work there only you can work locally and you can implement a serious backup strategy to have the data always updated, preferably with copies that remain for at least 2 weeks. you can also do it with cobian backup (free). If you do not want to have copies that allow you to return to the previous days you can also use the robocopy command of windows to sync the archive. In this case you can also make a batch file that at the end of the day starts alone, syncs the archive and then turns off the pc. It would be good to have a copy not accessible from the local pc, if you take a cryptolocker in this way save the data, if the copy is always accessible they are encrypted too. it would not be bad to have the local disk in raid 1 or raid 5 to prevent the loss of local data in case of a disk failure.

I'll join this discussion.
currently where I work being the only, I work on local. every noon leaves a back-up on the dedicated server of the folder where all files are stored.
in case the local disk burns, so I have all the files on the server. when I go to restore everything I lose all links?

 

[re_solidworks]

I'll join this discussion.
currently where I work being the only, I work on local. every noon leaves a back-up on the dedicated server of the folder where all files are stored.
in case the local disk burns, so I have all the files on the server. when I go to restore everything I lose all links?

If you keep the paths equal, no, nothing happens.