ACE Backup-server failover

I'm having trouble with the functionality of backup servers in a serverfarm.
Lets say I have three rservers in a serverfarm. Each rserver has a backup-server assigned to it. When a probe detects that one of the three nodes failed, the ACE puts the backupserver in rotation for the whole serverfarm. This causes one out of three connections to show a "under construction" page. However two of the three nodes are still functioning, but users randomly see a construction page, which confuses them.
Is there a way to configure the ACE to follow this procedure?
One server fails a probe, take server out of rotation
Second server fails a probe, take server out of rotation
Third server fails a probe, take server out of rotation
Place backupserver in rotation for the whole farm
When one server comes back online, put it inservice and take backupserver out of rotation.
The intent is for the rservers to be self-sufficient making server administrators not have to have any knowledge of ACE and need to login and manually place a serever out of service. I want a probe to detect IIS failing and allow server administrators to work on one node at a time without an outage, and still retain a construction page if all nodes fail.

Hi,
Probably, you may need a "sorry server" configuration but also there´s another way which you may take into account which backup serverfarm, please take a look:
http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/vA5_1_0/configuration/slb/guide/classlb.html
backup
name2
—(Optional) Designates an existing host (with valid content) or a redirect (sorry) server farm as a backup server farm in case all the real servers in the primary server farm become unavailable. You can configure one backup server farm for each existing primary server farm. When at least one server in the primary server farm becomes available again, the ACE sends all new connections back to the primary server farm. The ACE allows existing connections to the backup server farm to complete."
Regards,
Jorge

Similar Messages

ACE backup-server and sticky

Hi all,
a question:
     if a configure a serverfarm with backup-server
serverfarm host S_Das
rserver DAS1
    backup-rserver DAS1_1
    inservice
rserver DAS_1
    inservice standby
rserver DAS2
    backup-rserver DAS2_1
    inservice
rserver DAS_1
    inservice standby
sticky ip-netmask 255.255.255.255 address both SF_DAS
timeout 10
replicate sticky
serverfarm S_Das
and rserver DAS1 goes down what will be behaviour of sticky and balancing?
New connection wel'll go towards DAS2 or a tricky and clever sticky take precedence? (i mean persistence on DAS1_1 that is my backup server..)
tnx
Das

Hi Danilo,
If your primary rserver goes down the sticky entries associated with that server will be automatically flushed from the sticky table so that
all new incoming connections will be diverted to your backup rserver.
In case that primary rserver comes back then:
- Existing connections on backup keep accessing backup.
- For new connection requests ACE looks up sticky entries, if there's already an entry for backup server the connections is sent to the standby rserver.
- If a new client request (connection) doesn't match any sticky entry for backup rserver ACE forwards this request to primary.
In case that you want to use the primary rserver for all the connections after coming back to operational state then the backup option would be configured like this:
rserver Primary
ip address 10.10.10.2
inservice
rserver Standby
ip address 10.10.10.3
inservice
serverfarm host Primary
rserver Primary
    inservice
serverfarm host Standby
rserver Standby
    inservice
policy-map type loadbalance http first-match slb
class class-default
serverfarm Primary backup Standby
HTH

ACE: Server- /backup-server connection failover

Hi, I have a question regarding server-failover when using rserver+backup-rserver or serverfarm+backup-serverfarm (via sticky).
My understanding is, that in case a server fails, the existing connections will not fail over to a backup-server.
We are looking for a way to change that (default) behaviour - We've already searched the documentation etc. and found the "failaction reassign/purge". But when my colleague tried to have this confirmed via TAC, it got pretty confusing and we were told, there's no way to do/solve this..
So in a second attempt, does anyone have experience with this - maybe can confirm or give another solution?
Thanks & Regards,
Max

This was answered sometime back in few discussion:
first, not all servers accept TCP connection to be reassigned to them.
This is because tcp requires 3-way handshake and keeps track of sequence/ack numbers.Therefore, the servers need some way to exchange this information or to start in the middle.
On ace, we have 2 commands "failaction reassign" or "failaction purge".
The reassign is to simply move the connection to a backup server.
The purge is to kill the connection forcing the client to reopen a new one - this new connection will then be loadbalance to an active server.

Backup server on an ACE

When creating a backup server on an ACE running A5(2.1), we're using the probe as the trigger. Once the primary real server has failed to the backup, will it fail back to the primary server when the probe deems the primary server available?
It's just as well as the ACE manual documents the backup serverfarm, there's dearth of info on the backup server.
Thanks.
_ Greg

Hi Greg,
Backup rserver as you know would be configured with standby keyword. When primary server will be Operational (probe passed)
- Existing connections on backup keep accessing backup.
- For new connection requests ACE looks up sticky entries, if there's already an entry for backup server, the connection is sent to the standby rserver.
- If a new client request (connection) doesn't match any sticky entry for backup rserver ACE forwards this request to primary.
Let me know if you have any questions.
Regards,
Kanwal
Note: Please mark answers if they are helpful.

AnyConnect Client Profile Backup Server Configuration

I'm trying to understand the use of Backup Server option in AnyConnect Client Profile
Configuration > Remote Access VPN > Network (Client) Access > AnyConnect Client Profile > Edit > Backup Server
(Screenshot attached)
My questions:
1. In what all scenarios do we add servers (ASA devices) in this tab
2. If I have same information in two different locations (Site A and Site B) for AnyConnect user, can I add Site A-ASA and Site B-ASA into Backup Server tab as a failover mechanism for end user.
3. Or is it only used to mention ASA devices configured in failover unit
4. In case of failover unit, does it support stateful failover
I could not find answers to above questions from Google search. So, asking here

I think we need to be careful when we talk about failover. The original post was clearly asking about two different scenarios
1) ASAs at two different sites
2) ASAs configured as a High Availability failover pair (Active/Standby).
The profile does work to provide failover in 1) but does not work to provide failover in 2).
I do not know the authoritative answer to the question about IP phones use of the profile. I believe that the answer ought to be that yes the phone would receive the profile after its first connection and would use the backup server identified in the profile is the primary server was not available. That is a basic functionality of the AnyConnect client and if the phone is using the AnyConnect client then it ought to support that failover.
If someone does have an authoritative answer then please speak up. Several of us would like to know the right answer here.
HTH
Rick

Backup server recomendations

We currently backup our 4 V880 servers using a 420R as backup server and an L25 tape jukebox on a dedicated gigabit ethernet.
The L25 is in need of replacement and I thought an SL24 would be ideal but wondered what people might recommend as a backup server. The 420R already has some i/o issues and given the increased throughput of the LTO drives I thought this might need replacing as well. We use Netbackup software on the 420R is that has any bearing on the answer.
regards,
Paul

Hi Greg,
Backup rserver as you know would be configured with standby keyword. When primary server will be Operational (probe passed)
- Existing connections on backup keep accessing backup.
- For new connection requests ACE looks up sticky entries, if there's already an entry for backup server, the connection is sent to the standby rserver.
- If a new client request (connection) doesn't match any sticky entry for backup rserver ACE forwards this request to primary.
Let me know if you have any questions.
Regards,
Kanwal
Note: Please mark answers if they are helpful.

ACE real server rate liiting

Hi,
If the ACE is configured to rate limit the traffic to a given real server to a certain bandwidth, what happens to the traffic that exceeds the specified limit ? Does the ACE drop this traffic in all cases as the documentation says ? Or can we configure the ACE to bypass this traffic either without any load balancing or to a backup server ?
Thanks and regards

That sounds good, When there is excess traffic, all the new connections would be sent to the serverfarm representing the DG. Now when the traffic level of the cache due to the existing connections decrease below acceptable levels, the ACE will again bring it in to rotation.
Cool, One question though. What happens if there are two caching servers, and we want to implement the same to both the servers. I'm thinking the net effect would be similar. But would there be any caveats ?

Connecting backup server to brocade switch help

Hi all
We are implementing a new backup server for our SAN, the server currently had one connection to our brocade switch, is it possible to put a second connection to the brocade switch from the server? and will it team them or become a failover connection, I believe the FC card in the server is Q Logic
hope you can help
thanks
Carl

There are no restrictions whatsoever to how many ports you use to connect from your server to the switch. I had a single server that used 16 ports to each switch.
I was wrong with the first post as I got sidetracked talking about how FC does trunking. You can't trunk from the server to the switch. It does from switch to switch though. The server multipathing software manages the traffic to the storage array normally in a round robin approach.
If you just have a backup server <-> switch <-> FC tape drive, the traffic is managed by the backup media agent. Backups are pretty simple as tape drives are just one thing. They are not like storage arrays.
As far as broadcast goes, look up RSCN.
FC networking is different to IP so get a book and read up about it.

Hot backup server

Hi everybody.
I would like to have one server active and a passive
backup server, which is ready to take over in case the
active one crashes. It is important that the failover times
are around 1 second. The active server is handling all
the requests, the backup server is just standing by. It is
OK if, for example, all the software is loaded on both
servers and the state is mirrored to the passive server all
the time.
How could I do that? Can I do it with Sun Cluster or
should I use some other software framework?
Thanks in advance.
Niels

One second fail over time? So what kind of data service?
Assuming its a database you would be looking at very expensive special hardware and software to achieve this. Oracle Parallel Server (OPS) worse case times are less that a minute and HA oracle will go up from there. All this would depend on the database size and workload.
Think you will be after a fault tolerant and not highly available system.

Recently backing up my ipad onto my macbook, which is the backup server for all of my gadgets. This includes all my photos and tons of music. The macbook said it could not backup the ipad because there was insufficient disc space to do so. What now?

I have a macbook operating OSX10.6.7. Recently backing up my ipad which had lots of photos from a recent vacation. I use this laptop as the backup server for all of my gadgets so it has thousands of photos and tons of music. It just told me that it couldn't back up the ipad bc there wasn't enough disc space. I was afraid that this would happen eventually. What next? Newer laptop with more space? I'm not sure what files I could sacrifice to free up more space as most of these are important.

What size hard drive do you have in your MacBook? The cheapest options are, a larger internal hard drive, or an external drive. Or you could get a cheap desktop PC and network to it for storage. I've got one that lives in the hall with 3 Terabytes (That's 3000gb) of storage.

How do I restore a Windows Backup Server backup recovery partition?

I'm trying to test restoring a backup from our real server on a temp server.
First, I was surprised it can't do a restore to a smaller drive because the original server is only 1/3 full (it wants to restore all the empty bytes too).
Also it appears it wants to see that target partitions are already created.
It wants to restore recovery to an EXISTING recovery partition and OS to an existing OS partition all with exact sizes.
What if the old system died and I had to go to something new?
Do I have to preinstall 2012 R2 on a bare drive so it creates the partitions?
I've been down this path before, if it's not byte for byte match (offsets and all) it won't boot.
I'm pretty sure I could restore just the OS partition and then do a Windows Repair which would move the master boot record onto the OS drive. But that seems wrong.
What's the proper way to restore?
Is Windows Backup Server to limiting?

Hi,
1. When trying to recover a partition, it requires a same or larger target partition. If you only backup data, there is no size limitation of the target partition.
2. We need an operation system to do the recovery. However you can perform a Bare Metal Backup so it could be restored without operation system - but it may force to backup more than partition C.
If you have any feedback on our support, please send to [email protected]

Service Accounts for Reporting Service in SQL Server Failover Cluster setup

I am setting up 2 Report Services (SSRS) in SQL Failover Clustering (Version: 2012SP1) on Windows 2012, as part of scale out architecture.
There are 2 options to configure the service account for SSRS:
Option 1) Using domain accounts, as what I have done for DB Engine and SQL Agent.
Option 2) accept the default, which is virtual account for SSRS. Per documentation URL:
http://msdn.microsoft.com/en-us/library/ms143504.aspx
which is the recommended one? is it option 2?
There is security note on above URL as well, but does not clearly mention that option 1 is not recommended.
Security Note: Always run SQL Server services by using the lowest possible user rights. Use a MSA or virtual account when possible. When MSA and virtual accounts are not possible, use a specific low-privilege user account or domain account instead
of a shared account for SQL Server services. Use separate accounts for different SQL Server services. Do not grant additional permissions to the SQL Server service account or the service groups. Permissions will be granted through group membership or granted
directly to a service SID, where a service SID is supported.
Thanks very much for your help!

Hi Luo Donghua,
In SQL Server Failover Cluster Instance, personally two options can run well. If you use the virtual account for SQL Server Reporting Service. Virtual accounts in Windows Server 2008 R2 and Windows 7 are managed local accounts that provide the features to
simplify service administration. The virtual account is auto-managed, and the virtual account can access the network in a domain environment.
Of cause, you can also use domain accounts in your clustering.
Just make sure your service account is set up here, or that it is using a proper built-in account.For more information, see:http://ermahblerg.com/2012/11/08/cluster-ssrs-in-2008/
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

The host is not authorized to connect to this Backup Server

Hi experts,
I'm trying to connect to a remote backup server S2_BS running on VM2 from a data server S1 running on VM1. When I issued following command in isql
1> SYB_BACKUP...sp_who
2> go
Msg 7221, Level 14, State 2:
Server 'S1', Line 1:
Login to site 'SYB_BACKUP' failed.
It failed to connect to its SYB_BACKUP (i.e. S2_BS is configured for SYB_BACKUP in this case).
And I got following error in the error log of S2_BS:
Jun 23 14:48:53 2014: Backup Server: 2.24.2.1: The host '10.43.13.204' is not authorized to connect to this Backup Server.
Jun 23 14:48:53 2014: Backup Server: 2.6.2.10: Login information unavailable.
I can ping VM2 from VM1 without any issue:
$ ping 10.43.13.204
PING 10.43.13.204 (10.43.13.204) 56(84) bytes of data.
64 bytes from 10.43.13.204: icmp_seq=1 ttl=64 time=0.035 ms
And have entry for S2_BS in /opt/sybase/interfaces on VM1:
S2_BS
master tcp ether 10.43.11.19 5002
query tcp ether 10.43.11.19 5002
And S2_BS is running correctly on VM2.
I'm running ASE 15.7 SP110 on both VM1 and VM2.
Could someone please let me know how to fix this?

The message is due to a new security feature. See Remote Dump Host Control
for details on how to register your host with the remote backupserver.
-bret

How to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)

I have a scenario with the three nodes with server 2012 standard, each running an instance of SQL Server 2012 enterprise, participate in a
single Windows Server Failover Cluster (WSFC) that spans two data centers.
If the nodes in the primary data center are unavailable due to data center outage. Then how I can able to access node in the WSFC (Windows Server Failover Cluster) in the secondary disaster recovery data center automatically with some script.
I want to write script that can be able to check primary data center by pinging some IP after every 5 or 10 minutes.
If that IP is unable to respond then script can be able to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)
Can you please guide me for script writing for automatic failover in case of primary datacenter outage?

please post you question on failover clusters in the cluster forum. THey will explain how this works and point you at scipts.
You should also look in the Gallery for cluster management scripts.
¯\_(ツ)_/¯

How to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster) with scrpiting

I have a scenario with the three nodes with server 2012 standard, each running an instance of SQL Server 2012 enterprise, participate in a
single Windows Server Failover Cluster (WSFC) that spans two data centers.
If the nodes in the primary data center are unavailable due to data center outage. Then how I can able to access node in the WSFC (Windows Server Failover Cluster) in the secondary disaster recovery data center automatically with some script.
I want to write script that can be able to check primary data center by pinging some IP after every 5 or 10 minutes.
If that IP is unable to respond then script can be able to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)
Can you please guide me for script writing for automatic failover in case of primary datacenter outage?

You are trying to implement manually what should be happening automatically in the cluster. If the primary SQL Server becomes unavailable in the data center, it should fail over to the secondary SQL Server automatically. Is that not working?
You also might want to run this configuration by some SQL experts. I am not a SQL expert, but if you have both hosts in the data center in a cluster, there is no need for replication between those two nodes as they would be accessing
the database from some form of shared storage. Then it looks like you are trying to implement Always On to the DR site. I'm not sure you can mix both types of failover in a single configuration.
FYI, it would make more sense to establish a file share witness in your DR site instead of placing a third node in the data center for Node Majority quorum.
. : | : . : | : . tim

ACE Backup-server failover

Similar Messages

Maybe you are looking for