uncleflo
Registered since September 28th, 2017
Has a total of 4246 bookmarks.
Showing top Tags within 6 bookmarks
howto information development guide reference administration design website software solution service product online business uk tool company linux code server system application web list video marine create data experience description tutorial explanation technology build blog article learn world project boat download windows security lookup free performance javascript technical control network beautiful support london tools course file research purchase library programming image youtube example php construction html opensource quality install community profile computer feature power browser music platform mobile work user process manage database share hardware professional buy industry internet dance advice installation developer 3d search material camera access customer travel test standard money documentation review css engineering webdesign engine develop device photography digital api speed source program management phone discussion question event client story simple water marketing yacht app content setup package fast idea interface account communication cheap script compare study market easy live google resource operation startup monitor price
Tag selected: failover.
Looking up failover tag. Showing 6 results. Clear
Working with Amazon Aurora Global Database - Amazon Aurora
Saved by uncleflo on June 23rd, 2019.
Following, you can find a description of Amazon Aurora Global Database. Each Aurora global database spans multiple AWS Regions, enabling low latency global reads and disaster recovery from region-wide outages. An Aurora global database consists of one primary AWS Region where your data is mastered, and one read-only, secondary AWS Region. Aurora replicates data to the secondary AWS Region with typical latency of under a second. You issue write operations directly to the primary DB instance in the primary AWS Region. An Aurora global database uses dedicated infrastructure to replicate your data, leaving database resources available entirely to serve application workloads. Applications with a worldwide footprint can use reader instances in the secondary AWS Region for low latency reads. In the unlikely event your database becomes degraded or isolated in an AWS region, you can promote the secondary AWS Region to take full read-write workloads in under a minute.
aurora cluster database endpoint latency snapshot amazon query console replication footprint synchronize bucket secondary instance primary compatibility relational capability website failover mariadb howto isolated resource application workcreate enable browser read parameter outage administration aws documentation
AWS - How to redirect database traffic to a new master on RDS after promoting a read replica? - Server Fault
Saved by uncleflo on June 23rd, 2019.
A lot of RDS's documentation about read replicas contains a magical step along the lines of "direct database traffic to the new master." For instance, their instructions on implementing failure recovery say: This talk about directing traffic glosses over what is actually a complicated step, though. If I were using EC2 instances to host my database, I could give them elastic IPs, use the public DNS address of the instance to address it (which resolves to its private IP from inside AWS), and then instantly swap my entire stack to the read replica by reassigning the elastic IP (and thus simultaneously reassigning the public DNS). I used this method happily back in the days when RDS was considered straightforwardly inferior to rolling your own database instance on EC2 by many DBAs. RDS instances still cannot have elastic IPs, though, so I cannot use this particular trick to magically redirect all my database traffic to a new instance when using RDS.
downtime unscheduled overflow fault deploy database answer server documentation automatic failover address reassign method rds inferior complicated disaster recovery instance host aurora instruction replication switch administration cloud aws howto discussion question
Lab 2 - Build a Failover Solution with Amazon Route 53 and Amazon RDS Read Replication - YouTube
Saved by uncleflo on June 23rd, 2019.
Lab-2: Below is the steps that we had followed to setup Route 53 failover and achive disaster recovery of Application and RDS database. We will examine the Primary Region 1 and what to do, the Secondary Region 2 and the steps there, Failover route 53 from one region to another and set it up, and Test your failover.
test administration failover disaster recover route application rds database region examine follow setup replication solution amazon read video youtube watch howto explanation development
Amazon - High Performance MySQL: Optimization, Backups, and Replication - Third Edition
Saved by uncleflo on June 27th, 2018.
How can you bring out MySQL’s full power? With High Performance MySQL, you’ll learn advanced techniques for everything from designing schemas, indexes, and queries to tuning your MySQL server, operating system, and hardware to their fullest potential. This guide also teaches you safe and practical ways to scale applications through replication, load balancing, high availability, and failover.
amazon mysql power performance technique design index query tune server system hardware potential practical scale application replication balance availability failover infrastructure advanced optimization backup high performance buy product book information developer administration
Painless HA failover with MariaDB
Saved by uncleflo on February 26th, 2018.
At work, we run a simple high-availability (HA) MariaDB setup that consists of an active master that handles all read and write queries from our applications, a passive master that can take over for the active master at any time, and a read-only replication slave (not shown) that we use for backups and analytics. Replication is configured so that the active master follows the passive master, the passive master follows the active master, and the analytics slave follows one of the masters. For the remainders of this post, I will refer to the active master as the master and the passive master as the standby. The benefits of this master-master configuration is that it allows us not only to failover from master to standby if the master becomes unhealthy, but also allows us to perform patching, reboots, lengthy migrations, and other kinds of database maintenance without impacting our users. Well, almost...
high availability mariadb master slave query db dbms backup replication failover painless administration configuration perform patch reboot application remain impact user configure maintain
MariaDB High Availability: Replication Manager
Saved by uncleflo on February 25th, 2018.
This is a follow-up blog post that expands on the subject of highly available cluster, discussed in MariaDB MaxScale High Availability: Active-Standby Cluster. Replication Manager is a tool that manages MariaDB 10 clusters. It supports both interactive and automated failover of the master server. It verifies the integrity of the slave servers before promoting one of them as the replacement master and it also protects the slaves by automatically setting them into read-only mode. You can find more information on the replication-manager from the replication-manager GitHub repository. Using Replication Manager allows us to automate the replication failover. This reduces the amount of manual work required to adapt to changes in the cluster topology and makes for a more highly available database cluster. In this blog post, we'll cover the topic of backend database HA and we’ll use Replication Manager to create a complete HA solution. We build on the setup described in the earlier blog post and integrate Replication Manager into it. We're using Centos 7 as our OS and we'll use the 0.7.0-rc2 version of the replication-manager.
replication cluster high availability manager manage administration topology master slave automatic failover failsafe integration howto article description use software mariasql verify repository expansion readonly server information standby blog post subject discuss backend solution
No further bookmarks found.