Errors: Media write error(84), FTL - socket write failed, 24: socket write failed, INF - Server status = 24 & cannot write data to network: An existing connection was forcibly closed by the remote host.
Not sure if my issue is because of MSEO, but I don't have that.
How can I run pkginfo in windows to see the output?
Media write errors (Status 84) after upgrade to NetBackup 7.1 (http://www.symantec.com/docs/TECH176291)
My bptm logs show these errors:
pkginfo is Solaris command, and is not available on Windows.
Actually, block position which the tape drive provided by VTL is not same with which NetBackup expects.Does it work without multiplexing well? Any defect in Filestreamer?
Backups work well without multiplexing, in fact they work fine with multiplexing if I run backup of C drive for 2 clients in same policy or if I take backup of 3 clients with less data size (for example about 6-8 GB).
Moreoever, for some reason I cannot use the same MPX Media for backups again and get error 86 on it, but that is not a priority right now.
Status code 86 is "media positioning failure". Positioning command to the tape drive returns by error. This indicate somethimg wrong with VTL and its virtual media. Any error in Filestreamer's log?
BTW, I found fix for multiplexing backup in NetBackup 7.5, with that backup fails with status code 25.
This guide does not detail about this defect any more, so I can not determite if this hit to your case.
If you are seriously in difficulties, it is better to log a call with Filestreamer and Symantec.
Emulating SCSI for tape access has never been very successful in VMs.
These are hardware errors that need to be logged with your VTL vendor:
io_ioctl: WRITE FILEMARKS returned (1:write filemarks scsi command failed, status = 0x2, key = 0x5, asc = 0x24, ascq = 0x0) tapealert_and_release: TapeAlert failed (log sense scsi command failed, status = 0x2, key = 0x5, asc = 0x20, ascq = 0x0)
The following is a sign of SAN firmware or configuration problem (as per Status 84 In Depth Troubleshooting Guide)::
write_data: block position check: actual 2370, expected 2371 write_data: FREEZING media id 4_1810, External event caused rewind during write, all data on media is lost
Best Practice is to provide physical servers as media servers.
Well, here's the thing. Firestreamer said "Sorry" for NetBackup, and said "Symantec was uncooperative when we approached them in order to make Firestreamer compatible with their backup products." lol Good that we didn't buy it yet.
Any other known good VTL which is fully compatible?
Logging - firestreamer console or logs or the Windows event logs - NONE.
Incompatible Software - There no option to check that within Firestreamer.
Moreover, I just found that Firestreamer console is showing Data compression enabled for the virtual media files. trying to find how to disable it.
Still trying to figureout how to disable "Speed Write".
Here's the reply for Firestreamer:
There is a bug in Firestreamer 4.0 related to tape positioning. It does not affect Microsoft DPM, but may affect Netbackup. The bug is fixed in Firestreamer 4.1, which is not released yet; the release date is unknown at this stage.
So I can't do much about multiplexing on Firestreamer.
Microsoft DPM is only software Filestreamer supports.
By HCL, there seems no software based VTL supported by NetBackup. NetBackup is backup infrastructure for enterprise, so only proven hardware based VTLs are listed.
BTW, why do you need to use Filestreamer? For use of removable media?
I am trying to use VTL for training and testing purposes. For the live environment we have IBM Ultrium drives. We are trying to create a small lab for testing before we roll our updates in the live environment, and for training purposes.
So, mhvtl is best for test purpose. But mhvtl is linux software. If you need to test on Windows, consider to export robots and drives via iSCSI using scst-iscsi.
It is not so easy, but worth to try. If you don't need to test encryption, Scientific Linux CERN 5 is nice because SLC5 has scst SRPM and is easy to build. Installation of mhvtl rpm is also easy on SLC5.
Much thanks Yasuhisa... mhVTL rocks.
I tested Multiplexing of 5 clients with about 25 GB data to begin with, and it all went smooth. And, mhVTL actually emulates complete Robot, so I got MAP as well.
A preconfigured mhVTL -