Robert Calkin 

Two rules from my point of view:

• Never ever store ANY production files on c:
• Never use any cloud storage for Trados Studio files

Using cloud will cause you huge synchronization problems. The solution is to store TMs and TBs in a path common to all your computers. Then synchronize this folder with the cloud using some software and automated synchronization once a day or once an hour. What I mean is a local folder OUTSIDE the cloud, which would be synchronized with its copy WITHIN the cloud. This will help you avoiding duplicate files and other issues. Same applies to your project files, however the path to these is not that critical, if you're changing computers, because only the TM and TB paths are absolute paths. All paths withing a project are relative and thus a project can be moved everywhere and will still work, provide the absolute paths to the TM and TB configured in that project remain exactly the same.

Jerzy Czopik 

How exactly (software) do you backup your files to cloud storage?

NB: Might be worth pointing out at this point that MultiTerm does not cope with network drives, don't know for sure about Trados Studio, but I would also avoid network drives for that. It leads erratic bahaviour that is hard to track down.

Daniel

Unknown said:

How exactly (software) do you backup your files to cloud storage?

Previously the software used was Allway Sync, which has now been bought by GoodSync. The usage is a bit different and also the pricing differs, but there are many other solution for this, so in the end of the day the name of the software does not matter much.

What I do is synchronizing my files with the pCloud when my PC starts. This can be setup easily in the synchronization software.

TMs and TBs are stored all locally on a NVMe SSD, but are also synchronized daily at 8 pm to a NAS. All other files including project files for Trados Studio and memoQ are stored on a NAS. This NAS synchronizes all business data live (RTRR) to another NAS. This one uses Rsync to synchronize data wit the next NAS at 2:00 am. The other NAS synchronizes its data via Rsync with the last NAS at 0:00 am.

Hi Daniel, Many thanks for flagging up the risks with this. I am concerned about potential loss of files and data with any backups. Rob

Robert Calkin said:

Hi Daniel, Many thanks for flagging up the risks with this. I am concerned about potential loss of files and data with any backups. Rob

Do I understand correctly? You are concerned, that backups may cause data loss? But this is completely the other way round. A proper backup is run daily and you also need a regular backup (weekly, monthly) on an external drive, which must be disconnected from the PC after securing data.

If you look on my description above, the data backuped with the method above can be restored back to 48 hours. And the probability of loosing data is very low. My main data is stored on 4 HDDs at the same time! How probable is it, that all four will die at the same time? And further to this the data goes on 3 more HDDs. On top of this the data is kept on an external SSD, updated more or less monthly. The TMs/TBs are stored locally in my PC, so these are on 8 HDDs alltogether. On top of this TMs and TBs are synchronized to pCloud on every PC start...

Hi Jerzy, Thanks for your help and descriptions. Rob

Hallo Jerzy Czopik 

The English-speaking people are different from us and they have no such thing as 0.00am, sondern 12.00am.

And... I am impressed by your storage hardware and programming.

Serdecznie pozdrawiam.

Gérard

Gérard LAMBERT 

Gérard LAMBERT said:

The English-speaking people are different from us and they have no such thing as 0.00am, sondern 12.00am.

I wouldn't say that... 0:00am typically refers to midnight in English-speaking countries, which is equivalent to 12:00am if you don't use a 24-hr clock, or simply "midnight". But it is definitely a source of confusion.  I think most people would use "midnight" or 0000hrs... at least most people in my circle of English speakers where I've even used this time.  Although funnily enough I even think this is technically incorrect as it should probably be 00:00, 0000 hours or 0000H.

It's a funny old world!

Gérard LAMBERT 

Thank you for clarifying the times for me. I must admit, that I should have known that, but obviously forgotten

The good part about my hardware is, that I did not need any programming for that. Just a simple setup using apps provided by QNAP, the bran of all my NAS. And even if the necessity of backups was obvious to me far before having NAS, the concept has been born with ISO 17100 and my certification, when I needed to make files available to my revisor (at home) even if my PC was not running. The first NAS came 2011, the second shortly after that one and was already the backup soultion. And when I bought a better NAS, the row has moved and the previous working one became backup 1, the backup one was then backup 2...

Gérard LAMBERT 

Thank you for clarifying the times for me. I must admit, that I should have known that, but obviously forgotten

The good part about my hardware is, that I did not need any programming for that. Just a simple setup using apps provided by QNAP, the bran of all my NAS. And even if the necessity of backups was obvious to me far before having NAS, the concept has been born with ISO 17100 and my certification, when I needed to make files available to my revisor (at home) even if my PC was not running. The first NAS came 2011, the second shortly after that one and was already the backup soultion. And when I bought a better NAS, the row has moved and the previous working one became backup 1, the backup one was then backup 2...