Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Proper Back Up workflow

Comments

4 comments

  • Rob Sackyta
    Anyone
    0
  • rap_digital
    Look at carbon copy cloner or chronosync.
    I use CCC and have a saved scheduled a incremental backup that keeps BackupA and BackupB the same and then after every shot ie. every couple hundred frames while we are setting up the next shot I run another task that does a incremental backup of LiveShootDriveA to BackupA.

    I generally dont use the "delete items that dont exist on source" option so that if I mistakenly delete a file after a backup it will stay on the backup sets, But, doning this means that your backup set will always be bigger and if you move or rename between backups you'll have the old name files and the new. Not a problem with my workflow just means I need more space and thats cheap.

    One Slightly annoying thing with CCC is if you are shooting to your operating system drive then the backup will have all the folders to the root ie. /users/shared/Jobs/todaysSession.

    Not a problem for me as I never shoot to the OS drive 😂
    -1
  • Paul Steunebrink
    [quote="Rob372" wrote:
    ...
    What about overwriting the safe drives with the new CO folder. Is that good or bad? Don't want to lose files or corrupt them.

    I don't see any harm in that.
    0
  • Rob Sackyta
    Anyone else?
    0

Post is closed for comments.