Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
ARCServe NDMP NAS Option 1
- Thread starter mfc133
- Start date
-
1
- #2
More often than not it depends on the OnTAP version the filer is running. If you have one on the CDL it should work fine, so should newer versions, however there have been some issues in the past with newer versions requiring patches.
Perhaps if you give us some more details on the patch levels of arcserve, the filer, the problems you are experiencing, and the number of type of drives being used in the overland changer we may be able to offer some more specific guidance.
Perhaps if you give us some more details on the patch levels of arcserve, the filer, the problems you are experiencing, and the number of type of drives being used in the overland changer we may be able to offer some more specific guidance.
- Thread starter
- #3
The filer(FAS3020) is running OnTAP 7.1, with NDMP set to v4. ARCServe is 11.1 SP2 (build 3200). The library is an Overland NEO 2000 with 2 HP LTO3 drives. The library is connected directly to the filer via SCSI.
I've checked the comp. matrix on CA's site. OnTAP 7.1 is supported for the NAS option, and the Overland library is also supported. The only thing that may be an issue is that the firmware we're running on the drives themselves aren't listed on CA's site. We're running G24H but CA has G23H listed.
The funny thing is we had it working fine before. We recently had an extended power outage where we had to shutdown the library and backup server before the UPS gave out. Since then we've tried a number of things and we can't get ARCServe to talk to the filer/library.
One thing I did notice is that if I'm telnet'd in to the filer, when I try to connect to th filer through ARCServe I see SCSI bus errors/resets:
fas1> Tue Aug 8 14:37:29 EDT [scsiAdapter.detected.unexpected.bus.phase:error]
: SCSI adapter 4b encountered an unexpected bus phase. Issuing SCSI bus reset.
Tue Aug 8 14:37:56 EDT last message repeated 5 times
Tue Aug 8 14:38:01 EDT [scsi.cmd.pastTimeToLive:error]: Device 4b.1: request failed after try #1: cdb 0x00.
Tue Aug 8 14:38:01 EDT [scsiAdapter.detected.unexpected.bus.phase:error]: SCSI
adapter 4b encountered an unexpected bus phase. Issuing SCSI bus reset.
When I try to add a NAS server through device config. in ARCServe, it hangs and throws these SCSI errors on the filer until I kill ARCServe on the backup server.
I've checked the comp. matrix on CA's site. OnTAP 7.1 is supported for the NAS option, and the Overland library is also supported. The only thing that may be an issue is that the firmware we're running on the drives themselves aren't listed on CA's site. We're running G24H but CA has G23H listed.
The funny thing is we had it working fine before. We recently had an extended power outage where we had to shutdown the library and backup server before the UPS gave out. Since then we've tried a number of things and we can't get ARCServe to talk to the filer/library.
One thing I did notice is that if I'm telnet'd in to the filer, when I try to connect to th filer through ARCServe I see SCSI bus errors/resets:
fas1> Tue Aug 8 14:37:29 EDT [scsiAdapter.detected.unexpected.bus.phase:error]
: SCSI adapter 4b encountered an unexpected bus phase. Issuing SCSI bus reset.
Tue Aug 8 14:37:56 EDT last message repeated 5 times
Tue Aug 8 14:38:01 EDT [scsi.cmd.pastTimeToLive:error]: Device 4b.1: request failed after try #1: cdb 0x00.
Tue Aug 8 14:38:01 EDT [scsiAdapter.detected.unexpected.bus.phase:error]: SCSI
adapter 4b encountered an unexpected bus phase. Issuing SCSI bus reset.
When I try to add a NAS server through device config. in ARCServe, it hangs and throws these SCSI errors on the filer until I kill ARCServe on the backup server.
it may be worth resetting the library, and then issuing an ndmp kill all on the NAS filer to reset NDMP on the filer.
You can also look to see if the filer is still seeing the devices correctly by issuing a sysconfig -m and sysconfig -t. If the filer isn't seeing the devices correctly then you have configuration or hardware issues between the filer and the library which need to be resolved before ARCserve will be able to work with it again.
You can also look to see if the filer is still seeing the devices correctly by issuing a sysconfig -m and sysconfig -t. If the filer isn't seeing the devices correctly then you have configuration or hardware issues between the filer and the library which need to be resolved before ARCserve will be able to work with it again.
- Thread starter
- #5
It turns out that the SCSI card in the Filer was the culprit here. After speaking with NetApp, apparently the SCSI errors the filer was throwing were hardware-level errors. They shipped us out a new SCSI adapter and all is well since we installed it. Kind of odd considering the card and the filer itself are not even a year old but I've seen stranger things happen.
Thanks for the help, much appreciated.
Thanks for the help, much appreciated.
- Status