Maris,
Thanks for the info. A follow up question, you mentioned that you take
snapshot for cloning, as the volumes you are using are already stripped.
Are you creating an image (AMI) or snapshot of individual volume.
Reason why i ask is, if you are taking snapshot of individual volumes(which
are stripped) then restoring it, is that working alright ?? I want to see
how the restore of the snapshot is work when volumes are stripped ...
On Mon, Jan 11, 2016 at 9:29 AM, Maris Elsins <elmaris@xxxxxxxxx> wrote:
Hi,
We're running a configuration that addresses some of your IOPS concerns
and it's basically one of the architectures from this whitepaper
https://d0.awsstatic.com/whitepapers/aws-advanced-architectures-for-oracle-db-on-ec2.pdf
- We have created our EC2 for Oracle DBs using Oracle Linux 6 (requirement
for Oracle Smart Flash Cache)
- We've set up ASM on multiple provisioned IOPS EBS volumes (SSD) for
striping
- We've enabled Oracle Smart Flash Cache on part of the ephemeral instance
store SSD (it doesn't have even the tiny network latency that EBS volumes
have, as they are local). And based on the AWR reports we see this works
very well. And in fact with larger EC2 instances one gets plenty of
instance store SSDs that otherwise are of no big use.)
- We don't rely on EBS volumes' snapshots for backups, as we have a
DataGuard set up and when needed we stop the recovery there and take
snapshots from it (for cloning purposes usually). I'd think this would also
work with "ALTER DATABASE BEGIN/END BACKUP" + simultaneous snapshot of all
striped EBS volumes too.
- We take regular RMAN backups for point in time recovery requirements.
May be this is not exactly what you were looking for as you provided a
link related to RAID configurations, but probably you can still extract
something useful from what I wrote.
regards,
---
Maris Elsins
@MarisElsins <https://twitter.com/MarisElsins>
www.facebook.com/maris.elsins
On Mon, Jan 11, 2016 at 4:44 PM, max scalf <oracle.blog3@xxxxxxxxx> wrote:
Hello all,
This question is related to running oracle database on Amazon Web
Service. Just so i respect everyone's time on here, I would say please
ignore this question if you do not work with AWS.
We are running oracle some 11g and 12c database on AWS EC2 server. Most
of the server have anywhere from 2 -8 EBS Volume attached(general purpose
SSD), they are NOT striped or mirrored. Lately we have been seeing some
performance issue(year end closing) with high IO wait time(60-80 ms per
read), for some mission critical application we have moved the EBS volumes
from general purpose SSD to Provisioned IOPS(PIOPS) and everything seems
happy. But now we are coming back to some of the other application and our
sysadmin says instead of moving everything from general purpose volumes to
PIOPS we should just strip the volumes to get better performance.
I agree with him, but my question if we were to strip the EBS volumes how
do we deal with taking EBS Snapshot and managing them. We rely on them for
our DR in another region. From what i understand about taking snapshot
when your EBS volumes are stripped is that you have to freeze the IO before
you do the snapshot to guarantee EBS snapshot consistency, see below link..
https://aws.amazon.com/premiumsupport/knowledge-center/snapshot-ebs-raid-array/
So i wanted to see what others are doing in the community
to achieve higher IOPS and i am sure quite a few ppl are running oracle on
AWS and also I wanted to find out when they say "Freeze IO", I am assuming
putting database in HOT BACKUP mode is the wrong thing.
