|
Everyone,
Here is a little update. I finally after many months have been
able to run my first restore.
I started an 800G restore. Which is half of my 1.7TB
backup.
I ran iostat while it was restoring and was getting between 50
and 140 Meg/s. I would say the average is around 85Meg/s.
This is performing a restore to the raid-6 array. Not sure if
this information helps or hinders the issue at hand.
Thanks again for all the good suggestions.
-H
Mehma,
Sorry man wish that was the case. It was doing this on 3.0.1
and then I decided that maybe an upgrade would help.
It was doing this when the database was on the local machine.
I moved it to its own machine and it was still slow. I have also upgraded the
kernel.
I will get our db admin to restart the postgres process and
see if it makes any difference. I will try anything :)
Thanks for the suggestion.
-H
Ah HAH! The old "I just upgraded to bacula 3.03 this morning"
mistake. The problem here could be what happened to me. The database needs to be
bounced. Yes, indexes dropped and re-init-ed. It was a few moons ago and I
forget what exactly I did. Horribly slow backups and they NEVER finished
and no-one on the list could figure it out. I did the batch thing and pulled my
hair out. Until I just happen to bounce PostgreSQL db and voila everything
started working.
PLEASE BE CAREFUL:
a. I do know I re-init-ed
the indexes - I had to dump and reload the database and I re-init-ed it in the
process.
b. This is a delicate process and I played with it for many
weeks.
Mehma
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
| 