#failover — Public Fediverse posts

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/7Q8aqV #veeamone

Redis Sentinel: `sentinel monitor <name> <host> <port> <quorum>` with quorum=2 ensures 2 Sentinels agree before promoting a replica. Config on Redis 5.0+/Ubuntu 20.04. Automatic failover without manual intervention. #sentinel #high-availability #failover #ValtersIT

https://www.valtersit.com/vault/automated-failover-with-sentinel-and-sentinel-monitor-quorum-c212c0/

Redis Sentinel: `sentinel monitor <name> <host> <port> <quorum>` with quorum=2 ensures 2 Sentinels agree before promoting a replica. Config on Redis 5.0+/Ubuntu 20.04. Automatic failover without manual intervention. #sentinel #high-availability #failover #ValtersIT

https://www.valtersit.com/vault/automated-failover-with-sentinel-and-sentinel-monitor-quorum-c212c0/

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/7Q8aqV #veeamone

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/7Q8aqV #veeamone

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/7Q8aqV #veeamone

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/7Q8aqV #veeamone

@ikkeT @Doveux I use #openwrt only and it works well & secure with #banip & #adguardhome & #wireguard & #failover & #loadbalancing ....

@ikkeT @Doveux I use #openwrt only and it works well & secure with #banip & #adguardhome & #wireguard & #failover & #loadbalancing ....

@ikkeT @Doveux I use #openwrt only and it works well & secure with #banip & #adguardhome & #wireguard & #failover & #loadbalancing ....

@ikkeT @Doveux I use #openwrt only and it works well & secure with #banip & #adguardhome & #wireguard & #failover & #loadbalancing ....

@ikkeT @Doveux I use #openwrt only and it works well & secure with #banip & #adguardhome & #wireguard & #failover & #loadbalancing ....

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/7Q8aqV #veeamone

This happens. The money I've spent to allow this to happen? Worth every penny. #resilient #failover

This happens. The money I've spent to allow this to happen? Worth every penny. #resilient #failover

This happens. The money I've spent to allow this to happen? Worth every penny. #resilient #failover

This happens. The money I've spent to allow this to happen? Worth every penny. #resilient #failover

This happens. The money I've spent to allow this to happen? Worth every penny. #resilient #failover

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/7Q8aqV #veeamone

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/7Q8aqV #veeamone

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/7Q8aqV #veeamone

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/yhouMN #veeamone

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/yhouMN #veeamone

Das Einzige, was ich noch nicht rausbekommen habe: Wie erhalte ich bei #Failover auf 5G eine Nachricht (per Push oder als SMS)?

Die Situation mit separatem 4G-#Failover vor meinem #Router war mir schon lange ein Dorn im Auge - und funktionierte auch nicht zuverlässig. Also habe ich erst versucht, mein #Netgear Orbi RBK752/LM1200-Kombi durch einen Netgear NBK752 zu ersetzen … nur, um nach Lieferung festzustellen, dass das Gerät komplett veraltet (und daher so preiswert zu haben) ist.

⬇️

#SmartHome #WLAN

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/yhouMN #veeamone

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/yhouMN #veeamone

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/yhouMN #veeamone

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/yhouMN #veeamone

Почему ваш DR-план не сработает при реальной аварии (и что с этим делать)

Недавно на вебинаре Хайстекс разбирались реальные сценарии DR на практике. В чате трансляции зрители задали ряд технических вопросов, наиболее интересные из них легли в основу этого разбора.

https://habr.com/ru/companies/hstx/articles/1048140/

#аварийное_восстановление #disaster_recovery #RTO #RPO #репликация #failover #failback #резервное_копирование #виртуализация #хайстекс_акура

Почему ваш DR-план не сработает при реальной аварии (и что с этим делать)

Недавно на вебинаре Хайстекс разбирались реальные сценарии DR на практике. В чате трансляции зрители задали ряд технических вопросов, наиболее интересные из них легли в основу этого разбора.

https://habr.com/ru/companies/hstx/articles/1048140/

#аварийное_восстановление #disaster_recovery #RTO #RPO #репликация #failover #failback #резервное_копирование #виртуализация #хайстекс_акура

Почему ваш DR-план не сработает при реальной аварии (и что с этим делать)

Недавно на вебинаре Хайстекс разбирались реальные сценарии DR на практике. В чате трансляции зрители задали ряд технических вопросов, наиболее интересные из них легли в основу этого разбора.

https://habr.com/ru/companies/hstx/articles/1048140/

#аварийное_восстановление #disaster_recovery #RTO #RPO #репликация #failover #failback #резервное_копирование #виртуализация #хайстекс_акура

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/yhouMN #veeamone

Три задачи discovery при работе с PostgreSQL master/replica — и как их решить

Когда у приложения появляется несколько хостов PostgreSQL, начинается головная боль: нужно динамически находить мастера после failover, выбирать реплику с нужным отставанием и гарантировать что пользователь не увидит устаревшие данные после своей же записи. DNS кешируется минутами, libpq не знает про lag, HAProxy не слышал про LSN. Разбираем как устроены существующие решения и как закрыть все три задачи через лёгкий HTTP сервис — pg-status .

https://habr.com/ru/articles/1047374/

#postgresql #репликация #failover #replication #python #sql #discovery #high_availability

Три задачи discovery при работе с PostgreSQL master/replica — и как их решить

Когда у приложения появляется несколько хостов PostgreSQL, начинается головная боль: нужно динамически находить мастера после failover, выбирать реплику с нужным отставанием и гарантировать что пользователь не увидит устаревшие данные после своей же записи. DNS кешируется минутами, libpq не знает про lag, HAProxy не слышал про LSN. Разбираем как устроены существующие решения и как закрыть все три задачи через лёгкий HTTP сервис — pg-status .

https://habr.com/ru/articles/1047374/

#postgresql #репликация #failover #replication #python #sql #discovery #high_availability

Три задачи discovery при работе с PostgreSQL master/replica — и как их решить

Когда у приложения появляется несколько хостов PostgreSQL, начинается головная боль: нужно динамически находить мастера после failover, выбирать реплику с нужным отставанием и гарантировать что пользователь не увидит устаревшие данные после своей же записи. DNS кешируется минутами, libpq не знает про lag, HAProxy не слышал про LSN. Разбираем как устроены существующие решения и как закрыть все три задачи через лёгкий HTTP сервис — pg-status .

https://habr.com/ru/articles/1047374/

#postgresql #репликация #failover #replication #python #sql #discovery #high_availability

@PC_Fluesterer Auf jeden Fall unprofessionell, schlecht designed, schlecht gemacht und sowas von nicht zeitgemäß. Dabei weiß man doch schon lange, wie man hohe Verfügbarkeit, Redundanz und Ausfallsicherheit in der IT architekturell erlangt und, daß diese Komponenten nicht optional sind.

#itsec #performance #ausfallsicherheit #redundanz #failover #fallback #verfügbarkeit #devops #itarchitektur #togaf #rechenzentrum #spof #singlepointoffailure #bottleneck

@PC_Fluesterer Auf jeden Fall unprofessionell, schlecht designed, schlecht gemacht und sowas von nicht zeitgemäß. Dabei weiß man doch schon lange, wie man hohe Verfügbarkeit, Redundanz und Ausfallsicherheit in der IT architekturell erlangt und, daß diese Komponenten nicht optional sind.

#itsec #performance #ausfallsicherheit #redundanz #failover #fallback #verfügbarkeit #devops #itarchitektur #togaf #rechenzentrum #spof #singlepointoffailure #bottleneck

@PC_Fluesterer Auf jeden Fall unprofessionell, schlecht designed, schlecht gemacht und sowas von nicht zeitgemäß. Dabei weiß man doch schon lange, wie man hohe Verfügbarkeit, Redundanz und Ausfallsicherheit in der IT architekturell erlangt und, daß diese Komponenten nicht optional sind.

#itsec #performance #ausfallsicherheit #redundanz #failover #fallback #verfügbarkeit #devops #itarchitektur #togaf #rechenzentrum #spof #singlepointoffailure #bottleneck

@PC_Fluesterer Auf jeden Fall unprofessionell, schlecht designed, schlecht gemacht und sowas von nicht zeitgemäß. Dabei weiß man doch schon lange, wie man hohe Verfügbarkeit, Redundanz und Ausfallsicherheit in der IT architekturell erlangt und, daß diese Komponenten nicht optional sind.

#itsec #performance #ausfallsicherheit #redundanz #failover #fallback #verfügbarkeit #devops #itarchitektur #togaf #rechenzentrum #spof #singlepointoffailure #bottleneck

@PC_Fluesterer Auf jeden Fall unprofessionell, schlecht designed, schlecht gemacht und sowas von nicht zeitgemäß. Dabei weiß man doch schon lange, wie man hohe Verfügbarkeit, Redundanz und Ausfallsicherheit in der IT architekturell erlangt und, daß diese Komponenten nicht optional sind.

#itsec #performance #ausfallsicherheit #redundanz #failover #fallback #verfügbarkeit #devops #itarchitektur #togaf #rechenzentrum #spof #singlepointoffailure #bottleneck

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/yhouMN #veeamone

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/yhouMN #veeamone

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/yhouMN #veeamone

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/yhouMN #veeamone

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/yhouMN #veeamone

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/yhouMN #veeamone

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/xvsjaB #veeamone

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/yhouMN #veeamone

[ Blog ] Veeam High Availability Cluster: #failover and automation - pt.2

Once the Veeam High Availability #Cluster has been created, there are two ways to perform the failover: manual and automated through Veeam ONE.

Manual failover does not require additional components to be installed, whereas automatic failover requires Veeam ONE to be installed and configured within your http://rviv.ly/yhouMN #veeamone

Blog alert!

This time on checking your options when a cloud service goes down. Are you aware of what happens in your cloud?

#Redundancy
#BusinessContinuity
#FailOver
#HADR

http://sqlreitse.com/2026/05/12/remember-your-redundancy/

Blog alert!

This time on checking your options when a cloud service goes down. Are you aware of what happens in your cloud?

#Redundancy
#BusinessContinuity
#FailOver
#HADR

http://sqlreitse.com/2026/05/12/remember-your-redundancy/

Blog alert!

This time on checking your options when a cloud service goes down. Are you aware of what happens in your cloud?

#Redundancy
#BusinessContinuity
#FailOver
#HADR

http://sqlreitse.com/2026/05/12/remember-your-redundancy/

Строим шину данных для микросервисов на ZeroMQ: failover, гарантии доставки и E2E-шифрование

Асинхронная клиент-серверная библиотека для обмена сообщениями между микросервисами на базе ZeroMQ. Реализует гарантированную доставку сообщений (At-Least-Once) с персистентной файловой очередью при обрывах связи, автоматический failover сервера переадресации (клиенты могут подхватывать роль сервера на лету) и два уровня защиты: шифрование канала (CurveZMQ) и сквозное шифрование сообщений (HMAC). Лёгкая альтернатива брокерам вроде RabbitMQ, не требующая отдельного сервера.

https://habr.com/ru/articles/1030020/

#python #zeromq #zmq #failover #atleastonce #endtoend_шифрование #микросервисы #распределенные_системы #hmac #криптография

Строим шину данных для микросервисов на ZeroMQ: failover, гарантии доставки и E2E-шифрование

Асинхронная клиент-серверная библиотека для обмена сообщениями между микросервисами на базе ZeroMQ. Реализует гарантированную доставку сообщений (At-Least-Once) с персистентной файловой очередью при обрывах связи, автоматический failover сервера переадресации (клиенты могут подхватывать роль сервера на лету) и два уровня защиты: шифрование канала (CurveZMQ) и сквозное шифрование сообщений (HMAC). Лёгкая альтернатива брокерам вроде RabbitMQ, не требующая отдельного сервера.

https://habr.com/ru/articles/1030020/

#python #zeromq #zmq #failover #atleastonce #endtoend_шифрование #микросервисы #распределенные_системы #hmac #криптография

Turns out, failover success is subjective. Apparently, being ‘active’ just means you get tested harder. Ever wondered how ‘best intentions’ can invent new incidents? Let’s talk IT wisdom in the replies.

Find out more in Episode 12 : The Failover That Failed Successfully

https://youtube.com/shorts/L3s3K2E4-1I

Listen here : https://ithorrorstories.eu/#ep12

All other things : https://links.ithorrorstories.eu/

#podcasts #failover #drtest #disaster #technology #operationalreadyness #tech

Turns out, failover success is subjective. Apparently, being ‘active’ just means you get tested harder. Ever wondered how ‘best intentions’ can invent new incidents? Let’s talk IT wisdom in the replies.

Find out more in Episode 12 : The Failover That Failed Successfully

https://youtube.com/shorts/L3s3K2E4-1I

Listen here : https://ithorrorstories.eu/#ep12

All other things : https://links.ithorrorstories.eu/

#podcasts #failover #drtest #disaster #technology #operationalreadyness #tech

Turns out, failover success is subjective. Apparently, being ‘active’ just means you get tested harder. Ever wondered how ‘best intentions’ can invent new incidents? Let’s talk IT wisdom in the replies.

Find out more in Episode 12 : The Failover That Failed Successfully

https://youtube.com/shorts/L3s3K2E4-1I

Listen here : https://ithorrorstories.eu/#ep12

All other things : https://links.ithorrorstories.eu/

#podcasts #failover #drtest #disaster #technology #operationalreadyness #tech

Turns out, failover success is subjective. Apparently, being ‘active’ just means you get tested harder. Ever wondered how ‘best intentions’ can invent new incidents? Let’s talk IT wisdom in the replies.

Find out more in Episode 12 : The Failover That Failed Successfully

https://youtube.com/shorts/L3s3K2E4-1I

Listen here : https://ithorrorstories.eu/#ep12

All other things : https://links.ithorrorstories.eu/

#podcasts #failover #drtest #disaster #technology #operationalreadyness #tech

Ever run a failover test that worked perfectly… and still felt like everything was falling apart?

In Episode 12, we take you into a disaster recovery test during a busy release weekend — where the tech held up, but communication didn’t.

Subcontractors weren’t aligned, assumptions didn’t match reality, and suddenly a ‘simple test’ turned into a full coordination puzzle.

No production impact — but plenty of lessons.

Because resilience isn’t just about systems… it’s about people, timing, and actually talking to each other.

Listen now to IT Horror Stories with Jack Smith
You can find us on Spotify, Apple Music, Youtube, Deezer and of course at ITHorrorStories.eu

You are one of us.

https://youtube.com/shorts/k_SyFbQ71TU

#podcast #technology #failover #failure #techlife