Those limitations exist with every other file-based backup solution. Of course you should test a recovery from time to time ;)
On August 9, 2023 5:19:09 PM GMT+02:00, Les Mikesell <lesmikes...@gmail.com> wrote: >On Wed, Aug 9, 2023 at 8:42 AM Wächtler, Jan <jan.waecht...@amasol.de> >wrote: > >> The Overview description of backuppc states that it is a >> >> “ .. system for backing up Unix, Linux, WinXX, and MacOSX PCs, desktops >> and laptops …” >> >> >> >> Is there any reason why this list does not include Server systems? >> >> I am using it for years now to backup (web/application/database)-server >> data and configuration, is there any reason why I should not do so? >> >> >> >Databases can be a problem because they update all the time so you may not >get a consistent snapshot unless you use the tool specific to the database >to perform a consistent dump to a file, then let backuppc back that up. >Similarly with active windows machines you may need to use tricks to make a >shadow filesystem copy to get files that would be locked. Other than that, >the only issue is that it won't do a bare metal restore, so you have to be >prepared to do an OS and app install or use another approach to get to a >point where backuppc can put the files back. If instead, you just want to >grab an old copy of a file or directory lost or corrupted by mistake, >backuppc is better than most at that. Of course in a production system >you should really have a formal version control system and deployment >process to fix that sort of thing. > >-- > Les Mikesell > lesmikes...@gmail.com
_______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
