That was a typo on my part - Forgive me, I am going on about 3 hours  of
sleep.

We figured out the solution - we backup the tarballs that are currently
sitting on a windows box with a standard policy. We will be moving the
luns that are tied to that Windows box and shifting them over to be
attached to our Linux boxes.

Thanks for the help... 


Regards,

-cj
Courtenay Jones





-----Original Message-----
From: Sander [mailto:sander at humilis.net] 
Sent: Friday, February 16, 2007 1:40 PM
To: Jones, Courtenay
Cc: veritas-bu at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Windows Backups Restored to Linux Boxes

Jones, Courtenay wrote (ao):
>    But, we are going to DR here shortly, and we were hoping to just
drop
>    the tarballs directly onto LINUX boxes running ESX. I can restore
the
>    tarballs, but the restore comes up incomplete.

FWIW, ESX runs on top of the iron, not on top of Linux.

>    I see the following errors in our logs:
> 
>    08:47:16 2/16/2007: Restore Started

Do you also get errors in the backup log? Or are you sure the tarballs
get mangled during the restore?

>    When I try to untar the tarballs, I see the following errors:
> 
>    [root at sbs09932vi001 restored]# tar -zxfv sbs09932vm031_11.tgz
>    tar (child): v: Cannot open: No such file or directory

You are trying to untar file 'v' ..

>    tar (child): Error is not recoverable: exiting now
>    tar: Child returned status 2
>    tar: sbs09932vm031_11.tgz: Not found in archive

.. and extracting sbs09932vm031_11.tgz from it.

>    Does anyone have any thoughts on this?

Can you try with 'tar xf sbs09932vm031_11.tgz' ?

How big are your tarballs and the VMDK files they include? And to what
filesystem are you recovering?

        With kind regards, Sander

-- 
Humilis IT Services and Solutions
http://www.humilis.net