HAving multiple workstations to perform tasks and different drives or partioned RAID drives for different tasks can help since the writing out, archiving and transferring on the files takes time and can really hose a machine from moving on to another task (i.e. We started with an 8 bay x 6TB Synology with 7200rpm drives and have just added a 8 bay x 10TB Synology that we are getting ready to daisy chain-and hopefully move to 10GB Network specifically to our "Download Transfer Workstation".
#SYNOLOGY CLOUD STATION DRIVE CRASHES DOWNLOAD#
We usually download the RAW scan files and sometimes will download directly to our workstation SSD and then upload later to the NAS for import to our Register 360 Projects directory on the NAS.
(I think it's pretty important ,according to other network posts on LSF, that your Cyclone/Reg 360 TEMP location folders are on a totally different drive than the project drive (we use our 2TB HDD internals for those locations) We can sometimes see slowdown when our two copies of Reg 360 are both processing different tasks at the same time (Reading, writing, cleaning,publishing, etc to the NAS.) We currently are running on a 1GB network to all workstations and work everything on NAS directly. We are working on a system similar to Jonathan, although not as fast (but we'd like to operate on the 10GB option on our Synology NAS if we can finally convince out County DTS group that our sub-network will not impact the entire county network.) Not near as much experience (started in late 2016), but trying some unique distributed mode of providing Jetstream data for Viewing and modeling in Cloudworx It will be a separate volume, but it has not been a problem for us.Īlso, don't take my word as the best advice there are many more here with more knowledge that might chime in. The nice thing about the Synology NAS for archiving is that you can daisy chain another box to give you more space. Its difficult to give you much more help without knowing how much data you have and the rate in which you accumulate it.
#SYNOLOGY CLOUD STATION DRIVE CRASHES ARCHIVE#
If I had to start over right now (serving 6) I would probably purchase an 8 Synology with 10gb network, loaded with SSDs of some sort (don't know if NVMe is supported), then another 8 bay full of large platters to back up and archive everything on. Backing up offsite can be costly, but it is recommended if your internet speed can handle it. The time it takes to get a NAS server back up and running after its motherboard dies is often too long for most project schedules to tolerate so please keep that in mind if you work at a similar pace. All our data is backed up, but we are working towards full hardware redundancy with mirrored servers. If there is one thing I have learned its is to plan for expansion and full redundancy.
we use mostly Faro Scene, but I have no reason to believe that Cyclone would have any problems. The faster and somewhat smaller(10TB) server has all but eliminated the need for large storage drives on our workstations and most projects run fairly smoothly over the network.
We use another larger (60TB) and cheaper Synology setup for archiving on large platter drives which is really just two 30TB 8 bays daisy chained. We purchased a big rack mount server a long time ago that has 15k rpm "enterprise class" drives in it served up on a 10gb network.
0 kommentar(er)
