Data sets are growing. Requirements for increased Production data availability are expanding in the 24 x 7 world. But amongst all this change – there still remains the critical demand for the DBA to support the agreed Recovery Point Objective (RPO).
I’m always looking for ways to offload the backup workload . During the backup window, server performance degrades. I’ve recently been researching Flash Copy Manager. These are some scenarios \ thoughts \ issues requiring investigation.
When investigating new Backup and Restore products and how they may apply to an environment, simple or obvious questions can sometimes elicit responses revealing gold mine information. I’m never scared to ask the obvious question.
Scenario 1 – Data corruption and FlashCopy Manager
Can we complete a data recovery of an older level of data , for example, due to a logical application error? Would that be at a database level or drive level?
Scenario 2- ETL and FlashCopy Manager
Can Flash Copy of data be restored onto another server, with another server name, security and supporting files, maintaining consistent transactions and be available for read\write?
Is there a documented process for Instant restore of volume process?
Scenario 3 – High Availability and FlashCopy Manager
If the SQL Server is set up in an AlwaysOn configuration i.e high availability databases – do the nodes on TSM need to be set up differently.?
Is the snapshot transaction consistent across all the drives?If data and transaction log files are stored across different drives
If any Production DBAs have Flash Copy Manager experience in a Production Database Server environment, I’d like to hear from you. Your feedback will assist me to assess Flash Copy manager
Network card teaming or NIC teaming are networking terms describing methods of combining multiple parallel network connections . The main purposes are 1) increasing throughput beyond a single connection and 2) redundancy.
The three main teaming configurations
Network Fault Tolerance (NFT)
1) Two – Eight Physical NICS are teamed together into one virtual network adapter.
2) Only one port (Primary) is used for transmit and receive. The remainder adapters are deemed secondary Ports. They are used in the event of a Primary Port failure.
3) Heartbeats can be received and transmitted by all ports
Transmit Load Balancing with Fault Tolerance
1) All NFT features plus Transmit Load Balancing (TLB)
2) Two – Eight Physical NICS are teamed together into one virtual network adapter
3) TLB allows allows load balancing on IP traffic tramsmitted from server
4) Incoming traffic is not load balanced i.e Primary Adapter manages all incoming traffic
Switch Assisted Load Balancing (SLB) with Fault Tolerance
1) All NFT and TLB features plus load balancing incoming traffic
2) Load balancing incoming and transmit traffic
3) SLB load balances all traffic regardless of protocol
There are considerable design considerations for designing redundancy into a SQL Server database system for high availability(HA).
The extent to which redundancy is built into a system will depend on : expertise, cost,resources, service level agreements (SLA)
General areas in considering the HA stack.Consider all these categories - ensuring every element is documented . One of the most resource intensive aspects of maintaining a high availability environment is the managing and monitoring of the system once it's designed and deployed