A non-incremental backup will be almost exactly the same size as the original forest(s). For the most part forests aren't compressible, and the backup doesn't try. To see how this works, take a look at the filesystem layout of the backup and the original forest(s).
I'm not sure where concurrency comes into this: you say you're only using one forest? -- Mike On 31 May 2014, at 07:26 , Tim <[email protected]> wrote: > Hi Folks, > > I have question about backups. We have a fairly large database (which is > currently using only one forest) and are running out of space when performing > backups. I do not understand the backup process very well and I don't know if > it is just a matter of running out of space or if it has to do with performing > concurrent backups and the size of any given forest that is being backed up. > Could splitting the database up into multiple smaller forests fix the problem? > > The error log merely tells me that there is insufficient space available, but > I > don't know how to measure that - in other words is there a rule for calculate > the necessary disk space based on the database size and any degree of > compression? Is it impacted by concurrent backups? > > Thanks for any help with this! > > Tim Meagher > > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general > _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
