Thanks all for responding so fast,

Timothy and Stephen  were the one's harping  on resolving the issue to be either at filer end or Veritas end. And this approach proved correct.

As soon they  asked me to check dump for root volume ... i remembered that i hadn't checked this for root, but done a dump for other volumes , just to ascertain whether the SCSI channel was the issue . I checked the same today, and bingo

> dump 0uf nrst0a /vol/vol0
DUMP: creating "/vol/vol0/../snapshot_for_backup.26" snapshot.
DUMP: could not create "backup" snapshot : No more snapshots available.
Please delete one or more snapshots before trying backup again.

DUMP: Dump failed to initialize.
DUMP: DUMP IS ABORTED

As any backup on our NAS is a Snapshot and backup, so if number of snapshots exceeds the limit allowed by OS , then we cant take any backup on that volume. My problem was some old snapshots lying around, and so the limit of 31 in 6.3.3D11 was reached. I have deleted the snapshots not required, and now all's well.

Thanks & regards,

Manish  A Kinnerkar.






stephen.j.darragh@baesystems.com

12/17/2003 11:00 PM

       
        To:        manish.a.kinnerkar@jpmorgan.com
        cc:        
        Subject:        RE: NetBackup 4.5 ,NDMP backup failing for root volume



Hi,
 
I would try to do a netapp dump of /vol/vol0 and get Veritas out of the picture.
If it fails, it's a problem with the tape or drive.
 
If that works, then I would go to the filer and there are options
ndmpd debug 50 and
ndmpd debug screen (toggle to turn off all the messages to the screen)
ndmpd debug by itself will let you check the values.
This will create debug files in the etc directory of the filer.
 
Also, create /usr/openv/netbackup/logs/ndmp so the backup attempt will get logged.
Now try a backup with Veritas and you should have some data that you can post or log to either netapp or veritas.
 
Good luck, the error 99s are generic and hard to track down.
 
Stephen Darragh
 
 
-----Original Message-----
From:
manish.a.kinnerkar@jpmorgan.com [mailto:manish.a.kinnerkar@jpmorgan.com]
Sent:
Wednesday, December 17, 2003 2:56 AM
To:
toasters@mathworks.com
Subject:
NetBackup 4.5 ,NDMP backup failing for root volume

 


Hi All,


We are having a setup of 2 filers with locally attached Tape drives - part of a Multihost Tape librbary . The scheduling &  backup control is via a Netbackup 4.5  server  via NDMP. The filers as well as the Backup server are a part of a Win2k domain .

On one filer, the backup of /vol/vol0 fails specefically after initiation of the ndmp session with the filer. All other volumes can be backed up properly without any such issues. The ndmp session report  on the filer is initiated , tape is opened and then it is displays as halted . In netbackup the error code is 99 , which asks you to check the backup  file list for invalid entries. The other filer's backup goes well for all volumes including root.


I have checked by trying /vol/vol0  or /etc or / as the paths , with no effect.All options seem same on both filers. Can someone suggest  what would specefically need to checked in this case.


regards,

Manish


This communication is for informational purposes only. It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its subsidiaries
and affiliates.




This communication is for informational purposes only. It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its subsidiaries
and affiliates.