AlloyDB Omni

Hardianto Aries Wicaksono

ITOS
PT Astra Graphia Information Technology
Agenda

Overview Product AlloyDB Omni

Comparison Product

Way of Learning AlloyDB Omni

Installation and Basic

Configuration

Preparation for Project

Agenda

OVERVIEW PRODUCT ALLOYDB

OMNI

5
Overview AlloyDB Omni
What is AlloyDB Omni
• containerized image of Google’s AlloyDB database.
• share the same core components with AlloyDB for
PostgreSQL.
• uses the same standard file system interface used by
PostgreSQL.
• doesn't include AlloyDB for PostgreSQL features that rely on
operation in Google Cloud.
• have enterprise and developer version.

What is it use for

• multi-cloud deployments.
• scalable and performant version of PostgreSQL, but can't run
in the cloud.
• keeps running even when it's disconnected from the internet.
• to minimize latency.
• data analytics and machine learning.
Overview AlloyDB Omni
Features
• Higher Transactional Performance
• Integrated Columnar Engine for Fast Analytics
• Advanced Vector Support for Generative AI
• Automatic and Adaptive Memory Management
• AI-Powered Index Recommendations
• AI-powered management and development tools
• Deployment flexibility across various environments
Architecture PostgreSQL
Architecture AlloyDB
Omni
Agenda

Comparison Product

5
PostgreSQL Community vs EnterpriseDB vs
AlloyDB Omni
Features PostgreSQL Community Enterprise DB AlloyDB Omni
faster performance, especially
Performance and
needed optimization Faster performance for transactional and analytical
Scalability
workloads
HTAP (Hybrid
needed configurarion and built-in with columnar engine
Transactional/Analytic not specified main focus
extention addition for fast analytic
al Processing)
Management Self-managed Self and Fully managed Fully-managed by Google Cloud
needed configurarion and
AI Integration not specified built-in built-in with AlloyDB AI
extention (pgvector)
enhanced protection from SQL
needed configurarion and integrated with Google Cloud
Security injections, Row-Level Access
extention addition infrastructure
Control
Deployment on-prem, cloud on-prem, cloud on-prem, cloud (container)
Support and free to use and community enterprise-grade support with enterprise-grade support from
Licensing support multiple SLA Google Cloud with multiple SLA
Agenda

Way of Learning AlloyDB Omni

5
Way of Learning AlloyDB Omni
1. We can use Laptop which specification RAM 16 GB, storage SSD 512 GB, Processor Intel i3 or
more, OS Linux or MacOS.
2. We can use VirtualBox to make Virtual Server in our Computer/Laptop.
3. We can use official documentation of AlloyDB Omni in this link:
https://cloud.google.com/alloydb/omni/16.3.0/docs/overview
4. We can use official documentation of configuration guide AlloyDB Omni in this link:
https://cloud.google.com/static/alloydb/omni/current/docs/pdfs/AlloyDB_Omni_Configuration_G
uide.pdf
5. We can use Gemini AI to know what is AlloyDB Omni.
Agenda

Installation and Basic

Configuration

5
Preparation
AlloyDB Omni minimum requirement:
Preparation
Operating System: Oracle Linux 9.5
Prepare 2 VM(s):

Installation : 192.168.56.10
Username VM : oracle
Password VM : oracleuser
Username DB : postgres
Password DB : postgresadmin

BackupRestore : 192.168.56.20
Username VM : oracle
Password VM : oracleuser
Username DB : postgres
Password DB : postgresadmin
Installation Docker
Engine
1. Set up the repository
$ sudo dnf -y install dnf-plugins-core
$ sudo dnf config-manager --add-repo
https://download.docker.com/linux/rhel/docker-ce.repo

2. Install docker packages

$ sudo dnf install docker-ce docker-ce-cli containerd.io docker-
buildx-plugin docker-compose-plugin

3. Start and Enable Docker Engine

$ sudo systemctl start docker
$ sudo systemctl enable --now docker

4. Verify Docker Engine

$ docker --version
$ sudo docker run hello-world
Installation AlloyDB Omni
1. Run Docker as a non-root user 4. Check if AlloyDB Omni is running
If you want to use Docker without sudo: $ docker ps
$ sudo usermod -aG docker $USER
Then log out and back in or run: 5. Verify the volume
$ newgrp docker $ docker volume ls

2. Pull AlloyDB Omni Docker Image 6. Connect to AlloyDB Omni

$ docker pull google/alloydbomni:16.3.0 $ docker exec -it alloydb-omni psql -h
192.168.56.10 -p 5432 -U postgres
3. Create AlloyDB Omni container
$ docker run -d --name alloydb-omni \ 7. To stop and remove container but keep
-e POSTGRES_PASSWORD=postgresadmin \ data
-v alloydbomni-data:/var/lib/postgresql/data \ $ docker stop alloydb-omni
-p 5432:5432 \ $ docker rm alloydb-omni
--restart=always \
google/alloydbomni:16.3.0
Installation AlloyDB Omni
Connect to AlloyDB Omni via DBeaver
3

2 4
Backup Restore AlloyDB
Omni
Backup and Restore in AlloyDB Omni
Ensure that you have the same major version of PostgreSQL and pgBackRest installed on both
your source and target servers.
$ docker exec CONTAINER_NAME psql -h localhost -U postgres -c "SELECT version();"
$ docker exec CONTAINER_NAME pgbackrest version

Backup AlloyDB Omni

1. Create AlloyDB Omni container
$ docker run -d --name alloydbomni-backup \
-e POSTGRES_PASSWORD=postgresadmin \
-v alloydbomni-data:/var/lib/postgresql/data \
-v alloydbomni-backup:/var/lib/postgresql/backups \
-p 5431:5432 \
--restart=always \
google/alloydbomni:16.3.0
Backup Restore AlloyDB
Omni
2. Create Database and Schema
$ docker exec -it alloydbomni-backup psql -h 192.168.56.20 -p
5431 -U postgres
=# CREATE DATABASE db1;
=# \l
=# \c db1
=# CREATE SCHEMA db1_schema;
=# \dn

3. Make the backups directory, in your container, readable

by postgres
$ docker exec alloydbomni-backup chown -R postgres:postgres
/var/lib/postgresql/backups

4. Make the configuration file pgbackrest.conf in your

container.
$ docker exec -it alloydbomni-backup bash
/# apt install vim
/# vi /var/lib/postgresql/backups/pgbackrest.conf
Backup Restore AlloyDB
Omni
5. Create the stanza using the stanza-create command.
$ docker exec -it -u postgres alloydbomni-backup pgbackrest \
--config-path=/var/lib/postgresql/backups \
--stanza=omni stanza-create \

6. Configure your database for backups

$ docker exec -u postgres alloydbomni-backup psql \
-c "ALTER SYSTEM SET archive_command='pgbackrest --config-
path=/var/lib/postgresql/backups --stanza=omni archive-push
%p';" \
-c "ALTER SYSTEM SET archive_mode=on;" \
-c "ALTER SYSTEM SET max_wal_senders=10;" \
-c "ALTER SYSTEM SET wal_level=replica;“

7. Restart the container

$ docker restart alloydbomni-backup
Backup Restore AlloyDB
Omni
8. Validate the backup configuration 10. Perform a full backup
$ docker exec -u postgres alloydbomni-backup $ docker exec -u postgres alloydbomni-backup
psql \ pgbackrest \
-c "SELECT name, setting --config-path=/var/lib/postgresql/backups \
FROM pg_catalog.pg_settings --stanza=omni \
WHERE name IN ('archive_command', --type=full \
'archive_mode', Backup
'max_wal_senders',
'wal_level') 10. Report backups
ORDER BY name“ $ docker exec -u postgres alloydbomni-backup
pgbackrest \
9. Perform a pgBackRest check (optional) --config-path=/var/lib/postgresql/backups \
$ docker exec -u postgres alloydbomni-backup --stanza=omni \
pgbackrest \ info
--config-path=/var/lib/postgresql/backups \
--stanza=omni \
check
Backup Restore AlloyDB
Omni
Restore AlloyDB Omni 3. Remove your data directory
1. Stop your AlloyDB Omni Backup $ docker exec alloydbomni-idle sh -c "rm -rf
container /var/lib/postgresql/data/*“
$ docker stop alloydbomni-backup
$ docker rm alloydbomni-backup 4. Validate that your backups are visible
$ docker exec -it -u postgres alloydbomni-idle
2. Create idle AlloyDB Omni container pgbackrest \
$ docker run -d --name alloydbomni-idle \ --config-path=/var/lib/postgresql/backups \
-e POSTGRES_PASSWORD=postgresadmin \ --stanza=omni \
-v alloydbomni-data2:/var/lib/postgresql/data \ info
-v
alloydbomni-backup:/var/lib/postgresql/backup 5. Restore your backup
s\ $ docker exec -it -u postgres alloydbomni-idle
-p 5434:5432 \ pgbackrest \
--restart=always \ --config-path=/var/lib/postgresql/backups \
google/alloydbomni:16.3.0 sleep infinity --stanza=omni \
restore
Backup Restore AlloyDB
Omni
6. Remove idle AlloyDB Omni container 9. Validate that AlloyDB Omni started via
$ docker kill alloydbomni-idle log
$ docker rm alloydbomni-idle $ docker exec -it alloydbomni-restore psql -h
192.168.56.20 -p 5433 -U postgres
7. Create AlloyDB Omni container =# \l
$ docker run -d --name alloydbomni-restore \ =# \c db1
-v alloydbomni-data2:/var/lib/postgresql/data \ =# \dn
-v $ docker logs -f alloydbomni-restore
alloydbomni-backup:/var/lib/postgresql/backup
s\
-p 5433:5432 \
--restart=always \
google/alloydbomni:16.3.0

8. Validate that AlloyDB Omni started

$ docker exec -it alloydbomni-restore psql -h
192.168.56.20 -p 5433 -U postgres
Agenda

Preparation for Project

5
Preparation for Project

Plan meeting with BD Google for legal and

license

Plan meeting preparing demo for

OpenText

Plan meeting preparing demo for ERP

Odoo
Plan meeting with BD Google for legal
and license
Preparing Internal for Licensing Model:
1. License Types
• Are there different license types (e.g., standard, enterprise editions, etc.)?
• Features included and not included in each license type.
2. License Renewal and Changes
• The license renewal process.
• What if there are changes to the licensing model in the future?
3. Support and SLA (Service Level Agreement)
• The level of technical support included in the license.
• What's the issue escalation process?
4. License Misuse/Compliance
• Consequences of license misuse or non-compliance.
• Google's audit process for license compliance.
Plan meeting preparing demo for
Opentext
OpenText Preparation:
1. OpenText Licenses and Installation Media
Ensure you have a valid license, installation media, and official installation documentation from OpenText for the
specific product. (e.g., OpenText Content Suite, Extended ECM, or others)
2. Choosing the OpenText Product for Demo
Select one or two OpenText products most relevant to your demo needs.
3. OpenText Prerequisites (Application Server)
Ensure you have VM (Virtual Machine) to host the OpenText application server like Apache Tomcat, WildFly, or
Microsoft IIS.
Plan meeting preparing demo for ERP
Odoo
Basic Understanding of Odoo ERP:
1. Core ERP Concepts
Familiarize yourself with common core modules in Enterprise Resource Planning (ERP).
2. Odoo User Interface
Understand how to navigate within Odoo, how to create transactions, view reports, etc. (watch tutorial videos that
available for free on the Odoo website)
3. Odoo Use Cases
Think about specific business scenarios you'd like to see demonstrated in Odoo.
Reference

https://cloud.google.com/alloydb/omni/16.3.0/docs/overview
https://cloud.google.com/static/alloydb/omni/current/docs/pdfs/
AlloyDB_Omni_Configuration_Guide.pdf
https://docs.docker.com/engine/install/rhel/#install-using-the-reposi
tory
ChatGPT / GeminiAI
Thank
You