Actually is that simple, if you comply with 2 conditions:
1) you substystem MUST supoport on-the-fly volume grown. I know that the Engenio ( SUN/STK ) discs support that.
2) You O.S. MUST support the same feature. This is simple if you have a LVM live Veritas VxVm or Solaris/AIX/HP-UX bundle...
This tray isn't orderable. This a strategy to force customers to buy the package (tray + drive) from SUN. Even if you find the P/N, SUN will not sell you the part. The only way to go is to try to find any 2nd hand trays on the internet...
Try getting the RSM driver for the L20 (http://www.storagetek.com/support/drivers.html), and install the latest HP driver from HP web site.
To be sure if the HW is 100 %, try using ntbackup just for testing.
Cheers!
As far as i know, Amanda is not supported for SUN/STK libraries. I have worked on a case trying to get this config to work, and tried everything you could think of, without success.
I would suggest you goig to comercial solutions like NBU, TSM, LEgato, DP, TINA, and so on...
Hi there, I've saw lots of cases where this problem was resolved updating the firmware level for both the library end the drive to the most current version. There are no problem regarding this kind of errors addressed in the new versions, but that's just a personal experience.
STK v107 is a different version from ATL for sure as STK does some tweaking to port then to STK libraries. Also each DLT series drives has a "personality module" which dentifies these drives as a STK one.
Actually the latest version is 5.34.04.00, and it's available for download at the CRC website. This version of Santricity should work with your firmware release, as it's compatible with almost all firmwares since 4.01.xx.xx.
If your're using Windows XP, it's not supported yet, so try using 2000...
Hi there, i'm having this issue, but i do have available medias in the SCRATCH and BCV_VOB03 pools. And according to the media list i don't have any FROOZEN or SUSPENDED media.
vmdb_query_scratch_bypool2: unable to unpack string from server: volume does not exist in database (35)
01:28:29.519...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.