thanks for your help and input.
I don't think the controller was/is causing the corruption. The problem
stems from my initial configuration of the storage and volumes causing
the disks to fill up. In order to hopefully not loose any backup data I
moved some of the volumes to another disk
On Wed, May 11, 2011 at 02:06:44PM -0700, Jerry Lowry wrote:
another mistake on my part. You have to give bls the correct spelling
of the volume ( sometimes I wonder )
Once I corrected the volume name this is the results I get:
Volume Record: File:blk=0: 206 Sessid=16 SessTime=1303843290
thanks for the help. Looks like I have some digging to do to figure out
what is actually happening. I know that I one time I had some problems
with the raid controller. I have since gotten that resolved.
If the volume has been recycled will the corruption remain with the
volume or will it
Is there anyone that can help me with this problem? Surely someone is
using the migration job.
On 5/9/2011 2:51 PM, jerry lowry wrote:
Hi,
I am frequently getting errors on my migration jobs and I need some
help trying to figure out what the problem is.
I have three migration jobs that
On Wed, May 11, 2011 at 08:44:18AM -0700, Jerry Lowry wrote:
Is there anyone that can help me with this problem? Surely someone is
using the migration job.
I'm not using migration jobs, but maybe I can give you a hint...
On 5/9/2011 2:51 PM, jerry lowry wrote:
09-May 13:59 distress-sd-sd
I have not tried to restore from that particular job as yet, but the
next question would be, if it fails on the restore that would mean that
anything backed up in that job would not be valid, correct?
thanks
On 5/11/2011 8:54 AM, Graham Keeling wrote:
On Wed, May 11, 2011 at 08:44:18AM
On Wed, May 11, 2011 at 09:19:49AM -0700, Jerry Lowry wrote:
I have not tried to restore from that particular job as yet, but the
next question would be, if it fails on the restore that would mean that
anything backed up in that job would not be valid, correct?
I think that depends upon
Ok, I am trying to run bls on the specified volume file that is
associated with this job. But the problem I am having is that bls is
failing trying to stat the device.
I have one director and two storage directors. The volume I am trying
to run against is on the second SD. Do I run bls on
Sorry, forgot to add this..
When I run bls on the second SD it asks me to mount the volume on the
device specified. But when I go to the director and try to mount the
device is says that it is always mounted due to the device being a disk.
bls -j -V Home-0006 /Home
this uses the
On 05/11/11 13:48, Jerry Lowry wrote:
Ok, I am trying to run bls on the specified volume file that is
associated with this job. But the problem I am having is that bls is
failing trying to stat the device.
I have one director and two storage directors. The volume I am trying
to run
Hi,
No, the migration job is occurring on the same storage daemon. This
storage daemon has 6 raid devices setup as jbod, 3 are for daily use and
3 are setup as hotswap devices for off-site backups. The problem is
when I run bls on the storage daemon where the disks are located I get a
another mistake on my part. You have to give bls the correct spelling
of the volume ( sometimes I wonder )
Once I corrected the volume name this is the results I get:
Volume Record: File:blk=0: 206 Sessid=16 SessTime=1303843290 Jobid=3
DataLen=171
11-May 13:42 bls JobId 0: Error:
Hi,
I am frequently getting errors on my migration jobs and I need some help
trying to figure out what the problem is.
I have three migration jobs that migrate data from a daily disk to a
raid disk that is setup as a hotswap disk. Once this is full I pull the
disk and move it to an offsite
13 matches
Mail list logo
