<div dir="ltr">Thanks Pavel. The change in the file was made by hand and it was even an error. What we have clear now is that every file involved with Apache should not be changed to avoid this errors. The only question is, what happens if we continue using Apache from the first restore and it's Apache who made the changes to the logs or to the confs? We haven't tried that but we are wondereing if it will happens the same error. <br><br>Thaks in advance.<br>Roberto.<br><br><br></div><div class="gmail_extra"><br><div class="gmail_quote">2014-11-25 13:06 GMT-06:00 Pavel Emelyanov <span dir="ltr"><<a href="mailto:xemul@parallels.com" target="_blank">xemul@parallels.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 11/25/2014 11:47 AM, Roberto Del Aguila Rivera wrote:<br>
> Thanks a lot Pavel. (I don't know if it's ok to copy this large file here).<br>
><br>
</span>> ...<br>
> (00.039488) 2001: Error (files-reg.c:820): File var/log/apache2/error.log has bad size 109 (expect 100)<br>
> (00.039560) Error (cr-restore.c:1780): Restoring FAILED.<br>
<br>
OK, here it is. The file size has changed. We have this check to try<br>
to make sure filesystem is in the same state as it used to be on dump,<br>
so that applications can continue working.<br>
<br>
Can you describe what you're trying to do with apache, why has<br>
the error.log's size has changed in such a strange way (plus<br>
9 bytes)?<br>
<br>
Thanks,<br>
Pavel<br>
<br>
</blockquote></div><br></div>