Looking forward to the fourth edition of Pure//Accelerate conference that is packed with over 100 breakout sessions. This year Accelerate conference is held at the Austin Convention Center, Austin, TX between Sep 16th and 18th. This year I am very happy to present a breakout session on Splunk under the content type, Build a Data …
Get ready for the 4th edition of PURE//ACCELERATE Read More »
Most of Pure FlashArray customers are used to the snapshot functionality that helps them in taking either a crash-consistent or application-consistent snapshot in a flash (literally and figuratively) irrespective of the database size. While this helps them in protecting the database from any accidental changes or creating clones for development and test usage but cannot …
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 …
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 …
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 »
