[Veritas-bu] need NetBackup experts. Michigan

2008-01-08 Thread barratt-mccartney
We're in search of NBU experts and Sr level Administrators to join our 
growing NetBackup consulting team.

You must be able to design and deploy complex NetBackup solutions. If 
you have stellar skills with high end storage and tape solutions 
(IBM/EMC/Hitachi) or Symatec EVault that would be beneficial. The 
offered positions will be very technically rewarding for the right 
candidate.

You must be able to work in the US, Canadian citizens are fine. There is 
a minimal amount of local travel (25%). We are not a body shop, we are 
not staffing to fill temporary hourly contracts.

this is a direct hire, salaried position


Susan Damron Horan
Senior Technical Recruiter
email:[EMAIL PROTECTED]
Compsat Technology Inc.
25330 Telegraph Road, Suite 200
Southfield, MI 48034
Fax: (248) 223-1026 - Attn: S. Horan

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] NetBackup 6.5 and holding Jobs

2008-01-08 Thread Nardello, John
http://seer.entsupport.symantec.com/docs/278938.htm
 
And no, "nbpemreq -suspend_scheduling" does not carry over across daemon
bounces or reboots. If you want to not have jobs trigger immediately
after those actions, you'll need to either disable your NB startup
script or be really quick with another suspend command. 
 
- John Nardello



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Holowinski, Scott
Sent: Tuesday, January 08, 2008 2:26 PM
To: Len Boyle; veritas-bu@mailman.eng.auburn.edu
Cc: Kevin Whittaker
Subject: Re: [Veritas-bu] NetBackup 6.5 and holding Jobs



Len,

 

That doesn't appear to be a documented command line switch.  So how do
you turn scheduling back on after using it?

 

Thanks,

 

Scott 



From: Len Boyle [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, January 08, 2008 9:32 AM
To: Kevin Whittaker; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] NetBackup 6.5 and holding Jobs

 

Kevin, 

 

Try the command

 

nbpemreq -suspend_scheduling

 

len

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kevin
Whittaker
Sent: Tuesday, January 08, 2008 10:59 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] NetBackup 6.5 and holding Jobs

 

Ok, when I was on 5.1 I could change the behavior file to # of tries 0
and rereadconfig to allow NB to be running but no new jobs to kick off.
But I could still submit jobs manually.

When I went to 6.5, VERITAS told me to just stop the bprd daemon.  Well,
with that not running I can not submit jobs manually.

Sometimes, I am working on the master server and bring up netbackup and
don't want any jobs to run. 

Anybody have any ideas on how to do this? 

Kevin Whittaker 
Syniverse Technologies 
Systems Engineer - UNIX Admin 
Work: (813) 637-5502 
Cell: (813) 810-6456 

Privileged/Confidential Information may be contained in this message or
attachments hereto. Please advise immediately if you or your employer do
not consent to Internet email for messages of this kind. Opinions,
conclusions and other information in this message that do not relate to
the official business of this company shall be understood as neither
given nor endorsed by it.

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] NetBackup 6.5 and holding Jobs

2008-01-08 Thread A Darren Dunham
On Tue, Jan 08, 2008 at 03:25:55PM -0700, Holowinski, Scott wrote:
>> nbpemreq -suspend_scheduling

> That doesn't appear to be a documented command line switch.  So how do
> you turn scheduling back on after using it?

It does appear in a technote.

http://seer.support.veritas.com/docs/278938.htm

-- 
Darren Dunham   [EMAIL PROTECTED]
Senior Technical Consultant TAOShttp://www.taos.com/
Got some Dr Pepper?   San Francisco, CA bay area
 < This line left intentionally blank to confuse you. >
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


[Veritas-bu] Getting a list of files from a failed backup

2008-01-08 Thread Chris_Millet

Yeah, as you mentioned with 5.5 million inodes, there is probably a significant 
amount of time before the client can start sending data to the media server, 
causing the default timeout value to get overran causing what looks to be a 
network connection timeout.

+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


[Veritas-bu] 1 TB limit ?

2008-01-08 Thread Chris_Millet

turn on verbose logging, and check the client side log (i.e. bpbkar).  See if 
it is hanging on a particular directory or file.  If it is, you may have 
corruption or some other problem in the client filesystem.

As of v6.5, I don't know of any 1TB limit in most traditional filesystem 
backups in Netbackup.

+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


[Veritas-bu] T2000 vaulting performance with VTL/LTO3

2008-01-08 Thread Chris_Millet

Ok, I figured it out.  Since we use Qlogic branded adapters and QLA driver 
instead of the QLC driver there was a setting we needed to change in 
/kernel/drv/qla2300.conf.  It is the equipment of the pci-max-read-request 
variable in qlc.conf.

# PCI-X Maximum Memory Read Byte Count.
#Range: 0, 128, 256, 512, 1024, 2048 or 4096 bytes
#Default: 0 = system default
hba0-pci-x-max-memory-read-byte-count=2048;

Anyway, that plus setting maxphys=0x80 in /etc/system seems to have removed 
all bottlenecks from the T2000 and we are able to get linespeed data transfer 
speeds through the QLE2462.

We are now able to vault jobs at around 160MB/sec from VTL to LTO3.  I've only 
tried two concurrent vaults for x2 performance.

+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] NetBackup 6.5 and holding Jobs

2008-01-08 Thread Holowinski, Scott
Len,

 

That doesn't appear to be a documented command line switch.  So how do
you turn scheduling back on after using it?

 

Thanks,

 

Scott 



From: Len Boyle [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, January 08, 2008 9:32 AM
To: Kevin Whittaker; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] NetBackup 6.5 and holding Jobs

 

Kevin, 

 

Try the command

 

nbpemreq -suspend_scheduling

 

len

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kevin
Whittaker
Sent: Tuesday, January 08, 2008 10:59 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] NetBackup 6.5 and holding Jobs

 

Ok, when I was on 5.1 I could change the behavior file to # of tries 0
and rereadconfig to allow NB to be running but no new jobs to kick off.
But I could still submit jobs manually.

When I went to 6.5, VERITAS told me to just stop the bprd daemon.  Well,
with that not running I can not submit jobs manually.

Sometimes, I am working on the master server and bring up netbackup and
don't want any jobs to run. 

Anybody have any ideas on how to do this? 

Kevin Whittaker 
Syniverse Technologies 
Systems Engineer - UNIX Admin 
Work: (813) 637-5502 
Cell: (813) 810-6456 


Privileged/Confidential Information may be contained in this message or 
attachments hereto. Please advise immediately if you or your employer do not 
consent to Internet email for messages of this kind. Opinions, conclusions and 
other information in this message that do not relate to the official business 
of this company shall be understood as neither given nor endorsed by it.

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


[Veritas-bu] 10Gbps network for backup LAN

2008-01-08 Thread vijayraj

how about configuring bondo on linux and ipmp on solaris side.

+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


[Veritas-bu] 1 TB limit ?

2008-01-08 Thread vijayraj

1 tb limit is already resolved in netbackup 5 with mp4.  We have been backing 
the database of more than 2 tb. But better you divide backup in multiple 
streams as some time it fails depending on the number of files you have in 
backup.

+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Some info on my experiences with 10GbE

2008-01-08 Thread Peters, Devon C
I don't think it's the T2000's that are so special, I think it may have
more to do with Sun's cards...

I recently did some 10G testing with a Sun X4100 w/ 2 Opteron 2216's
(dual core, 2.4Ghz) running RHEL 4, and found that it drastically
outperformed the 4-core 1Ghz T2000's.  I just swapped one of the cards
from a T2000 into the X4100, and I tested sending data from the
X4100->T2000, and then from the T2000->X4100.  When sending data from
the X4100->T2000, the throughput was the same as T2000->T2000, but when
sending data from T2000->X4100, the maximum throughput achieved was
9.8Gb/s with 16 threads.  An interesting observation is that all 4 cores
on the X4100 were 50% idle when running at this rate.

Also, worth mentioning is that I did some tests between a couple 8-core
1.2Ghz T2000's, and I got them to 9.3Gb/s with 16 threads, so the 8-core
1.2Ghz T2000's definitly outperform the 4-core 1Ghz ones.  Big supprise.
:)

Similar to the previous poster, iperf seemed to perform the best with a
512k buffer and 512k tcp window size, and I also saw some large
fluctuations in total throughput results.  I'm guessing this is due to
where the Solaris scheduler is running threads, since with mpstat I'd
occasionally see 1-2 cores (8 cpu's in mpstat) at 99-100% sys, and then
the other 2 cores would be 100% idle.  If the scheduler would spread the
load across the cores more evenly then perhaps more throughput could be
achieved.  To help smooth the results, all the numbers I've reported on
the list are the average of 3 separate 5-minute long iperf runs.

Btw, I'm also finding that the single threaded performance is crap with
these cards on the 1Ghz T2000's - though with the 1.2Ghz T2000's or
X4100, single threaded performance was slightly better (interestingly,
the 8-core T2000's consitently stumbled w/ 3 threads):


No. Threads Mbit/sec
X4100->T2000T2000->X4100
T2000->T2000(8core/1.2Ghz)
1   944 2143
1686
2   18673988
1937
3   25584772
1897
4   31465096
3704
6   43688071
5934
8   54688282
6908
16  64729842
9311
32  65139893
9283


-devon



Date: Mon, 7 Jan 2008 15:33:08 -0500
From: "Curtis Preston" <[EMAIL PROTECTED]>
Subject: Re: [Veritas-bu] Some info on my experiences with 10GbE
To: 
Message-ID:

<[EMAIL PROTECTED]>
Content-Type: text/plain;   charset="us-ascii"

This is another pro-T2000 report.  What makes them special?

---
W. Curtis Preston
Backup Blog @ www.backupcentral.com
VP Data Protection, GlassHouse Technologies 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of pancamo
Sent: Friday, January 04, 2008 11:43 PM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] Some info on my experiences with 10GbE


I just started testing 2 T2000's with dual 10Gbps SUN Nics directly
connected to each other...  

I'm somewhat pissed that I'm only able to get about 658Mbps from one
thread on the 10Gbps nic while I'm able to get 938Mbps using the onboard
1Gbs nic with when using the iperf default values.  Which means in some
cases the 10Gbit nic is actually slower than the onboard 1Gbit nic

However, I was able to get 7.2 Gbps using 10 threads.


Here are some of my max results with different thread (-P) values

./iperf -c 192.168.1.2 -f m -w 512K -l 512 -P x


TCP Win Buffer  Threads Gbps
512 512 1   1.4
512 512 2   2.5
512 512 4   4.3
512 512 6   6.4
512 512 8   6.1
512 512 10  7.2
512 512 15  4.6
512 512 18  3.6
512 512 20  3
512 512 30  2.5
512 512 60  2.3


Another annoying deal was that the results from iperf were not the same
each time I ran the test.   The results were as much as 3Gbps different
from run to run. The results should be the same for each run.





my /etc/system settings settings that I added as suggested by SUN

set ddi_msix_alloc_limit=8
set ip:ip_soft_rings_cnt=8
set ip:ip_squeue_fanout=1
set ip:tcp_squeue_wput=1
set ip:ip_squeue_bind=0
set ipge:ipge_tx_syncq=1
set ipge:ipge_bcopy_thresh = 512
set ipge:ipge_dvma_thresh = 1
set consistent_coloring=2
set pcie:pcie_aer_ce_mask=0x1




Here are the NDD settings that I found here:
http://www.sun.com/servers/coolthreads/tnb/parameters.jsp#2

ndd -set /dev/tcp tcp_conn_req_max_q 16384
ndd -set /dev/tcp tcp_conn_req_max_q0 16384
ndd -set /dev/tcp tcp_max_buf 10485760
ndd -set /dev/tcp tcp_cwnd_max 10485760
ndd -set /dev/tcp tcp_xmit_hiwat 131072
ndd -set /dev/tcp tcp_recv_hiwat 131072
ndd -set /dev/nxge0 accept_jumbo 1

I also found information

Re: [Veritas-bu] NetBackup 6.5 and holding Jobs

2008-01-08 Thread Len Boyle
Hello Kevin

If memory serves me, it is no longer suspended.
You can also use the command nbpemreq -resume_scheduling
To restore operations.

In the long term it would be good if netbackup could have a more general 
interface to the scheduling functions.
So one could suspend client schedules, or overhead job, like dups and db 
backups.
Also I do not believe that this command will stop user backups such has rman. 
It would be nice if one could do that also.

len

From: Kevin Whittaker [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 08, 2008 1:16 PM
To: Len Boyle; veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] NetBackup 6.5 and holding Jobs

Len,

That worked great, but if I stop and start netbackup will it still be suspended?

Kevin


From: Len Boyle [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 08, 2008 11:32 AM
To: Kevin Whittaker; veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] NetBackup 6.5 and holding Jobs
Kevin,

Try the command

nbpemreq -suspend_scheduling

len
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Whittaker
Sent: Tuesday, January 08, 2008 10:59 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] NetBackup 6.5 and holding Jobs


Ok, when I was on 5.1 I could change the behavior file to # of tries 0 and 
rereadconfig to allow NB to be running but no new jobs to kick off.  But I 
could still submit jobs manually.

When I went to 6.5, VERITAS told me to just stop the bprd daemon.  Well, with 
that not running I can not submit jobs manually.

Sometimes, I am working on the master server and bring up netbackup and don't 
want any jobs to run.

Anybody have any ideas on how to do this?

Kevin Whittaker
Syniverse Technologies
Systems Engineer - UNIX Admin
Work: (813) 637-5502
Cell: (813) 810-6456
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] NetBackup 6.5 and holding Jobs

2008-01-08 Thread Kevin Whittaker
Len,
 
That worked great, but if I stop and start netbackup will it still be
suspended?
 
Kevin



From: Len Boyle [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, January 08, 2008 11:32 AM
To: Kevin Whittaker; veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] NetBackup 6.5 and holding Jobs



Kevin, 

 

Try the command

 

nbpemreq -suspend_scheduling

 

len

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kevin
Whittaker
Sent: Tuesday, January 08, 2008 10:59 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] NetBackup 6.5 and holding Jobs

 

Ok, when I was on 5.1 I could change the behavior file to # of tries 0
and rereadconfig to allow NB to be running but no new jobs to kick off.
But I could still submit jobs manually.

When I went to 6.5, VERITAS told me to just stop the bprd daemon.  Well,
with that not running I can not submit jobs manually.

Sometimes, I am working on the master server and bring up netbackup and
don't want any jobs to run. 

Anybody have any ideas on how to do this? 

Kevin Whittaker 
Syniverse Technologies 
Systems Engineer - UNIX Admin 
Work: (813) 637-5502 
Cell: (813) 810-6456 
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


[Veritas-bu] Netbackup documentation written in French

2008-01-08 Thread Stump, Bob A
A person posted in the Symantec forums requesting where he may get
documentation for NetBackup written in French?

 

Here is a link to that posted thread. If you can help him then please
post a response at that link.

https://forums.symantec.com/syment/board/message?board.id=21&message.id=
39945

 

 

Here is the text of his request:

 

Bonjour
je cherche de la documentation ou un support de cour en francais sur
NETBackup
qq un peut m'aider
merci
ham

 

 

 

__

The information contained in this message is proprietary and/or confidential. 
If you are not the 
intended recipient, please: (i) delete the message and all copies; (ii) do not 
disclose, 
distribute or use the message in any manner; and (iii) notify the sender 
immediately. In addition, 
please be aware that any message addressed to our domain is subject to 
archiving and review by 
persons other than the intended recipient. Thank you.

Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] NetBackup 6.5 and holding Jobs

2008-01-08 Thread Len Boyle
Kevin,

Try the command

nbpemreq -suspend_scheduling

len
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Whittaker
Sent: Tuesday, January 08, 2008 10:59 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] NetBackup 6.5 and holding Jobs


Ok, when I was on 5.1 I could change the behavior file to # of tries 0 and 
rereadconfig to allow NB to be running but no new jobs to kick off.  But I 
could still submit jobs manually.

When I went to 6.5, VERITAS told me to just stop the bprd daemon.  Well, with 
that not running I can not submit jobs manually.

Sometimes, I am working on the master server and bring up netbackup and don't 
want any jobs to run.

Anybody have any ideas on how to do this?

Kevin Whittaker
Syniverse Technologies
Systems Engineer - UNIX Admin
Work: (813) 637-5502
Cell: (813) 810-6456
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


[Veritas-bu] NetBackup 6.5 and holding Jobs

2008-01-08 Thread Kevin Whittaker
Ok, when I was on 5.1 I could change the behavior file to # of tries 0
and rereadconfig to allow NB to be running but no new jobs to kick off.
But I could still submit jobs manually.

When I went to 6.5, VERITAS told me to just stop the bprd daemon.  Well,
with that not running I can not submit jobs manually.

Sometimes, I am working on the master server and bring up netbackup and
don't want any jobs to run.

Anybody have any ideas on how to do this?

Kevin Whittaker
Syniverse Technologies
Systems Engineer - UNIX Admin
Work: (813) 637-5502
Cell: (813) 810-6456
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


[Veritas-bu] Disk storage unit old lock files can they be deleted

2008-01-08 Thread mark_au

HI Guys

the site im working at has been having issues with its diskstorage unit.running 
out of space
even though there is seemingly penty of disk available, I believe that this may 
be because  the  images on disk are not getting moved to tape in time. I have 
re jigged the schedule so that the migration to tape happens earlier (there was 
previously a multi hour delay between the two jobs).

However during my investigation  i have noticed what seems to be old lock 
files. 
does anyone know what is the purpose of these, 
why do they not get cleaned up  and
can they be deleted safely if not

Were running nbu 6.0 mp 4 on solaris 10

cutdown listing below
thanks


2007 lab-ex2k3-v1_1179493284_C1_F1.1179493284.lock
--   1 root root   0 May 21  2007 
lab-ex2k3-v1_1179753436_C1_F1.1179753436.lock
--   1 root root   0 May 21  2007 
lab-ex2k3-v1_1179754385_C1_F1.1179754385.lock
--   1 root root   0 Jun  4  2007 
lab-ex2k3-v1_1180964051_C1_F1.1180964051.lock
--   1 root root   0 Jun  5  2007 
lab-ex2k3-v1_1180966971_C1_F1.1180966971.lock
--   1 root root   0 Jun  6  2007 
lab-ex2k3-v1_1181136894_C1_F1.1181136894.lock
--   1 root root   0 Jun  7  2007 
lab-ex2k3-v1_1181223199_C1_F1.1181223199.lock
--   1 root root   0 Jun  7  2007 
lab-ex2k3-v1_1181223207_C1_F1.1181223207.lock
--   1 root root   0 Jun  7  2007 
lab-ex2k3-v1_1181224177_C1_F1.1181224177.lock
--   1 root root   0 Jun 13  2007 
lab-ex2k3-v1_1181742660_C1_F1.1181742660.lock
--   1 root root   0 Jun 14  2007 
lab-ex2k3-v1_1181743632_C1_F1.1181743632.lock
--   1 root root   0 Jun 14  2007 
lab-ex2k3-v1_1181828145_C1_F1.1181828145.lock
--   1 root root   0 Jun 14  2007 
lab-ex2k3-v1_1181828183_C1_F1.1181828183.lock
--   1 root root   0 Jun 14  2007 
lab-ex2k3-v1_1181829140_C1_F1.1181829140.lock
--   1 root root   0 Jun 16  2007 
lab-ex2k3-v1_1181920574_C1_F1.1181920574.lock
--   1 root root   0 Jun 18  2007 
lab-ex2k3-v1_1182172766_C1_F1.1182172766.lock
--   1 root root   0 Jun 19  2007 
lab-ex2k3-v1_1182175724_C1_F1.1182175724.lock
--   1 root root   0 Jun 19  2007 
lab-ex2k3-v1_1182258133_C1_F1.1182258133.lock
--   1 root root   0 Jun 19  2007 
lab-ex2k3-v1_1182258136_C1_F1.1182258136.lock
--   1 root root   0 Jun 19  2007 
lab-ex2k3-v1_1182259071_C1_F1.1182259071.lock
--   1 root root   0 Jun 19  2007 
lab-ex2k3-v1_1182259135_C1_F1.1182259135.lock
--   1 root root   0 Jun 19  2007 
lab-ex2k3-v1_1182260077_C1_F1.1182260077.lock
--   1 root root   0 Jun 19  2007 
lab-ex2k3-v1_1182260091_C1_F1.1182260091.lock
--   1 root root   0 Jun 19  2007 
lab-ex2k3-v1_1182260104_C1_F1.1182260104.lock
--   1 root root   0 Jun 19  2007 
lab-ex2k3-v1_1182261020_C1_F1.1182261020.lock
--   1 root root   0 Jun 20  2007 
lab-ex2k3-v1_1182262036_C1_F1.1182262036.lock
--   1 root root   0 Jun 20  2007 
lab-ex2k3-v1_1182347461_C1_F1.1182347461.lock
--   1 root root   0 Jun 21  2007 
lab-ex2k3-v1_1182348448_C1_F1.1182348448.lock
--   1 root root   0 Jun 21  2007 
lab-ex2k3-v1_1182348460_C1_F1.1182348460.lock
--   1 root root   0 Jun 21  2007 
lab-ex2k3-v1_1182430933_C1_F1.1182430933.lock
--   1 root root   0 Jun 21  2007 
lab-ex2k3-v1_1182430942_C1_F1.1182430942.lock
--   1 root root   0 Jun 21  2007 
lab-ex2k3-v1_1182430945_C1_F1.1182430945.lock
--   1 root root   0 Jun 21  2007 
lab-ex2k3-v1_1182431878_C1_F1.1182431878.lock
--   1 root root   0 Jun 21  2007 
lab-ex2k3-v1_1182431914_C1_F1.1182431914.lock
--   1 root root   0 Jun 21  2007 
lab-ex2k3-v1_1182431922_C1_F1.1182431922.lock
--   1 root root   0 Jun 21  2007 
lab-ex2k3-v1_1182432844_C1_F1.1182432844.lock

+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu