home.social

#failover — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #failover, aggregated by home.social.

fetched live
  1. [ Blog ] Veeam High Availability Cluster: and automation - pt.2

    Once the Veeam High Availability 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 rviv.ly/7Q8aqV

  2. 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

    valtersit.com/vault/automated-

  3. 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

    valtersit.com/vault/automated-

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

    Once the Veeam High Availability 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 rviv.ly/7Q8aqV

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

    Once the Veeam High Availability 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 rviv.ly/7Q8aqV

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

    Once the Veeam High Availability 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 rviv.ly/7Q8aqV

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

    Once the Veeam High Availability 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 rviv.ly/7Q8aqV

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

    Once the Veeam High Availability 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 rviv.ly/7Q8aqV

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

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

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

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

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

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

    Once the Veeam High Availability 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 rviv.ly/7Q8aqV

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

    Once the Veeam High Availability 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 rviv.ly/7Q8aqV

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

    Once the Veeam High Availability 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 rviv.ly/7Q8aqV

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

    Once the Veeam High Availability 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 rviv.ly/yhouMN

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

    Once the Veeam High Availability 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 rviv.ly/yhouMN

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

  20. 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

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

    Once the Veeam High Availability 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 rviv.ly/yhouMN

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

    Once the Veeam High Availability 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 rviv.ly/yhouMN

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

    Once the Veeam High Availability 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 rviv.ly/yhouMN

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

    Once the Veeam High Availability 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 rviv.ly/yhouMN

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

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

    habr.com/ru/companies/hstx/art

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

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

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

    habr.com/ru/companies/hstx/art

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

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

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

    habr.com/ru/companies/hstx/art

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

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

    Once the Veeam High Availability 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 rviv.ly/yhouMN

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

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

    habr.com/ru/articles/1047374/

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

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

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

    habr.com/ru/articles/1047374/

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

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

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

    habr.com/ru/articles/1047374/

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

  32. @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

  33. @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

  34. @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

  35. @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

  36. @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

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

    Once the Veeam High Availability 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 rviv.ly/yhouMN

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

    Once the Veeam High Availability 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 rviv.ly/yhouMN

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

    Once the Veeam High Availability 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 rviv.ly/yhouMN

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

    Once the Veeam High Availability 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 rviv.ly/yhouMN

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

    Once the Veeam High Availability 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 rviv.ly/yhouMN

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

    Once the Veeam High Availability 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 rviv.ly/yhouMN

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

    Once the Veeam High Availability 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 rviv.ly/xvsjaB

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

    Once the Veeam High Availability 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 rviv.ly/yhouMN

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

    Once the Veeam High Availability 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 rviv.ly/yhouMN

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

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

    habr.com/ru/articles/1030020/

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

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

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

    habr.com/ru/articles/1030020/

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

  48. 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

    youtube.com/shorts/L3s3K2E4-1I

    Listen here : ithorrorstories.eu/#ep12

    All other things : links.ithorrorstories.eu/

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

  49. 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

    youtube.com/shorts/L3s3K2E4-1I

    Listen here : ithorrorstories.eu/#ep12

    All other things : links.ithorrorstories.eu/

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

  50. 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

    youtube.com/shorts/L3s3K2E4-1I

    Listen here : ithorrorstories.eu/#ep12

    All other things : links.ithorrorstories.eu/

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

  51. 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

    youtube.com/shorts/L3s3K2E4-1I

    Listen here : ithorrorstories.eu/#ep12

    All other things : links.ithorrorstories.eu/

  52. 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.

    youtube.com/shorts/k_SyFbQ71TU

    #podcast #technology #failover #failure #techlife