Database Backup best practices -

i working in production environment, process xml files daily. our database size quite big. taking daily backup. learned marklogic adds changes previous backup create new backup.

i wanted confirm best way keep daily backup or there other better way it. there limit process, following. database size around 350 gb , increasing daily. looking faster , easier solution.

this question open-ended: there no single "best way". marklogic supports full online backups, , journal archiving continuous incremental backup. docs @ http://docs.marklogic.com/guide/admin/backup_restore discuss these options.

instead of full daily backup, might consider full weekly backup plus journal archiving. start new week, can whatever data previous week: retain it, delete it, move onto cheaper storage, etc.

as marklogic databases go, 350-gb not large. @ point should have configured multiple forests: see http://docs.marklogic.com/guide/cluster/scalability#id_96443 guidelines. assuming have multiple cpu cores, storing content in proportional number of forests improve performance throughout system. includes backup, because multiple forests in parallel - though of course disk may still bottleneck. if storage bottleneck, separating i/o forests , backup advisable.

if having multiple forests new idea, might interested in https://github.com/mblakele/task-rebalancer