Hello @tous
Rather than directly saving my work on a limited speed SSD, I would like to save the work on the faster M2 (system), and that once saved, the files are automatically copied in the background to a folder on the SSD.
Ideally, copy only the modified files, in order to spare the SSDs.
Do you know of one or more methods to achieve this? Thank you.
Hi @Sylk
Can be with a file of type .BAT
with this command
xcopy d:"directoryAA" c:"destination\directoryBB"
But not sure you can do it automatically
Hi @Centor thank you for your answer.
This command may be viable for regular backups, less so for real-time backups, in which case it would take longer than writing to the SSD.
Finally, my idea is that the risk of data loss is inversely proportional to the speed of writing; the faster SW saves the work, the less time it leaves it to crash before the file is closed. And there is no shortage of reasons for SW to plant at this time...
Fast writing for recording security and instant resumption of work. Immediately followed by a copy (slower but without impact on performance) in the background for backup; If there is a problem with the next save, the copy will be up to date (last successful save).
So a batch could be a recourse, albeit tedious, if it meets at least certain criteria.
If there was a built-in option in SW, or native Windows 10, it would be better.