Are these files too large to backup?

[cglaser]

Hey All,
I have been getting error code 1 on a certain policy. Here are the files that have been showing up in the problems report for this client.

-rw-r--r-- 1 dmacdon msr 3209367133 Apr 10 19:45 cslSamLS.dat.R0000191.X094.seca.Z
-rwxrwx--- 1 dmacdon msr 3859303503 Apr 10 17:36 cslSamLS.dat.R0000191.X104.secd.Z
-rwxrwx--- 1 dmacdon msr 3710531013 Apr 10 17:48 cslSamLS.dat.R0000191.X105.secc.Z
-rw-r--r-- 1 dmacdon msr 2887027001 Apr 10 20:12 cslSamLS.dat.R0000191.X126.sech.Z
-rwxrwx--- 1 dmacdon msr 3357038831 Apr 10 18:05 cslSamLS.dat.R0000191.X148.secg.Z
-rwxrwx--- 1 dmacdon msr 3309159875 Apr 10 18:16 cslSamLS.dat.R0000191.X190.sece.Z
-rwxrwx--- 1 dmacdon msr 3170809697 Apr 10 18:27 cslSamLS.dat.R0000191.X226.secf.Z
-rwxrwx--- 1 dmacdon msr 3771987776 Apr 10 18:42 cslSamLS.dat.R0000191.X628.secb.gz
-rw-r--r-- 1 dmacdon msr 3662845650 Apr 10 20:01 cslSamLS.dat.R0000191.X628.secb.Z

Are these files too large to be backed up? Do you know if you can set this value to be something larger somewhere? Here is the output of the problems log.

2:09:57 PM from client pvllinsrv00: ERR - Cannot lstat etl/fulfillment.main.003.040604.tar. Errno = 75: Value too large for defined data type bpbrm
2:09:57 PM from client pvllinsrv00: ERR - Cannot lstat terms/cslSamLS.dat.R0000191.X094.seca.Z. Errno = 75: Value too large for defined data type bpbrm
2:09:58 PM from client pvllinsrv00: ERR - Cannot lstat terms/cslSamLS.dat.R0000191.X104.secd.Z. Errno = 75: Value too large for defined data type bpbrm
2:09:58 PM from client pvllinsrv00: ERR - Cannot lstat terms/cslSamLS.dat.R0000191.X105.secc.Z. Errno = 75: Value too large for defined data type bpbrm
2:09:59 PM from client pvllinsrv00: ERR - Cannot lstat terms/cslSamLS.dat.R0000191.X126.sech.Z. Errno = 75: Value too large for defined data type bpbrm
2:09:59 PM from client pvllinsrv00: ERR - Cannot lstat terms/cslSamLS.dat.R0000191.X148.secg.Z. Errno = 75: Value too large for defined data type bpbrm

can anyone help me out?

Thanks in Advance,
Chris

 

[PGPhantom]

What O/S - What version of Veritas?

 

[cglaser]

sorry about that, here is some more info about our Netbackup environment:
Master: NBU 4.5 MP5 AIX4.3.3
Client: Red Hat Advanced Server 2.1
Media Manager: Solaris 5.8

any other info you need - let me know. Thanks Phantom!
Chris

 

[rugby01]

4.5 MP5 will not support streams of files/file systems larger then 1 T. You can back them up - but it will not recovery them. I believe FP6 fixes the 1T issues - and I know 5.0 allows > 1 T files.

You may need to cut these up into multiple files and arcross directories. Then start one stream per directory.

 

[TAW]

Which system(s) have to be FP6 master/media and client or just the master/media server?

 

[cglaser]

thanks to all that responded!
because it was a hot issue to get these files on to tape, we ended moving these large files over to a solaris box and that cleared up the issue. apparently, the issue lied with linux and the structure of the filesystems...here is the response from Veritas support:
Either the user ID or the group ID of an IPC object or file system object was too large to be stored in an appropriate member of the caller-provided structure. This error occurs only on systems that support a larger range of user or group ID values than a declared member structure can support. This condition usually occurs because the IPC, or file system object, resides on a remote machine with a larger value of type "uid_t", "off_t", or "gid_t" than that of the local system. The symbolic name for this error is EOVERFLOW, errno = 79.
A common cause of this error is a corrupted binary on the client. The recommended action is to delete the client and push the correct client binaries out to this client.


Again, thanks so much to those that responded...

 

[tocco]

Try changing your OTM file size to 0 or another size