I want to create a failover web server using Windows Server 2016. If the first machine fails, the server should move to the second machine. However I'm not really sure which Clustered Role should I use.
Clustered Role Role or Feature Prerequisite
DFS Namespace Server DFS Namespaces (part of File Server role)
DHCP Server DHCP Server role
Distributed Transaction Coordinator (DTC) None
File Server File Server role
Generic Application Not applicable
Generic Script Not applicable
Generic Service Not applicable
Hyper-V Replica Broker Hyper-V role
iSCSI Target Server iSCSI Target Server (part of File Server role)
iSNS Server iSNS Server Service feature
Message Queuing Message Queuing Services feature
Other Server None
Virtual Machine Hyper-V role
WINS Server WINS Server feature
https://learn.microsoft.com/en-us/windows-server/failover-clustering/create-failover-cluster#create-clustered-roles. PS: I want a situation with and without a database.
Related
I have setup a VPN and able to ping the Private IP of EC2 instance from on-premises and vice versa. However, I am unable to the ping the Private IP of DMS Replication Instance.
I have created an endpoint pointing DB in EC2. Endpoint test connection succeeds. However, endpoint test connection fails for DB in on-premises.
The EC2 and DMS Replication Instance use the same Subnet, Security Group etc., The details are given in the image below.
May I know
1) why the DMS instance is not communicating with on-premises (and vice-versa)
2) why EC2 works fine in VPN but not DMS instance?
EDIT:
Details of Security Group associated with the DMS instance:
vpc - the same default vpc used by EC2
inbound rules - all traffic, all protocol, all port range, source = 192.168.0.0/24
outbound rules - all traffic, all protocol, all port range, source = 0.0.0.0/0
Route table:
destination - 10.0.0.0/16, target = local
destination - 0.0.0.0/0, target = internet gateway
destination - 192.168.0.0/24, target = virtual private gateway used in VPN
This is the error message I get when I try to test the DMS DB endpoint connection:
Test Endpoint failed: Application-Status: 1020912, Application-Message: Failed to connect Network error has occurred, Application-Detailed-Message: RetCode: SQL_ERROR SqlState: HYT00 NativeError: 0 Message: [unixODBC][Microsoft][ODBC Driver 13 for SQL Server]Login timeout expired ODBC general error.
You might need to describe/provide your full network topology for a more precise answer, but my best guess, based on AWS' documentation on "Network Security for AWS Database Migration Service", is that you're missing source and target database configuration:
Database endpoints must include network ACLs and security group rules that allow incoming access from the replication instance. You can achieve this using the replication instance's security group, the private IP address, the public IP address, or the NAT gateway’s public address, depending on your configuration.
Also, is this EC2 you mentioned a NAT instance? Just in case:
If your network uses a VPN tunnel, the Amazon EC2 instance acting as the NAT gateway must use a security group that has rules that allow the replication instance to send traffic through it.
PLEASE NOTE: This is not an RDS or a prepackaged EC2 with SQL Server solution. I installed an express copy independently after setting up the EC2 instance.
I am evaluating a free tier instance of AWS EC2. Several months in, I decided to install SQL Server 2014 express on the instance on my own. However I cannot connect to the SQL Server instance via SSMS from another server box local to us.
The following is a checklist of what I have done so far:
SQL Server Configuration Manager
Configured to run SQL Browser
Enabled TCP on the SQL Server instance
Windows Firewall
Created an inbound rule to allow communication on TCP port 1433 and 1434
Created an inbound rule to allow communication on UDP port 1434
AWS security group of EC2 instance where SQL Instance resides
Mirrored the rules above in the Windows firewall for inbound traffic from the local server I'm trying to access the EC2 instance from
Successfully tested if RDP and ICMP work on the instance
I believe my issue lies in the how I am referring to the SQL instance:
ec2-xxx-xxx-xxx-xxx.compute-1.amazonaws.com\INSTANCE_NAME
I've also noticed that when I log in on the EC2 instance's copy of SSMS, there is a two part name like so:
WIN#########\INSTANCE_NAME
Please help as I feel I've exhausted all options. This shouldn't be that impossible.
I have the following situation:
A private enterprise network with a Icinga2 master, monitoring the internal servers. The firewall blocks all inbound access, however all servers to have outbound internet access (multiple protocols, such as SSH, HTTP, HTTPS).
We also have an environment in Azure with 1 publicly accessable VM (nginx) and behind that, in a private network, application servers. I'd also like to monitor these servers. I read that I can set up a Icinga2 satellite (in Azure), that monitors the Azure environment and sends the data to the master.
This would be a great solution. However, my master is in our private enterprise network, so the Icinga satellite can't push any data to the master. The only option would be that the master pulls the data periodically from the satellite(s). It's possible for the master to login via SSH agent forwarding to the servers in Azure. Is this possible or is there a better solution? I'd rather not create a reverse SSH tunnel.
You might just use the icinga2 client and let the master connect to the client (ensure that the endpoint object contains host/port attributes). Once the connection is established the client will send its check results (and historical replay logs even if there).
I have setup a failover cluster in Windows Server 2012 which contains two nodes. I have used Microsoft MSMQ for communication. If I try the write on the queue remotely using the node name DIRECT=OS:mymachine\private$\MyQueueQueue then I am able to write on it but when I use the virtual IP of the cluster then the message got stuck in Outgoing Queues
I have disabled the firewall.
I am able to telnet to the MSMQ port 1801 from node IPs but not able to telnet with the virtual IP which is used by failover cluster
I have a multi tier application that want to use a RAC to improve the availability of the server.
What we have now is, the client side sending a transaction data to the server side through a webservice. At client level, we need to specify the url address (IP address) as a path to send a data.
As for now, there are 2 oracle instance installed as a RAC at a server.
1. 133.38.52.101
2. 133.38.52.102
Both of the server are connect to same Oracle Database (SAN storage).
Let say, the client side is pointing to .101. Suddenly the .101 machine is down, how can I possible to use the .102 without changing the point URL at the client side. Is there any configuration can be done at RAC or Windows Server 2008 for this type of problem?
Use a load balancer between client machine and application server machines.
Use Oracle's transparent application failover functionality in OCI to achieve redundancy and load balancing between application server machines and RAC instances. DML transactions will be rolled back but selects will be transparently failed over.