From Reactive to Ready: Why Resilience is more than Backup
Everyone knows you need to protect your data. It’s become a truism of our times. But, the thing is, there’s no intrinsic value in data alone. Unless you can index, search, or analyze it, it’s just passive information. This is why the apps, services, and other components you use to interrogate and act on your data are so important.
EP30: Top Reasons NetBackup Appliances Beats Data Domain
At the end of the day, Veritas is a hardware agnostic, software-defined solution approach to solving customers’ problems. Tune in as they dive in and uncover the key differentiators of NetBackup Appliances and how it out preforms its competitors.EP22: Active-Active High Availability with the NetBackup 5340 and 5330 Appliances
The high availability configuration of the 5300 family of NetBackup appliances reduces downtime to almost zero and brings a big increase in performance. If you’re looking for an HA configuration, tune into this podcast!
MSMQ Outgoing Queues referencing failed EV server - using Building Blocks for High Availability
Hi Everyone We make use of Building Blocks to build High Availability in our EV environment. We have come across a peculiar problem and wanted to know if anyone here has noted a similar issue. Scenario: We are in the archiving schedule and there are (say) 5 EV Mailbox Archiving Servers archiving 5 Exchange Servers. There are cross-references across EV and Exchange Servers i.e. the Storage Service for an archive is on an EV server other than the one which is running the Archival Task. Problem: If an EV Mailbox Archiving Servers fails, we use Building Blocks to quickly bring up services on a standby server by running Update Service Locations. However, we notice that items are still in archive pending state in user mailboxes being archived by other EV Servers. New items are also going into archive pending state across all user mailboxes. Analysis: We have already run a flushdns (or Clear-DNSClientCache in Powershell) across all EV servers. In the MSMQ Outgoing Queues, we noticed that there are queues which still resolve to the old failed servers and are in Failed to Connect or Waiting to Connect state, since MSMQ does not resolve to the EV aliases but the EV server hostnames. Solution: To resolve the issue, we need to add a host file entry resolving the hostname of the failed server to the IP address of the now active server and restart the storage/taskcontroller service. Has anyone of you come across a similar situation? We wish to avoid making host file entries and make the failover process seamless.
I want to switch the application to minos2，but I cannot select the system
I want to switch the application to minos2，but I cannot select the system No system，why？ root@minos1(/)# hastatus -sum -- SYSTEM STATE -- System State Frozen A minos1 RUNNING 0 -- GROUP STATE -- Group System Probed AutoDisabled State B ClusterService minos1 Y N ONLINE B EMS minos1 Y N ONLINE B replication minos1 Y N ONLINE -- REMOTE CLUSTER STATE -- Cluster State N minos2 RUNNING -- REMOTE SYSTEM STATE -- cluster:system State Frozen O minos2:minos2 RUNNING 0
