Streaming replication in PostgreSQL

Jun 3, 2014Download as PPTX, PDF3 likes1,885 views

This document provides instructions for setting up hot standby replication between a primary and secondary PostgreSQL database. It describes configuring WAL archiving on the primary, taking a backup of the primary to initialize the secondary, creating a recovery.conf file on the secondary, and testing replication. It also explains how to trigger a failover, switchover, and rebuild the primary database after a failover.

Hot Stand By
Setup, Failover and Rebuilding the Master
3/6/2014

Confidentialinformation,forinternaluseonly
Prepare the Instance
 Install Postgres on Servers which are going to hold Primary and Secondary
database
 Setup and configure the database cluster on Primary servers
 In this example:
 Primary DB Server:
 dbserver1
 192.168.160.147
 Data directory: /opt/PostgresPlus/9.2AS/data
 Port: 5444
 Stand by DB Server
 dbserver2
 192.168.160.150
 Data Directory: /opt/PostgresPlus/9.2AS/data2
 Port: 5222
2

Confidentialinformation,forinternaluseonly
Edit postgresql.conf and pg_hba.conf on
master
 wal_level = hot_standby (mandatory)
 max_wal_senders = 3 (mandatory to be set to a positive integer)
 wal_keep_segments = 128 (optional/depending on load)
 replication_timeout = 5 sec (optional)
 hot_standby = on (effective only for hot stand by server)
Add entry in pg_hba.conf
• host replication all 192.168.0.0/16 trust
3

Confidentialinformation,forinternaluseonly
Take a Backup and restore on Secondary
 Take a cold backup of Primary DB Instance/Cluster
 Restore the same for creating the DB cluster/instance on
Secondary server
4

Confidentialinformation,forinternaluseonly
Create recovery.conf in Secondary Server
 standby_mode = 'on'
 primary_conninfo = 'host=192.168.160.147 port=5444 user=enterprisedb
password=ashnik'
 restore_command = 'scp enterprisedb@192.168.160.147:/mnt/arch/%f %p'
# optional
# needs archiving command to be enabled on primary
 recovery_target_timeline = 'latest' #optional
 trigger_file = '/opt/PostgresPlus/9.2AS/data2/recover.trigger'
5

Confidentialinformation,forinternaluseonly
Start the servers
 Start the secondary server
 There will be a warning in log files that primary server is not
available, ignore that
 Start the primary server
6

Confidentialinformation,forinternaluseonly
Test Replication
On Primary:
edb=# insert into replication_test values (2);
INSERT 0 1
On Secondary:
edb=# select * from replication_test;
test_column
-------------
1
2
(2 rows)
Secondary server is read-only:
edb=# insert into replication_test values (3);
ERROR: cannot execute INSERT in a read-only transaction
7

$Confidentialinformation,forinternaluseonly Triggering the Failover  To, Trigger a failure on Primary and create the recovery trigger file (manually, but can be scripted too) touch opt/PostgresPlus/9.2AS/data2/recover.trigger  Logic to script the above step: while( pg_ctl -h 192.168.160.147 –p 5444 -c "select 1 “) { ; #do nothing } touch opt/PostgresPlus/9.2AS/data2/recover.trigger  Once completed, the recovery.conf will change to recover.done  Connect to secondary db and execute insert to confirm the failover edb=# insert into replication_test values (4); INSERT 0 1 Or execute select pg_is_in_recovery(); (output must be “f”) to confirm recovery is completed  Point the database/Virtual IP to new database server 8$

Confidentialinformation,forinternaluseonly
Triggering the Switchover
 Disconnect all the application from Primary Node
 Shutdown the primary database
 To, Trigger a failure on Primary and create the recovery trigger file
touch opt/PostgresPlus/9.2AS/data2/recover.trigger
 Once completed, the recovery.conf will change to recover.done
 Connect to secondary db and execute insert
edb=# insert into replication_test values (4);
INSERT 0 1
Or execute select pg_is_in_recovery(); (output must be “f”) to confirm recovery is completed
 Point the database/Virtual IP to new database server
9

Confidentialinformation,forinternaluseonly
Rebuilding the Master
 Let’s remove the data directory on Old Primary (dbserver1)
rm -Rf /opt/PostgresPlus/9.2AS/data
 Restore the primary server from Secondary server (Switched to Master
now: dbserver2):
pg_basebackup -D /opt/PostgresPlus/9.2AS/data -h 192.168.160.150 -W -p 5222 -Fp --xlog-method=stream
#This step does not need down time
 Change the port number in postgresql.conf on restored data directory
 Change the recovery.done to recovery.conf in data directory copied just
now and make changes in configuration to point to new master
 Start the old primary instance as new hot standby
10

Confidentialinformation,forinternaluseonly
Monitoring the Replication
Check if the current node is master or slave:
• SELECT pg_is_in_recovery();
See the current snapshot on master and slave:
• SELECT txid_current_snapshot();
11

12
Sameer Kumar
Ashnik Pte Ltd, Singapore
www.ashnik.com | sameer.kumar@ashnik.com

This document discusses setting up streaming replication in PostgreSQL v9.3 to enable high availability. It covers preparing primary and standby servers, configuring wal_level and max_wal_senders on the primary, taking a backup and restoring on the standby, creating a recovery.conf file, starting the servers to test replication, triggering failover by promoting the standby, handling multiple replicas without rebuilding, and rebuilding the original primary as a new standby. Monitoring replication status is also addressed using views like pg_stat_replication.

PostgreSQL Hangout Replication Features v9.4Ashnikbiz

Out of the box replication in postgres 9.4Denish Patel

This document provides an overview of setting up out of the box replication in PostgreSQL 9.4 without third party tools. It discusses write-ahead logs (WAL), replication slots, pg_basebackup, and pg_receivexlog. The document then demonstrates setting up replication on VMs with pg_basebackup to initialize a standby server, configuration of primary and standby servers, and monitoring of replication.

PostgreSQL Streaming Replication CheatsheetAlexey Lesovsky

The document provides configuration instructions and guidelines for setting up streaming replication between a PostgreSQL master and standby server, including setting parameter values for wal_level, max_wal_senders, wal_keep_segments, creating a dedicated replication role, using pg_basebackup to initialize the standby, and various recovery target options to control the standby's behavior. It also discusses synchronous replication using replication slots and monitoring the replication process on both the master and standby servers.

Out of the box replication in postgres 9.4(pg confus)Denish Patel

This document contains notes from a presentation on PostgreSQL replication. It discusses write-ahead logs (WAL), replication history in PostgreSQL from versions 7.0 to 9.4, how to set up basic replication, tools for backups and monitoring replication, and demonstrates setting up replication without third party tools using pg_basebackup, replication slots, and pg_receivexlog. It also includes contact information for the presenter and an invitation to join the PostgreSQL Slack channel.

Ilya Kosmodemiansky - An ultimate guide to upgrading your PostgreSQL installa...PostgreSQL-Consulting

Even an experienced PostgreSQL DBA can not always say that upgrading between major versions of Postgres is an easy task, especially if there are some special requirements, such as downtime limitations or if something goes wrong. For less experienced DBAs anything more complex than dump/restore can be frustrating. In this talk I will describe why we need a special procedure to upgrade between major versions, how that can be achieved and what sort of problems can occur. I will review all possible ways to upgrade your cluster from classical pg_upgrade to old-school slony or modern methods like logical replication. For all approaches, I will give a brief explanation how it works (limited by the scope of this talk of course), examples how to perform upgrade and some advice on potentially problematic steps. Besides I will touch upon such topics as integration of upgrade tools and procedures with other software — connection brokers, operating system package managers, automation tools, etc. This talk would not be complete if I do not cover cases when something goes wrong and how to deal with such cases.

Streaming replication in practiceAlexey Lesovsky

This document discusses streaming replication in PostgreSQL. It covers how streaming replication works, including the write-ahead log and replication processes. It also discusses setting up replication between a primary and standby server, including configuring the servers and verifying replication is working properly. Monitoring replication is discussed along with views and functions for checking replication status. Maintenance tasks like adding or removing standbys and pausing replication are also mentioned.

Countdown to PostgreSQL v9.5 - Foriegn Tables can be part of Inheritance Tree Ashnikbiz

Distributed databases and horizontal scale up is one of the key demands in today's date. PostgreSQL already had some vertical scaling features and horizontal scale-up by adding disks and table partitioning/child tables. With release of v9.5, PostgreSQL will get basic foundation for native sharing capability. From v9.5 Foreign Tables will be able to participate in Inheritance Tree as a child or parent table i.e. one can have table partitions residing on different system. In our countdown to v9.5 series of hangouts, we will be covering some of the great features of PostgreSQL v9.5 and what is their real life applicability. In the first hangout in this series we will be talking about- - The feature of foreign partitions/child tables - Syntax and usage - EXPLAIN plan demo - Use cases and benefits Join us for more and send us your queries on [email protected]

PostgreSQL Replication in 10 Minutes - SCALEPostgreSQL Experts, Inc.

This document summarizes a presentation about PostgreSQL replication. It discusses different replication terms like master/slave and primary/secondary. It also covers replication mechanisms like statement-based and binary replication. The document outlines how to configure and administer replication through files like postgresql.conf and recovery.conf. It discusses managing replication including failover, failback, remastering and replication lag. It also covers synchronous replication and cascading replication setups.

Advanced Postgres MonitoringDenish Patel

This document discusses advanced Postgres monitoring. It begins with an introduction of the speaker and an agenda for the discussion. It then covers selection criteria for monitoring solutions, compares open source and SAAS monitoring options, and provides examples of collecting specific Postgres metrics using CollectD. It also discusses alerting, handling monitoring changes, and being prepared to respond to incidents outside of normal hours.

PostgreSQL Replication High Availability MethodsMydbops

PostgreSQL WAL for DBAs PGConf APAC

Devrim Gunduz gives a presentation on Write-Ahead Logging (WAL) in PostgreSQL. WAL logs all transactions to files called write-ahead logs (WAL files) before changes are written to data files. This allows for crash recovery by replaying WAL files. WAL files are used for replication, backup, and point-in-time recovery (PITR) by replaying WAL files to restore the database to a previous state. Checkpoints write all dirty shared buffers to disk and update the pg_control file with the checkpoint location.

Logical replication with pglogicalUmair Shahid

This document discusses logical replication with pglogical. It begins by explaining that pglogical performs row-oriented replication and outputs replication data that can be used in various ways. It then covers the architectures of standalone PostgreSQL, physical replication, and logical replication. The rest of the document discusses key aspects of pglogical such as its output plugin, selective replication capabilities, performance and future plans, and examples of using the output with other applications.

What is new in PostgreSQL 14?Mydbops

Evolution of MongoDB Replicaset and Its Best PracticesMydbops

Logical Replication in PostgreSQL - FLOSSUK 2016Petr Jelinek

pgDay Asia 2016 - Swapping Pacemaker-Corosync for repmgr (1)Wei Shan Ang

The document discusses alternatives to Pacemaker/Corosync for managing high availability PostgreSQL clusters. It introduces pg_bouncer for connection pooling, Linux's UCARP for virtual IP failover, and 2ndQuadrant's repmgr for managing replication and automatic failover. It notes the challenges with Pacemaker/Corosync and provides an agenda that includes an introduction, challenges with Pacemaker/Corosync, discussing pg_bouncer, UCARP, repmgr, and a demo. Logs from Pacemaker/Corosync are also included showing failed operations and failover.

PostgreSQL Performance Tuningelliando dias

Basics of Logical Replication,Streaming replication vs Logical Replication ,U...Rajni Baliyan

This document provides an overview of logical replication in PostgreSQL 10. It discusses the history of PostgreSQL replication, the key concepts of logical replication including publications, subscriptions, and replication slots. It presents several use cases for logical replication such as cross-platform, cross-version, and write operations at the subscriber. The document also covers configuration settings, a quick setup demonstration, monitoring, resolving conflicts, and limitations of logical replication.

Case Studies on PostgreSQLInMobi Technology

plProxy, pgBouncer, pgBalancerelliando dias

GitLab PostgresMortem: Lessons LearnedAlexey Lesovsky

1. A PostgreSQL database outage occurred at GitLab on January 31st due to a combination of factors including an increase in load, replication lag, and the deletion of the database directory. 2. Lessons learned include monitoring replication, using tools like pg_basebackup properly, and having backups and disaster recovery processes in place. 3. Recommended preventative measures include setting sane configuration values, automated testing of backups, assigning an owner for data durability, and improving documentation.

GOTO 2013: Why Zalando trusts in PostgreSQLHenning Jacobs

NoSQL is on the rise but sadly when people compare the usual NoSQL candidates (Redis, MongoDB, Riak, Cassandra, HBase, ..) to relational databases they often only mention MySQL. In our presentation we tried to explain the power of the world’s most advanced opensource database - PostgreSQL. In our session we showed various examples of why we at Zalando trust PostgreSQL to reliably handle all our data. We make use of it in various scenarios, from less complex CRUD applications on a single node, to highly critical and more complex scenarios. This involves customer and order data with strong constraints for high performance and availability, sharded across multiple nodes. We believe that PostgreSQL is massively underrated and that you should have very good reasons to ignore its great features.

Building Spark as Service in CloudInMobi Technology

This document summarizes Spark as a service on YARN clusters and discusses key features: - Spark on YARN allows running multiple workflows like Spark and Hadoop on the same cluster and improves resource utilization. The application master can dynamically request more containers as needed. - Qubole YARN clusters support autoscaling to upscale and downscale based on load and use spot instances for cost savings. - Spark applications were limited by initial resource allocation. Dynamic provisioning allows applications to request more executors or release unused executors to improve performance and cluster utilization.

PostgreSQL and RAM usageAlexey Bashtanov

PostgreSQL High Availability in a Containerized WorldJignesh Shah

This document discusses PostgreSQL high availability in a containerized environment. It begins with an overview of containers and their advantages like lower footprint and density. It then covers enterprise needs for high availability like recovery time objectives. Common approaches to PostgreSQL high availability are discussed like replication, shared storage, and using projects like Patroni and Stolon. Modern trends with containers are highlighted like separating data and binaries. Kubernetes is presented as a production-grade orchestrator that can provide horizontal scaling and self-healing capabilities. The discussion concludes with challenges of multi-region deployments and how service discovery with Consul can help address those challenges.

SQL Server vs Postgreschandra sekhar pathivada , PMP,ITIL,MCTS

This document provides an overview of key differences between SQL Server and PostgreSQL databases. It covers topics such as extensions, cost, case sensitivity, operating systems, processor configuration, write-ahead logging (WAL), checkpoints, disabling writes, page corruptions, MVCC, vacuum, database snapshots, system databases, tables, indexes, statistics, triggers, functions, security, backups, replication, imports/exports, maintenance, and monitoring. The document aims to help SQL Server DBAs understand how to administer and work with PostgreSQL databases.

Best Practices: Migrating a Postgres Production Database to the CloudEDB

How to Replicate PostgreSQL DatabaseSangJin Kang

This document provides an overview of replicating a PostgreSQL database. It discusses setting up a primary server for reads and writes and standby servers that are kept in sync with the primary to serve as backups. The primary server writes data to its write-ahead log (WAL) files, which are streamed in real-time to the standby servers via WAL shipping. This allows the standby servers to keep an identical copy of the database. The document also covers configuration of both the primary and standby servers for replication as well as tools for testing the replication setup.

oracle upgradationinfluxbob

This document provides step-by-step instructions for upgrading an Oracle database from version 10.2.0.4 to 11.2.0.2. It involves running pre-upgrade checks, backing up the database, setting environment variables to point to the new Oracle home, running upgrade scripts to upgrade the database, and performing post-upgrade tasks like recompiling objects and checking for errors. The process ensures the integrity and consistency of the upgraded Oracle software.

More Related Content

What's hot (19)

PostgreSQL Replication in 10 Minutes - SCALEPostgreSQL Experts, Inc.

Advanced Postgres MonitoringDenish Patel

PostgreSQL Replication High Availability MethodsMydbops

PostgreSQL WAL for DBAs PGConf APAC

Logical replication with pglogicalUmair Shahid

What is new in PostgreSQL 14?Mydbops

Evolution of MongoDB Replicaset and Its Best PracticesMydbops

Logical Replication in PostgreSQL - FLOSSUK 2016Petr Jelinek

pgDay Asia 2016 - Swapping Pacemaker-Corosync for repmgr (1)Wei Shan Ang

PostgreSQL Performance Tuningelliando dias

Basics of Logical Replication,Streaming replication vs Logical Replication ,U...Rajni Baliyan

Case Studies on PostgreSQLInMobi Technology

plProxy, pgBouncer, pgBalancerelliando dias

GitLab PostgresMortem: Lessons LearnedAlexey Lesovsky

GOTO 2013: Why Zalando trusts in PostgreSQLHenning Jacobs

Building Spark as Service in CloudInMobi Technology

PostgreSQL and RAM usageAlexey Bashtanov

PostgreSQL High Availability in a Containerized WorldJignesh Shah

SQL Server vs Postgreschandra sekhar pathivada , PMP,ITIL,MCTS

PostgreSQL Replication in 10 Minutes - SCALEPostgreSQL Experts, Inc.

Advanced Postgres MonitoringDenish Patel

PostgreSQL Replication High Availability MethodsMydbops

PostgreSQL WAL for DBAs PGConf APAC

Logical replication with pglogicalUmair Shahid

What is new in PostgreSQL 14?Mydbops

Evolution of MongoDB Replicaset and Its Best PracticesMydbops

Logical Replication in PostgreSQL - FLOSSUK 2016Petr Jelinek

pgDay Asia 2016 - Swapping Pacemaker-Corosync for repmgr (1)Wei Shan Ang

PostgreSQL Performance Tuningelliando dias

Basics of Logical Replication,Streaming replication vs Logical Replication ,U...Rajni Baliyan

Case Studies on PostgreSQLInMobi Technology

plProxy, pgBouncer, pgBalancerelliando dias

GitLab PostgresMortem: Lessons LearnedAlexey Lesovsky

GOTO 2013: Why Zalando trusts in PostgreSQLHenning Jacobs

Building Spark as Service in CloudInMobi Technology

PostgreSQL and RAM usageAlexey Bashtanov

PostgreSQL High Availability in a Containerized WorldJignesh Shah

SQL Server vs Postgreschandra sekhar pathivada , PMP,ITIL,MCTS

Similar to Streaming replication in PostgreSQL (20)

Best Practices: Migrating a Postgres Production Database to the CloudEDB

How to Replicate PostgreSQL DatabaseSangJin Kang

oracle upgradationinfluxbob

Document Management: Opendocman and LAMP installation on Cent OSSiddharth Ram Dinesh

This document provides instructions for installing LAMP (Linux, Apache, MySQL/MariaDB, PHP), phpMyAdmin, and OpenDocMan on CentOS 7. It describes how to install each component, configure the required settings, and set permissions and firewall rules. It also provides steps for restoring an OpenDocMan installation to another server by dumping and importing the MySQL database, transferring files via tar/scp, and adjusting configuration files.

Creating a physical standby database 11g on windowsRoo Wall

This document describes the steps to create a physical standby database including: 1. Configuring the primary and standby databases with the same Oracle version and opening the primary in archive log mode. 2. Setting up Oracle Net components and testing connectivity between the databases. 3. Enabling archive logging and log shipping on the primary and duplicating or copying the primary database to the standby. 4. Recovering the standby database and opening it in read-only mode to synchronize the data.

Database upgradationsantosh kodandapani

PuppetConf 2016: An Introduction to Measuring and Tuning PE Performance – Cha...Puppet

This document provides an overview of measuring and tuning performance for the Puppet Enterprise (PE) platform. It discusses gathering data from PE services like Puppet Server and PuppetDB through JVM logging, metrics, and configurations. Important metrics for Puppet Server include JRuby usage and catalog compilation times. Tuning options involve adjusting JRuby capacity and rebalancing agent checkins. The document also covers monitoring PuppetDB for storage usage and command processing, as well as optimizing PostgreSQL query performance.

Out of the Box Replication in Postgres 9.4(PgConfUS)Denish Patel

This document contains notes from a presentation on PostgreSQL replication. It discusses write-ahead logs (WAL), replication history in PostgreSQL from versions 7.0 to 9.4, how to set up basic replication, tools for backups and monitoring replication, and demonstrates setting up replication without third party tools using pg_basebackup, replication slots, and pg_receivexlog. Contact information is provided for the presenter and information on their employer, Medallia, is included at the end.

Automating Disaster Recovery PostgreSQLNina Kaufman

Upgrading 11i E-business Suite to R12 E-business SuiteiWare Logic Technologies Pvt. Ltd.

The document provides information on upgrading Oracle E-Business Suite Release 11i to Release 12, including planning, preparing, performing the upgrade, and post-upgrade tasks. Key steps include applying the latest 11i patches, running the TUMS utility, upgrading the database to at least Oracle 10g Release 2, laying down the new Release 12 technology stack, and running the upgrade driver to migrate the applications to Release 12. The document outlines important tasks for each phase of the upgrade process.

Cake phpJyotisankar Pradhan

CakePHP is an open-source PHP framework used for developing web applications. The document outlines how to install CakePHP using Composer, create a project, configure databases, implement CRUD functionality, use caching, and deploy applications. Key aspects include using Composer to install dependencies, setting the database connection in config/app.php, generating controllers and models with bake, and clearing cache groups when data changes.

Cloning Oracle EBS R12: A Step by Step ProcedureOrazer Technologies

The document provides steps for cloning an Oracle EBS R12 environment from a source (PROD) system to a target (TEST) system. Key steps include: 1. Backing up files and databases from the source including applications files, database parameter files, and database backups. 2. Copying the backed up files to the target system and modifying configuration files to point to the target system. 3. Restoring and recovering the database on the target system using RMAN and modifying datafile names. 4. Running scripts to clone the application tier files and configure the applications. 5. Performing post-clone tasks like dropping and recreating temp tablespaces and cleaning up configuration.

The Magic of Hot Streaming Replication, Bruce MomjianFuenteovejuna

This document discusses PostgreSQL 9.0's new capabilities for maintaining a current standby server and issuing read-only queries on the standby server. It covers how to configure continuous archiving from the primary server to the standby, and how to configure the standby for streaming replication so it can accept queries. The summary demonstrates streaming replication by creating and inserting a row on the primary which then appears on the standby.

Install Oracle 12c Golden Gate On Oracle LinuxArun Sharma

In this article we will look at the steps to install oracle 12c Golden Gate on Oracle Enterprise Linux 6.5. The steps involved are: Virtual Machine Setup Install Oracle 12c Database Install Oracle 12c Golden Gate Prepare Golden Gate for Replication Here is the full link of article: https://www.support.dbagenesis.com/post/install-oracle-12c-golden-gate-on-oracle-linux

Oracle 11g Installation With ASM and Data Guard SetupArun Sharma

Out of the Box Replication in Postgres 9.4(PgCon)Denish Patel

The document provides an overview of out-of-the-box replication in PostgreSQL 9.4. It discusses PostgreSQL write-ahead logging (WAL), setting up basic streaming replication between a primary and standby server, taking base backups with pg_basebackup, and using replication slots and pg_receivexlog to archive WAL files without external tools. The presentation includes steps to set up a demo of this replication method on a virtual machine.

Out of the Box Replication in Postgres 9.4(PgCon)Denish Patel

This document provides an overview of setting up out of the box replication in PostgreSQL 9.4 without third party tools. It discusses write-ahead logs (WAL), replication slots, pg_basebackup, pg_receivexlog and monitoring replication. The presenter then demonstrates setting up replication on VMs with pg_basebackup to initialize a standby, configuration of primary and standby servers, and monitoring replication status.

Upgrading hadoopShashwat Shriparv

Oracle-12cData-Guard-Broker-Session-4.pptxnaveencl4

Oracle Data GuardMartin Meyer

This document discusses Oracle Data Guard and its capabilities for disaster recovery and high availability. It provides an overview of different types of database protection modes in Data Guard including maximum protection, maximum availability, and maximum performance modes. It also covers key Data Guard concepts like physical and logical standby databases, redo transport, log apply services, and role transitions like switchover and failover. The document demonstrates how to configure a basic Data Guard configuration with a primary and physical standby database and enable fast-start failover for automated, zero data loss failover.

Best Practices: Migrating a Postgres Production Database to the CloudEDB

How to Replicate PostgreSQL DatabaseSangJin Kang

oracle upgradationinfluxbob

Document Management: Opendocman and LAMP installation on Cent OSSiddharth Ram Dinesh

Creating a physical standby database 11g on windowsRoo Wall

Database upgradationsantosh kodandapani

PuppetConf 2016: An Introduction to Measuring and Tuning PE Performance – Cha...Puppet

Out of the Box Replication in Postgres 9.4(PgConfUS)Denish Patel

Automating Disaster Recovery PostgreSQLNina Kaufman

Upgrading 11i E-business Suite to R12 E-business SuiteiWare Logic Technologies Pvt. Ltd.

Cake phpJyotisankar Pradhan

Cloning Oracle EBS R12: A Step by Step ProcedureOrazer Technologies

The Magic of Hot Streaming Replication, Bruce MomjianFuenteovejuna

Install Oracle 12c Golden Gate On Oracle LinuxArun Sharma

Oracle 11g Installation With ASM and Data Guard SetupArun Sharma

Out of the Box Replication in Postgres 9.4(PgCon)Denish Patel

Upgrading hadoopShashwat Shriparv

Oracle-12cData-Guard-Broker-Session-4.pptxnaveencl4

Oracle Data GuardMartin Meyer

More from Ashnikbiz (20)

CloudOps_tool.pptxAshnikbiz

Webinar_CloudOps final.pptxAshnikbiz

Database automation tools are needed to automate repetitive tasks, reduce risks from manual errors, improve alignment between business and IT, and allow organizations to move faster. They help keep systems running smoothly through monitoring, provisioning, backup/restore, maintenance, security, and more. When choosing a tool, organizations should consider ease of implementation, breadth of use cases covered, ability to work on-premises and in the cloud, long-term costs, customizability, learning curve, and do a trial run.

Autoscaling in Kubernetes (K8s)Ashnikbiz

Autoscaling in Kubernetes allows applications to automatically scale resources up or down based on metrics like CPU usage. It addresses challenges with traditional autoscaling approaches by being platform independent and scaling pods quickly using the Horizontal Pod Autoscaler. The document outlines an architecture that sets autoscaling to increase application pods when CPU usage crosses 50%, with a minimum of 1 and maximum of 3 pods. It then demonstrates this through scenarios of idle and heavy loads, ramping up users over 10 seconds to test the autoscaling capabilities.

Why and how to use Kubernetes for scaling of your multi-tier (n-tier) appli...Ashnikbiz

Kubernetes can be used to scale multi-tier applications by providing tools for container orchestration, including service discovery, load balancing, storage orchestration, and self-healing capabilities. It addresses challenges with traditional monolithic architectures by allowing microservices that are isolated, declarative, and can autoscale horizontally and vertically through features like horizontal pod autoscaling, vertical pod autoscaling, and cluster autoscaling. This allows applications to dynamically add or remove pods and nodes as needed to meet changing workload demands.

Zero trust in a multi tenant environment Ashnikbiz

Vault provides secure multi-tenancy by allowing the creation of namespaces that isolate "Vaults within a Vault". Each namespace can have independent authentication methods, secret engines, policies, identities and access management. Vault also enables API-driven encryption through secret engines like Transit and unified identities across multiple environments through its identity system. These capabilities allow Vault to securely store, restrict access to, and manage encryption of secrets and keys for multi-tenant infrastructure.

Deploy and automate ‘Secrets Management’ for a multi-cloud environmentAshnikbiz

Over the years, there has been a massive transition from on-premise environments to hybrid or multi-cloud, resulting in a significant increase in the adoption of cloud-native practices and technologies. However, while cloud-native methodologies offer growing benefits and are instrumental to digitalization, they can pose considerable challenges in managing secrets. Secrets management aims to solve a lack of visibility and control on handling these highly-trusted credentials.

Deploy, move and manage Postgres across cloud platformsAshnikbiz

Running applications in a hybrid set-up creates complexities that can increase downtime and maintenance. PostgreSQL runs across virtual, cloud, and container environments; minimizing complexity without sacrificing the performance, so you can take control. Being today’s undisputed leader of relational databases for new and modern applications, Postgres’ tools and features will enable you to swiftly deploy, move and manage your database across platforms.

Deploy, move and manage Postgres across cloud platformsAshnikbiz

Running applications in a hybrid setup creates complexities that can increase downtime and maintenance. PostgreSQL runs across virtual, cloud, and container environments; minimizing complexity without sacrificing the performance, so you can take control. Being today’s undisputed leader of relational databases for new and modern applications, Postgres’ tools and features will enable you to swiftly deploy, move and manage your database across platforms. Webinar Covers: Multi-cloud strategy and trends How EDB Postgres can pillar your cloud platform Use cases: Postgres and its tools on-premises and multi-cloud platforms Demo: Using Postgres tools on-premises and for diverse cloud platforms – handling back-up, monitoring, and ensuring Business Continuity Process (BCP)

The Best Approach For Multi-cloud Infrastructure Provisioning-2Ashnikbiz

The webinar covers the best approach for multi-cloud infrastructure provisioning. It discusses the complexities of multi-cloud environments and how Terraform can help with adoption. The webinar features a demo of provisioning cloud infrastructure with Terraform. It also addresses the business drivers for multi-cloud, including improving customer experience, and the challenges of multi-cloud such as the need for multiple skills and complex deployments.

The Best Approach For Multi-cloud Infrastructure ProvisioningAshnikbiz

This document discusses challenges of cloud computing and how HashiCorp's products address them. It introduces Cloud 2.0 as needing a unified control plane across networking, security, operations, and development to manage applications across private and public clouds. HashiCorp's products like Terraform for infrastructure as code, Vault for secrets management, and Consul for service discovery provide a full stack to operate in modern, dynamic cloud environments.

Which PostgreSQL is right for your multi cloud strategy? P2Ashnikbiz

Which PostgreSQL is right for your multi cloud strategy? P1Ashnikbiz

This webinar discusses strategies for using PostgreSQL in a multi-cloud environment. It will cover the different PostgreSQL deployment options for multi-cloud, including PostgreSQL-as-a-service, containerized PostgreSQL, and PostgreSQL on infrastructure-as-a-service. The webinar will also demonstrate how to automate deploying and scaling PostgreSQL. Key considerations for choosing a PostgreSQL option for multi-cloud include manageability, transportability, and automation.

Reduce the complexities of managing Kubernetes clusters anywhere 2Ashnikbiz

Reduce the complexities of managing Kubernetes clusters anywhereAshnikbiz

Enhance your multi-cloud application performance using Redis Enterprise P2Ashnikbiz

This document provides an overview of Redis Enterprise. It discusses how Redis Enterprise is an in-memory multi-model database built on open source Redis that supports high-performance operational, analytics, and hybrid use cases. It offers deployment options including cloud, on-premises, and Kubernetes and supports a wide range of modern use cases including caching, transactions, streaming, messaging, and analytics workloads. Redis Enterprise provides features like high availability, security, and support for Redis modules to extend its capabilities.

Enhance your multi-cloud application performance using Redis Enterprise P1Ashnikbiz

Redis Enterprise can help enhance performance for multi-cloud applications. The webinar covered challenges of multi-cloud environments and how Redis is used, including a demo of setting up Redis across different platforms. It discussed how 72% of customers in Southeast Asia and India are adopting multi-cloud and the business benefits like improved experience, flexibility and reduced time to launch products. Challenges of multi-cloud like complex architecture and application performance were also reviewed.

Gain multi-cloud versatility with software load balancing designed for cloud-...Ashnikbiz

Enterprise-class security with PostgreSQL - 1Ashnikbiz

Enterprise-class security with PostgreSQL - 2Ashnikbiz