Good Morning, 
 
We are not using NDMP, with the EMC box, but I believe that the answer will be 
the same. 
 
The main thing to remember about ndmp backups is that a netbackup client is not 
doing the backup. The EMC box is doing the backup. So you have to look at the 
rules that the EMC box imposes on the process. So it might have rules that 
define at what level you can break up the backup. Or it might just require that 
the "*" character be escaped to get thru the different software levels. 
 
I thought that the 1TB limit for restores was fixed a while back. You might 
want to open a ticket with symantec(aka veritas) and ask if this is still a 
problem with the level of netbackup and the EMC hardware/software that you are 
using. 
 
Also you can try a test backup and restore using the EMC software to see if it 
works at that level without netbackup in the mix. And then if you still have 
problems go back to netbackup support. 
 
len

________________________________

From: veritas-bu-bounces at mailman.eng.auburn.edu [mailto:veritas-bu-bounces 
at mailman.eng.auburn.edu] On Behalf Of MacKinnon, Gregory (G.R.)
Sent: Monday, April 16, 2007 7:13 AM
To: veritas-bu at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Include list for NDMP


 


________________________________

        From: veritas-bu-bounces at mailman.eng.auburn.edu 
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Bobby 
Williams
        Sent: Monday, April 16, 2007 6:22 AM
        To: veritas-bu at mailman.eng.auburn.edu
        Subject: [Veritas-bu] Include list for NDMP
        
        

        Our master is set a Solaris 8 V880 with NB 5.1 MP6. 

        Our NDMP hardware is : 
        $ /usr/local/bin/sudo /usr/openv/volmgr/bin/set_ndmp_attr -verify
        Password:
        
        Verify Host name: XXXXX
        Connecting to host "XXXXX" as user "ndmp"...
        Waiting for connect notification message...
        Opening session--attempting with NDMP protocol version 4...
        Opening session--successful with NDMP protocol version 4
        host supports TEXT authentication
        host supports MD5 authentication
        Getting MD5 challenge from host...
        Logging in using MD5 method...
        Host info is:
        host name "server_2"
        os type "DartOS"
        os version "EMC Celerra File Server.T.5.5.22.2"
        host id "abc1997"
        Login was successful
        Host supports LOCAL backup/restore
        Host supports 3-way backup/restore
        
        We have some file systems that are over 1TB that back up just fine.  We 
can't restore.  There is a Tech Note from Veritas saying that backups over 1TB 
have trouble restoring.

        I changed the include list to split up the bigger file systems.  I used 
a Unix type syntax of /mount/bigshare/a* with NEW_STREAM between every 10 
letters of the alphabet.   Was trying to see how the split would divide up the 
total data (have done the same thing with many Unix and Windows boxes).

        As soon as I use the "*" in the file selection, the backups fail with 
an error 99, NDMP backup failure.  It happens immediately as soon as the tape 
is loaded.

        Is there a "trick" to assigning a file selection list to a NDMP mover? 
        Should not have patching the master to MP6 resolved the issue anyway? 
        Thanks. 




        Bobby Williams 
        2205 Peterson Drive 
        Chattanooga, Tennessee  37421 
        423-296-8200  

                

         

        NB 5.x doesn't do wildcards.

         

        Gregg 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20070416/acb2676f/attachment.html