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
RMAN Backups using mount host on Flasharray 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 »
Update (Aug 9th 2017): The Purity version with VVols integration is available starting 5.0 which is in beta currently. Check out our support website (support.purestorage.com) for Purity 5.0 availability. There has been lot of talks about VVols and how the storage vendors are implementing it. I am not a VMware vExpert and this blog post
Oracle Database cloning using VVols Read More »
As explained in my earlier post Pure FlashRecover Snapshots is one of the most used features within Purity by our customers who use these snapshots to clone their databases. In case of filesystems, the volumes that are cloned may even be part of LVM (Logical Volume Manager). In Linux world, when volume(s) part of LVM is
Cloning LVM volumes using Pure FlashRecover Snapshots Read More »
My earlier post Online resizing of Oracle volumes on Pure FlashArray was focused on resizing Pure FlashArray volumes that were mounted directly or through Oracle ASM. What if the volume is part of LVM and you wanted to extend the size of a logical volume? Disclaimer: Even though the following sequence of steps were validated in
Extending (root) volume on LVM on Pure FlashArray Read More »
