You can find more information about backup and recovery strategies in this year's conference class AED204. Here is the presentation slides:

https://support.laserfiche.com/search/RecordClickHandler.ashx?url=https%3a%2f%2fsupport.laserfiche.com%2fGetFileRepositoryEntry.aspx%3fid%3d3192%26mode%3ddownload&sid=f424701f-7736-4d57-a4c1-a75d09f1cf42&rank=3

In particular, one advice that is particular applicable to your situation is the Two-step backup, also known as a "Disk to Disk to Tape" strategy. This strategy consists of first backing up everything from the system to a second disk-based storage (disk to disk). Once this step is complete, the Laserfiche Server can be unlocked. After that, the backup files on the second disk-based storage can be transferred to the slower tape systems (disk to tape) over the course of the next few hours.

The presentation slides contain other information pointers about reducing the downtime during backups.

Also, if your backup application has journaling capabilities, you should configure and enable journaling to speed up the file check for only backing up changed files.  This change alone could reduce your backup time to a few hours.

Hello Ryan,

Thanks for the powerpoint presentation. Is there a documents it specify how to do differential back up for laserfiche repository and database on online mode since we can't put our repository to offline mode

Hello Bert,

Thanks for the advice.

We are using Symantec backup exe, can you please elaborate on how journaling can helps us in this situation.

We have close to 300 GB of data for our LF so I am using robocopy to only upload changed/newer files to disk which later gets copied over to tape as whole. So D2D2T is the appraoch to use. The processing I am using I have documented and shared here maybe it might apply to your situation as well.

https://answers.laserfiche.com/questions/55335/Automate-Laserfiche-Backup-using-Batch-Script-without-disabling-user-access-to-repository-at-backup-stage