Re: [cobalt-users] Disaster recovery

[metalwolf@xxxxxxxxxxxxx]

Hi.
About disaster recovery, I have now a problem on my cobalt 
3:

It reboot on friday. (I still dont know why)
The cobalt reboots well, but checking my /dev/hda4,
it found a huge file (I think it's a 300Megs file) with 
duplicate blocks.
Everything seems normal, pass in force check mode... 
and then , first DISPLAY the 300,000 bad blocks (which 
takes about 2.5 hours !!!)
and at the end just do nothing more ?!?!?!

Is that because the file is to big to be repaired ? e2fsck 
doesnt support so much repair ?  another tip ?

What can I do ?
How do I force the raq3 to run in level single to try to 
maintain manually the hda4 ? any other way to repair the 
disk or force to be mounted and then repair the file ? 
I critically need my raq mounted...

Any suggestion welcome.

MasterPhil  


> I was thinking of making a tar backup as someone 
suggested on the list a
> little while ago. Has anyone tested full restores using 
this type of method?
> I was wondering if it is best to tar specific areas 
separately and restore
> them in a certain order or just tar the whole thing as a 
disaster recovery
> proc. I am unsure of what I should do for disaster 
recovery as I'm bringing
> my first Cobalt appliance online soon. I am investing 
into a 2nd RaQ3 that
> will be used solely for disaster recovery. My plan is to 
make tar files of
> the whole active machine and have the 2nd one waiting 
with a fresh OS
> Restore loaded. Maybe test it each month.
> 
> If anyone has tried this type of disaster recovery, I 
would appreciate some
> insight. I was also wondering how much I can rely on the 
RaQ backup (.raq),
> or should I just do it all using tar. Once backed up 
using tar, the plan it
> to ftp it off to another machine.
> 
> Thanks,
> 
> Robert
> 
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users
> 


---------------------------------------------
This message was sent using Endymion MailMan.
http://www.endymion.com/products/mailman/