You're tasked with backing up network components. How do you decide which ones to prioritize for redundancy?

Firstly we need to evaluate which part of the network we need to achieve redundancy.If we are talking about WAN links that are being delivered by ISPs through managed services , we need to have Active/Active or Active passive links terminated on Edge device which mainly can be L3 devices like routers. Their we need to prioritse the routers to make sure network is deployed in such a way that if one link goes down traffic is automatically shifted to back up link through various redundancy protocols like HSRP/VRRPGLBP etc.

Core devices of organization are critical systems for which regular backups and replication are to be scheduled.Risk Management is also another important factor to be considered while managing them.

The first step in building a resilient infrastructure is to understand what are the business's crown jewels. What asset are critical to the business? What assets are nice to have and which are superfluous? This will allow you to focus your efforts on what delivers the most value to your business.

Consider your pets vs your cattle. Pets need to be backed up and this will always be a priority. Your cattle should be built from automated templates so your strategy should be focussed on the automation that ensures that those devices can be recreated from your automation.

C’est surprenant comment beaucoup de gens négligent le c?té inventaire des actifs et ne se fient qu’à la découverte automatique des actifs par la soi-disant IA des outils en vogue. Ces outils sont un bon point de départ mais il faut y ajouter l’IH (Intelligence Humaine) pour que l’inventaire soit valable

When conducting a risk assessment, it is important to identify and evaluate potential threats to various network components. This involves assessing the likelihood and impact of these threats. This important step helps to identify the network components that need immediate attention for backup solutions. By carefully examining past network performance and failures, one can identify the specific components that are most susceptible to risks. It is crucial to give priority to components that have experienced problems in the past or are essential for security by implementing redundancy. This approach ensures that the network remains stable and resilient.

A la hora de realizar un respaldo debemos saber que estamos guardando y el motivo, por lo cual es importante una buena clasificación de la informacion de los datos para asi mismo darle su criticidad y un buen manejo, so para saber la prioridad de la misma debemos tener claros que servicios o equipos son criticos en nuestra infra estructura.

Prioritizing network components for redundancy involves assessing their criticality to the overall network infrastructure and business operations. Here are the key steps to decide which components to prioritize: 1. Identify Critical Components Core Network Components: Prioritize routers, switches, and firewalls that are essential for network connectivity and security. Servers and Storage: Include critical servers (e.g., database, application, email servers) and storage systems. Network Services: Consider DNS, DHCP, and authentication services.

Buscar sempre postes mais limpos , onde possamos , identificar melhor a rede e também estar com projeto atualizado nas concercionaria de energia ,respeitando o limite de altura que e no máximo 5.20mt a depender do poste .

Le risque n’est pas simplement lié aux composantes réseau, il faut avant tout tenir compte des services supportés par les composantes réseau, leur criticité et leur vulnérabilité. L’inventaire complet des actifs (réseau, serveurs,…) est nécessaire à une bonne évaluation et planification de la résilience ??réseau??

Planning for redundancy involves creating strategies to ensure uninterrupted operation in case of component failure. This process involves choosing suitable methods to ensure redundancy, such as implementing failover systems, redundant hardware, or even geographic redundancy for data centers.?When planning, it's crucial to carefully evaluate different redundancy options to determine the ones that offer the best protection while keeping costs in check. By implementing high-availability pairs for servers or creating multiple network paths, you can effectively eliminate any potential single points of failure in your network. This guarantees that the system stays strong and durable, even in challenging circumstances.

La redundancia es un concepto que nace del dise?o de tu infraestructura y debe contemplar todos los escenarios y localidades. Permitiendo lo que significa alta disponibilidad. A este concepto debe incorporarse la parte electrica, el sistema de climatizacion y los centros de datos.

Sabemos, que para ter um sistema tecnológico funcionando sem nenhum problema , precisamos primeiro ter uma boa estrutura física externa e interna para n?o ter problemas de quedas no circuito.

A solid redundancy strategy should have considerations for * Degree of acceptable loss (can we fly on one wing, do we need 3 tiers of redundancy, can this service be down after hours, etc) and planning accordingly * Prioritization of which devices need to return to stable-state first (should we focus on an access-layer switch before restoring redundancy to the distro layer?) * Mitigation and minimization of impact for a full rebuild (i.e. replacing a switch in a stack is easy, replacing a firewall that corrupted the standby's config before it crashed itself with no backups for the last 6 weeks much less so).

Le design de la redondance doit tenir compte du support éventuel de l’architecture. La redondance doit être clairement documentée, de fa?on compréhensible, incluant les test périodiques qui doivent être faits. Il est très rare que ceux qui en ont fait la conception initiale sont là lors de l’évolution du réseau. Si les personnes chargées de l’évolution du réseau ne comprennent pas bien les mécanismes de résilience intrinsèque du réseau ils la briseront probablement sans même s’en rendre compte. Si la solution de résilience est trop complexe ou mal documentée, la même chose arrivera.

A backup solution is very important on an information system in order to restore the service very quickly in the event of failure. Personally, I find network programming based on programming languages such as python or others to be the best way of automatically backing up configurations on a daily basis.

Sim . Pois temos que ter um sistema muito confiável para poder manter o sistema todo funcionando . Além de um backup bom temos o sistema físico parte externa , como também parte de equipamentos para manter tudo funcionando .

A good network backup solution should have as a barest minimum: 1) triggered backups when a "configuration modified" trap is generated 2) Scheduled daily backups 3) Audit trails for config diff and a log of which user triggered the config changes. 4) Hardware snapshots with each backup (and maybe even triggered by log/SNMP traps as well) to allow for visibility of the hardware state of every managed device. Ideally, restoration of your network infrastructure should be something you can complete on demand and have documented processes and annual drills in the lab to ensure your support staff know how to get your infrastructure back online ASARP.

Les solutions de sauvegarde doivent à la fois comporter des composante ??online?? (pour restaurer rapidement après une panne, ou basculer automatiquement lors d’une panne) et une composante ??offline??, en cas de cyber attaque

I schedule backing up so they're done in the easiest possible order: 1. all devices that have a rear-view camera 2. all devices that have mirrors 3. the rest of the boxes When backing up the rest, it's important to have someone else watch the reverse path to make sure it's clear. Otherwise, you could hit something.

Don’t forget to build config version control into your change process. In addition to giving you point in time backups either side of change operations you can also diff the configs to ensure the change is consistent with what was planned.

El protocolo de mantenimiento es critico, ya que no solo se efectua el mantenimiento en si, sino que permite evaluar el estado de la infaestructura utilizada, realizar pruebas de los procesos de contingencia como respaldos y recuperacion de datos en ambientes controlados.

Critical Systems ,Impact Analysis,Historical Failures Scalability By considering these factors, you can develop a prioritized plan for implementing redundancy across your network infrastructure while optimizing resources effectively.

Le ??protocole de maintenance?? de la résilience c’est les tests réguliers, le basculement vers la solution de résilience. Sans ces tests, il est impossible de savoir ce qui se produira lorsqu’un événement nécessitera l’utilisation de l’architecture résilience, c’est trop souvent lorsqu’on en a besoin qu’on s’aper?oit que notre mécanisme de résilience a perdu une partie de sa fonctionnalité d? à l’évolution des solutions et/ou du réseau

Para estos procesos todo debe estar a la mano, no hay lugar para la improvisación, ya que un proceso de mantenimiento que no termine adecuadamente puede afectar la operacion.

Testing backups of networking devices before scheduling upgrades in a production network is a crucial step to ensure network stability and data integrity. Ensure that the backups are complete and not corrupted. Use checksums or hash values to confirm the integrity of backup files. Create a lab environment that mimics the production network as closely as possible and restore the backups onto the devices in the test environment. Validate that network connectivity between devices is as expected.