Datastore Utilization Alarm Trigger Test
I had an opportunity to conduct datastore utilization alarm test at 95 % utilization. The datastore criticl alarm was set to 95% and the free space was set to 10% before the customer implemented VMware snapshot based backups. The goal of the test was to identify the response times of respective teams starting from the time the datastore reached 95% and the actual time it takes the alarm trigger to reach the monitoring team and then the time it gets notified to VMware platform team to perform vMotion to overcome datastore out of space condition. Below are the steps performed and corresponding actual results. Test Steps and Expectations: 1. Datastore 95% alert alarms – Monitoring Team should receive the alarm 2. Ticket should be is escalated/raised with the Platform Team – performed by Monitoring Team 3. Platform Team should acknowledges the ticket – performed by VMware Platform Team Record Test Results: Capture how much time elapses for ticket to be raised with platform team Document the time each step is performed Identify any other groups that should be notified as a result of netbackup filling up the datastore full Actual Test Results: Total time elapsed from step 1 to 3 was 1 hr. This does not include the vMotion time to overcome the datastore out of space or full condition. It was noticed that clearly the 95% threshold and 10% free space was too narrow compared to the response times of respective teams. Thus it was concluded the free space should be at least 20 % and the alarm threshould should be set down to 85 % to avoid potential outage.We are looking for Oracle Application Developers
Symantec is developing a new exciting self-service product which will allow you to get access to the data you need faster. We are looking for Oracle Application Developers to participate in online meetings, phone interviews, and in person collaborations.
Opciones y desafíos de migración de Windows Server 2003, parte 1
El 14 de julio de 2015, Microsoft finalizará el soporte para todas las versiones de Windows Server 2003. Esto significa que Microsoft ya no proporcionará soporte, parches de seguridad ni actualizaciones de software para este producto. ¿Cuáles son los riesgos de seguir ejecutando Windows Server 2003 cuando deje de tener soporte?Desafios e opções da migração do Windows Server 2003 - Parte 1
No dia 14 de julho de 2015, a Microsoft encerrará o suporte para todas as versões do Windows Server 2003. Isso significa que, a partir dessa data, a Microsoft não fornecerá mais suporte, patches de segurança ou atualizações de software para esse produto. Quais são os riscos de continuar a executar o Windows Server 2003 após o encerramento do suporte?
Snapshot (156) Errors when no snapshots are being taken
I have been working with NetBackup since 6.5 as a consultant and from time to time I have seen flat file windows backups fail with 156 errors, which is a snapshot failure. A snapshot is not typically used when doing these types of backups. To avoid these failures do the following;
