Your system crashes during peak work hours. How do you keep productivity from grinding to a halt?

1. Alert stakeholders of the system downtime . This will help in managing expectations. 2. Activate the incident response plan as per SLA :Assess situation and, if cannot resolved as per the SLA, fallback to secondary backup . 3. Keep the team updated on ETA and the fallback plan. 4. Test and check secondary backup is Ok, activate. 5. Resolve the crash and analyse the root cause and remediation activities (must document). 6. Issue resolved, fallback to primary. 7.Test and deploy primary, if OK 8. Communicate uptime.

In the first place such issue with the proper design and high availability shouldn’t happen in production environment In case it happened if recovery time for the service will take longtime immediate failover to discover recovery site is a must

1.implement redundancy and failover 2.load balancing 3.regular maintenance and update 4.monitoring and alerts 5.data backup and recovery plans 6.employee training

Rule 1. A system will crash. Depending on that systems impact to productivity the plan may vary. If the Payroll system crashes close to payday deadlines your time to troubleshoot and repair is different than the hour after payroll posts when time is less of an impact. Work with stakeholders to develop effective expectations around timelines. Don’t discount the value of warranties and urgent SLA agreements on certain platforms. Loss of productivity can add up quickly making these up costs cheap insurance. If it’s your personal system that crashes… well you’re an IT professional it shouldn’t take you long to return to normal regardless of the failure.

Fazer backup regularmente dos seus dados é crucial, mas se uma falha o pegar desprevenido, tente salvar o que puder. Se o sistema for reinicializado, salve imediatamente todos os documentos abertos em um disco rígido externo ou armazenamento em nuvem. Se sua máquina n?o reiniciar, remova o disco rígido e conecte-o a outro computador para extrair arquivos importantes. Isso pode evitar uma perda significativa de dados e permitir que você continue trabalhando em um dispositivo diferente, se necessário.

We worked with users who are using cloud storage and have set policies that any documents are saved to servers or the cloud. There are various different solutions for backup with its advantages and drawbacks. Make sure that the client is aware of the features before implementing a system as money usually dictates the solution that is implemented.

Aparte de tener una copia de seguridad es necesario que nuestros sistemas críticos funcionen en servidores que funcionen como clúster o tener máquinas virtuales secundarias para brindar un servicio, aún si fuera de manera temporal, mientras se soluciona una falla.

It is better to store your data to the external hard drive or online storages so you cannot lose them when your computer crashes.

1St User Data Backup Because Data is very Very important and then System check and then OS Problem and Many Problem Ram zand other.

When I ran a computer business, I would ask managers: how long would it take if all your computers stopped working now, to get back to where you are right now? Regardless of the response, I would ask another worker to open their local documents. I would then ask if any files were backed up. The answer was usually no. This would always prove my point: computers and digital devices are expendable, the data on them is priceless. Your system is only as good as the last valid backup that it made. If it's a server, then it needs a proper redundancy plan. Look at the device you're using now. Ask yourself how long would it take to replace it - to the point where it is a 1:1 version of what you have now? Now extend that mindset to an entire network.

Quando seu sistema principal falha, ter ferramentas alternativas prontas pode salvar o dia. Use um laptop, tablet ou até mesmo seu smartphone sobressalente para manter as fun??es básicas de trabalho. Familiarize-se com aplicativos baseados em nuvem que podem ser acessados de qualquer dispositivo, garantindo que você possa recuperar e trabalhar em seus documentos de qualquer lugar. Essa flexibilidade pode mantê-lo produtivo até que seu sistema principal esteja online novamente.

Por lo visto esta súper mal formulada la naturaleza del problema. Hablan de un sistema bloqueado y proponen revisar ruidos y la red.. Esto lo hizo un bot o que? Hagan una encuesta basada en problemáticas reales por favor, no nos hagan perder tiempo. Gracias,

Yeah , usually a spare laptop for backup backup , and if possible a port on the switch or server , only accessible by me , and if in a domain controlled environment with policy to let me login and have network access through other systems i will use empty systems to resolve the force issue

Always is great have paper and pencil to can register everything there and when System is back you can upload all, or you can use offline tools

A comunica??o é fundamental durante uma falha do sistema. Informe sua equipe e supervisores sobre o problema e forne?a um tempo estimado para resolu??o, se possível. Essa transparência ajuda a gerenciar as expectativas e permite ajustes nos prazos ou fluxos de trabalho. Se você estiver em uma fun??o voltada para o cliente, informe seus clientes de que pode haver atrasos. A comunica??o clara pode mitigar a frustra??o e manter a confian?a.

Yeah and also not stressing anyone in communications so we can solve the issue with a clear mind , a clear mind helps everyone to have good performance

Communication is the key for everything since a system crash to the new personal on the company because that way you can have support from everyone and you can support all your partners

I totally agree with this, keeping all the stakeholders informed and being honest about it is paramount. This allows you to manage their expectations and in turn reduces anxiety whilst troubleshooting.

A comunica??o é fundamental para qualquer organiza??o seja ela pequena, média ou grande , precisamos passar informa??es a todos de como está o processo se inicou ou finalizou, para que quem esteja dependendo da sua informa??o fique ciente e n?o passe informa??o errada sem saber até mesmo para ter um melhor controle dentro da empresa.Imagina você come?ou a trabalhar em uma empresa e ninguém te comunica o que você vai fazer ? Comunica??o é tudo.Caso um sistema pare de funcionar você precisa informar na mesma hora e n?o deixar passar, só assim você conseguirá resolver.

Comece a solu??o de problemas identificando quaisquer altera??es recentes em seu sistema que possam ter causado a falha. Desinstale instala??es recentes de software ou reverta quaisquer ajustes de configura??es. Se você se sentir confortável com isso, acesse o BIOS (Sistema básico de entrada/saída) ou use uma unidade USB inicializável com ferramentas de diagnóstico para verificar se há erros de disco ou componentes de hardware com falha. A solu??o de problemas inteligente geralmente pode levar a uma resolu??o rápida.

I am comfortable with them, running all kinds of tests software , hardware Doing some driver updates , look if an update failed Conflicting services and ... Solve the issue and make sure it never returns

Well whatever may have crashed in the peak hour, at first I wouldn't lose myself in like " OH MY GOD!! " Instead I'll just calmly look for the problem then figure out what to do rather than using my 100% from the start, of course I'll have every means of backup for such. It totally depends upon the problem. Not to lose your demeanour and accessing the situation calmly is the main thing.

Check all available logs and try to isolate the issue. If it's a hardware fault, replace the hardware and run system tests (all indicators should be green, and there should be no errors in the logs). If everything is okay, recover your OS, databases, and applications. Consider using infrastructure monitoring tools.

Firstly try to identify the problem. Then try doing the things in reverse order (undoing the recent changes) disconnecting the recently added peripherals. Checking for the solutions online on google & youtube. Communicating with colleagues and fellow learners. Never hesitate to ask for help from your seniors/ juniors, co- workers, fellow learners, and teachers.

Use essa experiência como uma oportunidade de aprendizado para planejar futuras falhas. Invista em um sistema de backup robusto e crie um plano de recupera??o de desastres que inclua backups regulares de dados, informa??es de contato de emergência para suporte de TI e uma lista de tarefas críticas que podem ser executadas em dispositivos alternativos. O planejamento proativo ajudará a garantir que, na próxima vez que seu sistema falhar, você esteja pronto para lidar com isso com o mínimo de interrup??o.

Ensure redundancy after disaster. If you had no budget all the sudden you will since management will see the productivity loss is way more than if proper IT budget was allocated!

To alleviate any downtime, you have to plan for the worst. Having back ups and disaster recovery for your enterprise applications is a must. These plans need to be well thought out and you have to practice the recovery process just so you don’t run into any unknowns. I sleep way better knowing that I have these plans in place and have practiced the recovery processes, so we can have the applications back up in hours and not days, weeks or months.

I love can have plan b for the plan b like batman, for example i prefer have minimum 2 pieces of everything like hard disk, computer, monitors, usb, everything with the same information and the same model of product with this you can just replace quickly your tools

Properly vetted Standard Operating Procedures along with restore points and backups. Having multiple backup media and multiple backup locations.