The ARCHICAD BIM Server has a very useful built-in backup function, if configured correctly. Find below some considerations regarding a proper backup strategy.
1. On Mac OS X we find that people tend to choose Apple’s TimeMachine as their preferred backup option. Although this is a perfect solution for your regular desktop, this is problematic on a server level as it is not easy to control, e.g. the time it runs or what to include or exclude – we use the excellent Carbon Copy Cloner (CCC) instead;
2. We typically adjust CCC to backup after hours, with a preflight script to stop and post flight script to start the ARCHICAD BIM Server;
3. We also adjust the BIM Server backup settings to typically only do PLN backups, to ensure that in case of catastrophic failure, you at least have PLNs that you can use temporarily without a BIM Server (unless you have a few spare BIM Servers flying around)… note PLN backups are typically bigger in size than BIMSERVER backups;
4. We also choose to run backups after hours (not all at once at 1600h – not sure how Graphisoft determined that that might be good time to have all TW projects backup at the same time…);
5. Depending on your BIM Servers capacity and the number / size of your typical project files, carefully monitor that you do not run out of space (and risk corruption of the bimservers mongo database) – unfortunately there is no way to globally adjust the default backup settings easily, i.e. it is a manual process that requires regular checking to ensure that nobody has shared a few 4GB files with the default backup settings;
6. Offsite backups are essential but depend on your willingness to rotate backup drives / tapes offsite (we do it daily) or your internet connection bandwidth for cloud based backups. Do think twice about cloud backups though, although convenient restoration / download times for several GB of BIM Server data might be prohibitive (we only do tapes and hard drives to avoid massive downtime);
One last thing to keep in mind regarding the frequency of BIM Server backups:
If your practice works in large teams and you need to restore or roll back a project file (e.g. if a single user gets detached), we find that hourly backups are not really that useful, as you typically loose as many man hours as there are team members if you reset the project for the whole team (rather than just forfeiting a single users work for the last couple of hours).