Can "backup" happen automatically ?

Ivo Sedlacek

• 2018年08月30日 04:22

It is a bit annoying when closing few catalogues that you are prompt to agree on some "backup" and then to agree with OK for each one. If there are few windows open, it becomes a bit too much. Any way to let it backup automatically without troubling you every time ?

0

• 

  SFA

  • 2018年08月30日 09:44

  Have a look in the Preferences file under the "General Settings" tab.

  0
• 

  Ivo Sedlacek

  • 2018年08月30日 12:27

  Yes, you can select how often it will ask you about "backup", from always to never. But - what is this "backup" ? Why it is not able to do it by itself in the background and it has to be done manually ?

  0
• 

  SFA

  • 2018年08月30日 12:46

  isjn wrote:
  Yes, you can select how often it will ask you about "backup", from always to never. But - what is this "backup" ? Why it is not able to do it by itself in the background and it has to be done manually ?

  
  
  It is really a question of whether you need to create a backup just because you have opened a catalogue. You may not have changed anything. You may not need a very regular backup of the catalogue changes.
  
  This is not the same as a system type backup that might be an automated part of how you run your computer(s). It is more about having the option to quickly revert to a previous catalogue state if something has gone wrong or you have accidentally mis-processed something and stepping back would be easier than correcting.
  
  Also it is useful for anyone NOT running regular, scheduled, system managed backups. (Providing they keep the files on a separate drive, etc.
  
  
  
  Grant

  0
• 

  RobiWan

  • 2018年08月30日 16:49

  SFA wrote:
  

  isjn wrote:
  
  Also it is useful for anyone NOT running regular, scheduled, system managed backups. (Providing they keep the files on a separate drive, etc.
  

  
  
  Of course you can make a backup if the database is open. It is SQL database with transaction log. After "commit" are all transactions written into Database. You won't have saved all the edits you may be doing right now. But the database is still in a constant state.

  0
• 

  Ivo Sedlacek

  • 2018年08月30日 22:57

  Does it mean that if I don't do manually the "backup" on request, all the work and changes I did before will not be saved ? What about if C1 is force quit, laptop out of power etc. ? All the previous work vanished ?

  0
• 

  SFA

  • 2018年08月31日 03:22

  isjn wrote:
  Does it mean that if I don't do manually the "backup" on request, all the work and changes I did before will not be saved ? What about if C1 is force quit, laptop out of power etc. ? All the previous work vanished ?

  
  
  No. There is no need to save edits in C1 although the Keystone tool has an "Apply" requirement due to the nature of the change.
  
  The only risk of lost data in the event of a crash is whatever the very last adjustment you were doing at the time might have been. Or a corruption of a file or the database in memory.
  
  Normally, should that happen - a very very rare event - recovery should get everything back to where it was very shortly before a failure. Othewise the quickest route back would be the last backup you had manually run on exit or the last auto backup as part of the system backup process if you run one. Whichever was the most recent.
  
  Put it this way. It's not something I feel a need to worry about.
  
  Grant

  0

投稿コメントは受け付けていません。