Dimitre,
I also work at Microsoft focusing on Oracle with Kellyn.
A few lessons learned...
* For compute, choose /memory-optimized/ VM instance types
o Es_v5 and Eds_v5 are just coming available this week...
o Es_v4 and Eds_v4 have been the default "work horse" VM instance
types for database since last summer
o M-series instance types should be considered only for extremely
high CPU/memory requirements, preferably with Azure NetApp Files
storage only
* For storage, start with /premium SSD/ managed disk
o do not use /standard HDD/ or /standard SSD/ managed disk -- ever
-- for OsDisk or DataDisk with Oracle databases
o advanced options like UltraDisk, Azure NetApp Files, and Silk
should be considered for higher I/O throughput workloads
+ Azure NetApp Files should also be considered when
provisioning a large number of Oracle database VMs to take
advantage of a capacity pool
+ Azure NetApp Files and Silk should be considered for very
low I/O latency coupled with very high I/O throughput demands
o For premium SSD...
+ enable ReadOnly host-caching on managed disk underlying
Oracle datafiles, tempfiles, controlfiles, BFILEs, external
table files, block-change tracking (BCT) files, and
flashback log files
+ disable host-caching on managed disk underlying Oracle
online redo log files
* For database files, use /Oracle ASM with udev/ or use /LVM2 with
XFS/EXT4 filesystems/
o as preferred -- this is an old debate within Oracle
* For backups, please consider using /storage-level snapshots/ using
/Azure VM Backups/ or /Azure NetApp Files/
o snapshots are copied off to a Recovery Vault for subsequent
restore or clone operations
o /streaming backups using RMAN/ are of course fully supported,
just less preferable than snapshots
* For archived redo log files, please consider using Azure Files
shares or Azure NetApp Files shares
o works well especially in conjunction with Azure VM Backups
o snapshots are copied off to a Recovery Vault for subsequent
restore or clone operations
There are all kinds of lessons learned to share in the area of data
protection, high-availability, and disaster-resilience as well, but
these are the basics.
Hope this helps!
-Tim
On 5/7/2021 4:54 AM, Radoulov, Dimitre wrote:
Thank you very much Mike!
I'm aware, of course, that Kellyn Potvin contributes to oracle-l and thanks for mentioning her blog, I'll check the Azure related posts.
I know that we're supposed to patch our instances by ourselves just like we do on prem.
As a side note: we have a huge number of cloud managed databases on Google and the fact that all the backup and patching related stuff is handled by Google is really great (just like the other cloud vendors database managed solutions, I suppose).
Best regards
Dimitre
On 07/05/2021 13.40, Michael Gangler wrote:
Hi Dimitre,--
Kellyn Potvin-Gorman who use to work for Oracle and is now works for Microsoft and is the Oracle SME for Azure, has provided great information on setting up Oracle on Azure. I was able to setup a couple Oracle instances and it works great. Please note, though, Oracle in Azure is more IAAS so many of the items such as Oracle patching, etc. will have to be done by you. Her Blog is : https://dbakevlar.com/about/
Kellyn also follows this site and I'm sure she will also provide more expert than myself. Overall, worked like a charm, good performance and pretty straight forward install.
--Mike
Thank You,
Mike
mike@xxxxxxxxxxx
On 5/7/21, 6:40 AM, "Radoulov, Dimitre" <oracle-l-bounce@xxxxxxxxxxxxx on behalf of cichomitiko@xxxxxxxxx> wrote:
Hello all,
we have to set up Oracle database on MS Azure. I'm reading various
articles/blog posts on Internet and try to choose the best options for us.
If I understand correctly the licensing is different (one processor
license covers one virtual core, thus the Intel core factor doesn't apply).
RAC isn't supported, but you can deploy Data Guard as HA, and eventually
DR (on a different region), solution.
We definitely need to patch OS and databases on a regular basis.
We currently don't use the multitentant option, but I suppose that we'll
need to switch to it because the single tenant will be deprecated.
I don't believe ASM would be more appropriate than XFS with
filesystemio_options set to setall for a single instance.
It would be really great if you could share your experience, suggestions
and new "best practices" for running an enterprise grade Oracle database
on non-Oracle public cloud.
Thanks in advance!
Best regards
Dimitre
--
//www.freelists.org/webpage/oracle-l
//www.freelists.org/webpage/oracle-l
