How to articles
This blog post will go over the steps to connect FlashArray volumes over iSCSI on RHEL variant Linux systems (RHEL, Oracle Linux, CentOS). Required package on RHEL for iSCSIiscsi-initiator-utils Multipathing packagedevice-mapper-multipath High level process with iSCSI Setup iSCSI at the initiator Setup Host at the FlashArray level Discover the iSCSI targets Create a volume, attach
iSCSI setup with Flasharray Read More »
To preserve the device names across reboots in Linux, udev rules is the recommended option. The idea is to extract SCSI device’s unique ID and assign it to a symbolic name that will persist across reboots. To get the SCSI device’s unique ID, Linux command scsi_id can be used. On VMware, you might run into
Enabling SCSI_ID on VMware Read More »
To create a physical standby database, DBAs generally take an RMAN backup of the primary database, transfer them to the standby system and recover/duplicate them to create the standby database. Based on the size of the database and the distance between the sites where the standby database is created, the backup/restore, as well as transfer, can
Physical Standby database creation using FlashRecover Snapshots Read More »
Most of Pure FlashArray customers use Oracle on ASM or cooked filesystems like EXT4 or XFS. Rarely I do see ZFS and generally, those are Solaris users. Still, I do periodically get questions about ZFS with Pure FlashArray, specifically on database cloning where the database is hosted on FlashArray volumes. Hence, this post is to
Database cloning with ZFS on Pure FlashArray – Part I Read More »
A lot of customers have requested the steps to clone an Oracle database on ASM hosted on Pure FlashArray, on to the same database host like cloning QA database into DEV on the same host. The problem is, cloning an ASM lun and mounting it onto the same host would result in two luns with
Cloning Oracle Database on ASM with Pure FlashArray on to same host Read More »
