Storage & Backup solutions on virtual VAX and Alpha
0 likes3 views
The document outlines the services offered by a software engineering company specializing in hardware virtualization, particularly for legacy systems with over 20 years of experience. It discusses the challenges posed by aging hardware infrastructure and provides a roadmap for the successful transition to a virtualized environment, highlighting key parameters for analysis, project planning, and the benefits of reduced costs and improved performance. Additionally, specific solutions and technologies for virtualization in legacy systems are detailed, including various storage options and the use of the tapemgr utility for managing virtual tape libraries.
![TapeMGR for OpenVMS
29
$ tapemgr help load
TAPEMGR
LOAD
TAPEMGR LOAD device [filespec]
This command will load a virtual tape container file. The filespec
must include a full path in unix style (for example
"/files/tape.vtape"). The string must be enclosed in quotes. The path
must be on a mounted device that is not the system device.
If no filespec is given then the file as specified in the emulator's
configuration file will be used.
The tapeunit may not be mounted for this operation to succeed.
Topic?](https://image.slidesharecdn.com/avtware-250211065216-36904cb1/85/Storage-Backup-solutions-on-virtual-VAX-and-Alpha-29-320.jpg)
Storage & Backup solutions on virtual VAX and Alpha
- 2. Who are we? ▪ Software Engineering Company ▪ Located: Eindhoven, NL ▪ DEC Software Engineering ▪ 20+ years virtualization experience ▪ Global client base - Global presence ▪ X-industry ▪ Excellent expertise on Legacy Hardware platforms, e.g. Alpha, VAX,.. 2
- 3. 3 Legacy Hardware - a possible Dilemma 1 Cooling & floor space requirements 3 Unplanned downtime and loss of productivity 5 Scalability & Performance 2 Rising hardware and maintenance costs 4 Aging storage challenges 6 Business-critical systems Aging IT Infrastructure Is The Biggest Roadblock On The Path To Innovation & Digital Transformation
- 4. 4 "Virtualize your Legacy hardware into a modern IT Infrastructure" 4
- 5. 5 Software migration 1 Hardware Virtualization 3 HP Integrity / x86 2 What option do we have? Do nothing 4 Or choose the smart & riskfree way = “Hardware Virtualization“ 5
- 6. How to move to a comfortable HW virtualization? 6 What are the key parameters for a successful transfer? ▪ Analyze the legacy hardware environment ▪ Define and set the systems expectations on performance, load, system type.... ▪ Select the host platform, the new environment should run on: Local x86 server, Cloud, VMware, Hyper-V etc. ▪ What type of storage is preferred/available in the new environment ▪ Plan data migration ▪ POC (proof of concept)
- 7. 7 Project Plan to support the Virtualization
- 8. ▪ System downtime during the project is very low ▪ Floor space, electricity and cooling is getting minimized ▪ No need for a spare parts stock and further market research for spare parts ▪ Time saving because of higher hardware performance ▪ Easier to manage/maintain the legacy machines because of mainstream hardware ▪ Comply with modern datacenter standards ▪ Short term project (matter of hours to virtualize a legacy system) ▪ No change to the application(s) or operating system! ▪ Decreases unplanned server downtime ▪ Reduces overall operating costs What are the benefits? 8
- 9. Virtualization 9 Bare Metal Virtual Machine vtServer X86 Host vtAlpha vtAlpha vtVAX vtVAX vtServer vtAlpha vtAlpha vtVAX vtVAX X86 Host vtServer vtServer VM VM VM
- 10. Storage choices and possibilities 10 Legacy environment ▪ Local storage ▪ SCSI, MSCP, DSSI, IDE ▪ Network storage ▪ Pathworks, NFS ▪ Fibre Channel storage ▪ 1/2/4 Gbit ▪ Maintenance ▪ Replacement parts ▪ Technical skills Virtualized environment ▪ Local storage ▪ SAS, SATA, eSATA, SSD, NVMe, USB ▪ Network storage ▪ NFS, SMB, iSCSI ▪ Fibre Channel storage ▪ 8/16/32..128 Gbit ▪ Maintenance ▪ Off the shelf parts ▪ Mainstream
- 11. Storage virtualization/migration using vtVAX or vtAlpha 11 Legacy environment Virtualized environment Migrate SCSI DSSI MSCP FC
- 12. Virtual Disk/Tape Virtualized storage controllers vtVAX 12 ▪ KZDDA SCSI Controller ▪ Fully virtualized ▪ Physical disks/tapes ▪ Disk/tape container files ▪ RQDX3 MSCP Controller ▪ Fully virtualized ▪ Physical disks/tapes ▪ Disk/tape container files ▪ KFMSA DSSI Controller ▪ Fully virtualized ▪ Physical disks ▪ Disk container files Physical Disk/Tape
- 13. Virtual Disk/Tape Virtualized storage controllers vtAlpha 13 ▪ KZPBA SCSI Controller ▪ Fully virtualized ▪ Physical disks/tapes ▪ Disk/tape container files ▪ KGPSA FC Controller ▪ Fully virtualized ▪ Physical disks/tapes ▪ Disk/tape container files ▪ Direct link to a FC host adapter ▪ VTDSK Controller ▪ Fully virtualized ▪ Physical disks ▪ Disk container files ▪ SCSI, DSSI, MSCP, RAID, FC Physical Disk/Tape
- 14. VTDSK controller 14 ▪ Flexible and versatile ▪ Configurable OpenVMS device name (MSCP, SCSI, DSSI, CI, FC, IDE, RAID) ▪ No chipset emulation overhead in vtAlpha (paravirtual) ▪ No chipset driver overhead in OpenVMS vtServer vtAlpha vtDSK Physical disk / Diskimage vtDSK driver DUA,DKA,DIA,$1$DGA,DQA,DRA PU,PK,PI,PG,PQ,PR OpenVM S
- 15. VTDSK controller 15 ▪ Flexible and versatile ▪ Configurable OpenVMS device name ▪ No chipset emulation overhead in emulator, paravirtual ▪ No chipset driver overhead in VMS 0 10000 20000 30000 40000 50000 60000 70000 80000 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 i/o requests per second es47-vtdsk es47-isp1040 seq write 1-2-4-8- seq read 1-2-4-8- 16-32-64-128 blocks seq read/write 1- 2-4-8- 16-32-64-128 blocks rnd write 1-2-4-8- 16-32-64-128 blocks rnd read 1-2-4-8- 16-32-64-128 blocks rnd read/write 1-2- 4-8- 16-32-64-128 blocks
- 16. VTDSK controller 16 ▪ Flexible and versatile ▪ Configurable OpenVMS device name ▪ No chipset emulation overhead in emulator, paravirtual ▪ No chipset driver overhead in VMS 0 500000 1000000 1500000 2000000 2500000 3000000 3500000 4000000 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 i/o throughput in kb/sec es47-vtdsk es47-isp1040 seq write 1-2-4-8- 16-32-6-128 blocks seq read 1-2-4-8-16- 32-6-128 blocks seq read/write 1-2- 4-8-16-32-6-128 blocks rnd write 1-2-4-8-16- 32-6-128 blocks rnd read 1-2-4-8-16- 32-6-128 blocks rnd read/write 1-2- 4-8-16-32-6-128 blocks
- 17. KGPSA FC controller 17 ▪ Direct link to a FC host adapter ▪ No restriction on FC host adapter speed (128Gb +) ▪ Support of any brand FC storage controller ▪ Identifier emulation, SCSI-4 or higher support ▪ Lun remapping ▪ NPIV support FC HBA SAN fcad1 physical fcad2 NPIV fcad3 NPIV vtAlpha 1 vtAlpha 2 KGPSA KGPSA VMS Tru64 vtServer
- 18. KGPSA FC controller 18 ▪ Direct link to a FC host adapter ▪ No restriction on FC host adapter speed (128Gb +) ▪ Support of any brand FC storage controller ▪ Identifier emulation, SCSI-4 or higher support ▪ Lun remapping ▪ NPIV support 0 5000 10000 15000 20000 25000 30000 35000 40000 45000 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 i/o requests per second hp AlphaServer ES47 7/1150 vtAlpha-ES47 seq write 1-2-4-8- seq read 1-2-4-8- 16-32-64-128 blocks seq read/write 1- 2-4-8- 16-32-64-128 blocks rnd write 1-2-4-8- 16-32-64-128 blocks rnd read 1-2-4-8- 16-32-64-128 blocks rnd read/write 1-2- 4-8- 16-32-64-128 blocks HITACHI OPEN-V
- 19. KGPSA FC controller 19 ▪ Direct link to a FC host adapter ▪ No restriction on FC host adapter speed (128Gb +) ▪ Support of any brand FC storage controller ▪ Identifier emulation, SCSI-4 or higher support ▪ Lun remapping ▪ NPIV support 0 200000 400000 600000 800000 1000000 1200000 1400000 1600000 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 i/o throughput in kb/sec hp AlphaServer ES47 7/1150 vtAlpha-ES47 seq write 1-2-4-8- 16-32-6-128 blocks seq read 1-2-4-8-16- 32-6-128 blocks seq read/write 1-2- 4-8-16-32-6-128 blocks rnd write 1-2-4-8-16- 32-6-128 blocks rnd read 1-2-4-8-16- 32-6-128 blocks rnd read/write 1-2- 4-8-16-32-6-128 blocks HITACHI OPEN-V
- 20. Fibre Channel storage controllers 20 ▪ HPE EVA, MSA, 3PAR ▪ HPE Alletra, Primera ▪ HSG80 ▪ Hitachi ▪ Dell EMC VPLEX ▪ Pure storage ▪ IBM XIV ▪ Infinidat ▪ NetApp ▪ QNAP
- 21. OpenVMS supported FC storage 21 x86 HP ProLiant FC HBA vtServer fcad1 vtAlpha KGPSA OpenVMS PGA LUN: 120 ID: 1201 LUN: 120 ID: 1201 LUN: 120 ID: 1201 $1$DGA1201 Direct link 3PAR
- 22. OpenVMS unsupported FC storage 22 IBM XIV FC HBA vtServer fcad1 vtAlpha KGPSA OpenVMS PGA LUN: 20 LUN: 20 LUN: 20 $1$DGA1201 Direct link Lun 20 -> Lun 40, ID 1201 SCSI-4 SCSI-3 LUN: 40 ID: 1201 x86 HP ProLiant
- 23. Tape backup after virtualization 23 Legacy environment Virtual environment ▪ Virtual tapes (files) ▪ Physical tapes (SCSI, FC, USB) ▪ TapeMGR ▪ Virtual tape library Tape Tape library SCSI RAID, FC, iSCSI, NFS, SMB
- 24. TapeMGR for OpenVMS 24 ▪ Create / delete tapeimages ▪ Load / unload tapeimages ▪ Supports compression ▪ Limit size of tapeimages for multivolume backups ▪ Support for different tape formats (LM driver, MTD etc.) ▪ Copy or move tapeimages
- 25. TapeMGR for OpenVMS 25 OpenVMS TapeMGR vtAlpha/vtVAX MKA400 CPU $ tapemgr load MKA400 “/data/tape6” Special instruction tape 6 tape1 tape 4 tape 2 tape 5 tape 3 tape 6 Storage
- 26. TapeMGR for OpenVMS 26 vtAlpha 4.4.0 R7 Copyright AVTware 2010-2024 Build date: 23-Oct-2024 11:02 Revision: 4605 System model: AlphaServer ES47 Number of cpu's: 4 Memory size: 8092Mb P00>>> sh dev pka0.7.0.0.0 PKA0 QLOGIC ISP1040 SCSI dka0.0.0.0.0 DKA0 AVTWare AVTVdisk J001 OpenVMS8.3_ES45_demo dka100.1.0.0.0 DKA100 AVTWare AVTVdisk J001 vttools_alpha_vms.vdisk (readonly) mka200.2.0.0.0 MKA200 AVTWare AVTVtape H001 (format=default,removable) dka400.4.0.0.0 DKA400 AVTWare AVTVdisk J001 VMSV8.3.iso (readonly,unloaded,removable) eia0.0.0.3.0 EIA0 ei1000 3a-db-6d-49-19-4a avt0 (tap0) host speed: 1gb (auto) pica.0.0.7.0 PICA Intel I8259 picb.1.0.7.0 PICB Intel I8259 uarta.2.0.7.0 UARTA NS PC16650 connected to port 20003 host 127.0.0.1:44920 uartb.3.0.7.0 UARTB NS PC16650 telnet listening on host :20004 bbwa.4.0.7.0 BBWA Dallas DS1287A flpa.5.0.7.0 FLPA Intel I82078 kbda.6.0.7.0 KBDA Intel I8042 i2ca.7.0.7.0 I2CA NXP PCF8584 P00>>>
- 27. TapeMGR for OpenVMS 27 $ show device mk Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt VMS83$MKA200: Online 0 $ prod show prod ------------------------------------ ----------- --------- PRODUCT KIT TYPE STATE ------------------------------------ ----------- --------- AVT AXPVMS TAPEMGR V2.1 Full LP Installed CPQ AXPVMS CDSA V2.2-271 Full LP Installed DEC AXPVMS DECNET_PHASE_IV V8.3 Full LP Installed DEC AXPVMS DWMOTIF V1.6 Full LP Installed DEC AXPVMS DWMOTIF_SUPPORT V8.3 Full LP Installed DEC AXPVMS OPENVMS V8.3 Platform Installed DEC AXPVMS TCPIP V5.6-9 Full LP Installed DEC AXPVMS VMS V8.3 Oper System Installed HP AXPVMS AVAIL_MAN_BASE V8.3 Full LP Installed HP AXPVMS KERBEROS V3.0-103 Full LP Installed HP AXPVMS SSL V1.3-281 Full LP Installed ------------------------------------ ----------- --------- 13 items found $
- 28. TapeMGR for OpenVMS 28 $ tapemgr help TAPEMGR The vtAlpha emulator allows several parameters to be specified for logical tape devices. The TAPEMGR utility can be used to create, delete or change container files, and to select the format used to read or write these files. The utility needs OPER and CMKRNL privileges (except for the HELP and VERSION commands). This utility can also be activated with the command 'AVTAPEMGR'. Additional information available: Author CREATE DELETE DIRECTORY COPY MOVE LOAD UNLOAD SET SHOW VERSION HELP TAPEMGR Subtopic?
- 29. TapeMGR for OpenVMS 29 $ tapemgr help load TAPEMGR LOAD TAPEMGR LOAD device [filespec] This command will load a virtual tape container file. The filespec must include a full path in unix style (for example "/files/tape.vtape"). The string must be enclosed in quotes. The path must be on a mounted device that is not the system device. If no filespec is given then the file as specified in the emulator's configuration file will be used. The tapeunit may not be mounted for this operation to succeed. Topic?
- 30. TapeMGR for OpenVMS 30 $ tapemgr help unload TAPEMGR UNLOAD TAPEMGR UNLOAD device This command will unload the specified container file in the specified tape device. The tapeunit may not be mounted for this operation to succeed. Topic?
- 31. TapeMGR for OpenVMS 31 $ tapemgr help show TAPEMGR SHOW TAPEMGR SHOW device This command will show information for the specified device. Example: $ TAPEMGR SHOW MKA0: %TAPEMGR-I-INFO, _MKA0: file=/files/tape.vtape format=default maximumsize=unlimited autoload=yes status=unloaded Topic?
- 32. TapeMGR for OpenVMS 32 $ tapemgr help set TAPEMGR SET TAPEMGR SET device This command allows selection of the used tape format for the specified device. It also allows setting autoload compress and the maximum file size. Additional information available: /AUTOLOAD /COMPRESS /FORMAT /MAXIMUMSIZE TAPEMGR SET Subtopic
- 33. TapeMGR for OpenVMS 33 $ tapemgr help set /autoload TAPEMGR SET /AUTOLOAD /AUTOLOAD /NOAUTOLOAD If this qualifier is present then the tape will automatically be loaded and be ready for use. If /NOAUTOLOAD is specified then the tape will not be automatically loaded and needs to be loaded with the TAPEMGR LOAD command. Do not use autoloading with multi-volume backups or small container files since they will be overwritten when a volume switch is needed. Topic?
- 34. TapeMGR for OpenVMS 34 $ tapemgr help set /compress TAPEMGR SET /COMPRESS /COMPRESS /NOCOMPRESS If this qualifier is present then records will be compressed while written to the tape. If /NOCOMPRESS is specified compression will be disabled. Compression status must be set before the tape is initialized. Topic?
- 35. TapeMGR for OpenVMS 35 $ tapemgr help set /format TAPEMGR SET /FORMAT /FORMAT=(DEFAULT,MTD,SMA,LM) The following virtual container file formats are supported: DEFAULT MTD LM SMA Topic?
- 36. TapeMGR for OpenVMS 36 $ tapemgr help set /maximumsize TAPEMGR SET /MAXIMUMSIZE /MAXIMUMSIZE=xxx This qualifier allow specification of the maximum container file size in megabytes. Once this size is reached the virtual drive will return a 'tape full' status which allows a volume switch. Topic?
- 37. TapeMGR for OpenVMS 37 $ tapemgr show mka200: %TAPEMGR-I-INFO, _VMS83$MKA200: file=(none) format=default maximumsize=unlimited autoload=no status=unloaded compression=no $ tape load mka200: "/data/newtapecontainer" $ tape show mka200 %TAPEMGR-I-INFO, _VMS83$MKA200: file=/data/newtapecontainer format=default maximumsize=unlimited autoload=no status=loaded compression=no $ mount mka200:/for %MOUNT-I-MOUNTED, mounted on _VMS83$MKA200: $ backup/image dka0: mka200:dka0.bck/sav /ign=label /rew %BACKUP-I-LBLOVRWRITE, volume label NON-ANSI overwritten, new label is DKA0 $
- 38. TapeMGR for OpenVMS 38 $ dismount mka200: $ tape load mka200: "/data/newtapecontainercompressed" $ tapemgr set /compression mka200: $ tapemgr show mka200: %TAPEMGR-I-INFO, _VMS83$MKA200: file=/data/newtapecontainercompressed format=default maximumsize=unlimited autoload=no status=loaded compression=yes $ mount mka200:/for %MOUNT-I-MOUNTED, mounted on _VMS83$MKA200: $ backup/image dka0: mka200:dka0.bck/sav /ign=label /rew %BACKUP-I-LBLOVRWRITE, volume label NON-ANSI overwritten, new label is DKA0 $ tape dir "/data“ /data/test /data/test2 /data/newtapecontainer /data/newtapecontainercompressed
- 39. TapeMGR for OpenVMS 39 ▪ Easy integration in existing backup scripts ▪ Unattended backups ▪ No more FTPing of savesets ▪ Offsite backups directly to any remote storage ▪ Compatible with LM driver tapeimages
- 40. Thank you OpenVMS professionals and enthusiasts! 40 Look around you Use this forum to connect
- 41. THANK YOU FOR YOUR ATTENTION avtware.com info@avtware.com