Anybody uses VTL Falconstor for tapes on i?
We want change the block Size when create a tape ...
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
7 replies Latest Post - 2012-09-19T09:35:42Z by FPLAZAVI
Pinned topic VTL FALCONSTOR
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-09-19T09:35:42Z at 2012-09-19T09:35:42Z by FPLAZAVI
Re: VTL FALCONSTOR2012-09-14T14:44:55Z in response to FPLAZAVIHi Fernando, what block size do you use now and what do you want it to be?
The block size on saves is controlled by the type of drive you are using or emulating.
On the IBM i, you can specify the 'Use Optimum block' (USEOPTBLK) parameter. If *YES is specified, it will use the maximum block size the tape drive can use. Most newer tape drives use a block size of 256K. When you specify *NO, it will change the block size to 32K. Those are the only 2 choices
Here's the help text for the parameter :
The optimum block size supported by the device is used
for Save commands. If the block size that is used is
larger than a block size that is supported by all
device types, then:
o Performance may improve.
o The tape file that is created is only compatible
with a device that supports the block size used.
Commands such as Duplicate Tape (DUPTAP) do not
duplicate files unless the files are being
duplicated to a device which supports the same
block size that was used.
o The value for the DTACPR parameter is ignored.
The optimum block size supported by the device is not
used. Save commands use the default block size
supported by all device types. The tape volume can be
duplicated to any media format using the Duplicate
Tape (DUPTAP) command.
Here's the block sizes different tape drives use. The Falconstore is not listed but it depends on the drive you are emulating
Tape Drive Model Format/Density Uses Optimum Block Maximum Optimum Block Size
MLR3 - 25GB *MLR3 Yes 256K
SLR60 *SLR60 Yes 256K
SLR100 - 50GB *SLR100 Yes 256K
Model 3590 *FMT3590 Yes 256K
Model 3590E *FMT3590E Yes 256K
Model 3590H *FMT3590H Yes 256K
Model 3570-Bxx *FMT3570 Yes 256K
Model 3570-Cxx *FMT3570E Yes 256K
Model 3592 J1A *FMT3592A1 Yes 256K
Model 3592 E05 *FMT3592A1/A2 Yes 256K
Model 3592 E06 *FMT3592A2/A3 Yes 256K
Model 3592 E07) *FMT3592A3/A4 Yes 256K
LTO 1/2/3/4/5 *ULTRIUM1/2/3/4/5 Yes 256K
ProtecTIER *ULTRIUM3 Yes 256K
3490 F-18 track *FMT3480 Yes 64K
3490 F-36 track *FMT3490E Yes 256K
7208 Model 342 *FMT20GB Yes 240K
7208 Model 345 *FMT60GB Yes 240K
VXA-2 *VXA2 Yes 240K
VXA-3 *VXA2/3 Yes 240K
Dat 72 - 4mm *DAT72 Yes 256K
Re: VTL FALCONSTOR2012-09-17T07:40:40Z in response to SystemAdminHI Mervyn ....
Our problem is that we don't manage the configuration on the FlaconStor side ...
We change from POWER6 to POWER7 ... V6R1M1 ... new HW FC from 4 to 8 Gb ... and our tape drives are slow ... I can see on Iseries Navigator -configuration & service - tape resources ...propierties on Capabilities that the block size is 32768 and the save is make with USEOPTBLK *yes ...
Any idea ...
Can we do something on iseries side for optimize this backups?
Re: VTL FALCONSTOR2012-09-17T17:42:14Z in response to FPLAZAVIHi Fernando, the first problem I see is that the Falconstor is not supported on Power 7 hardware. Power 7 only uses IOPless IOAs and if you look at the following URL, you will see that the Falconstor is not listed as supported ( It also goes out of service in March 2013)
I would suggest making sure you have all these PTFs applied and then test
MF54231 and MF52471 (or superseding PTFs) and MF49848, MF52325, MF52423, MF52653, MF54265, MF54671, MF55016, MF55017, MF55018, MF55032, MF55406, MF55407 and MF55408.
The smaller block size is what is causing the backups to be slow
Re: VTL FALCONSTOR2012-09-18T15:18:35Z in response to FPLAZAVIHi Fernando, sorry about that....
Looking at the PMR, this is not a IBM Falconstor but Sun. I think they need to verify that the tape drives are emulating 3580's correctly. It does not look like they are.