If you are doing a database backup, changing the number of forests 
shouldn't change anything.

The size of a backup is the size of the database itself; our storage 
format is already very compressed, so no additional compression can be 
done as part of the backup. The one difference is that we don't backup 
up the journal files themselves, so there is a little bit of space 
saving there.

You don't mention whether you're doing a one off backup, or a scheduled 
backup. For a scheduled backup, you configure the number of backups you 
want to retain, and need space for N+1 backups because we won't remove 
the oldest one until the current one completes.

Wayne.


On 05/31/2014 07:26 AM, Tim 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

-- 
Wayne Feick
Principal Engineer
MarkLogic Corporation
[email protected]
Phone: +1 650 655 2378
www.marklogic.com

This e-mail and any accompanying attachments are confidential. The information 
is intended solely for the use of the individual to whom it is addressed. Any 
review, disclosure, copying, distribution, or use of this e-mail communication 
by others is strictly prohibited. If you are not the intended recipient, please 
notify us immediately by returning this message to the sender and delete all 
copies. Thank you for your cooperation.

_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general

Reply via email to