For deploy tableau server, can i deploy tableau server HA in three-node configuration on Azure Virtual Machine like this link : High Availability Installations (HA) Three-node configuration
How i do? who have experience about deploy tableau environment on Azure, please advise me.
Yes, running Tableau Server on a Microsoft Azure VM is an excellent choice if you want the flexibility of scaling up and scaling out without having to purchase and maintain an expensive fleet of servers.
For instance, you can configure Tableau Server as three-node to be highly available, and integrate with all of the common enterprise applications (for example, Active Directory) that many organizations rely on.
For more details, you could refer to:
Install Tableau Server on Microsoft Azure
Example: Install and Configure a Three-Node HA Cluster
Related
I'm trying to build a Decentralised social media platform using Cassandra. To do this I would like the instances or nodes of the Cassandra database to be hosted on the clients side rather then having it hosted on the cloud. I would like to know if it would be possible for the user to somehow run an instance on their side with part of the data. This will allow the information to be distributed between many computers globally.
You can deploy Cassandra nodes:
on-premise,
on a private cloud,
on a public cloud, or
a hybrid environment of on-premise + cloud.
It is also possible to deploy Cassandra on any combination of the above. Cheers!
I wanted to pull the data from my on-prem server ( hive or oracle ) to Azure data factory. Whereas i am facing issues can you help me in this?
I am asking this on the basis of enterprise issue. I wanted my integration Runtime to be in Onprem server , currently we are installing it in our own laptops and if our laptop is shut down then obviously IR is stopped and data won't be loaded this can't be feasible in production.
Do anybody know that what is meant installing IR in my on prem server? that means in my hive server?
Your help will be really appreciated.
Your SHIR server does not have to be on the same server as your data source. But it should be close to it. Same region or same data center.
You need a server that is always powered and running. Refer to the documentation.
If you want high availability you should refer to this link.
If you want DR, you will need another SHIR on a DR server in your secondary region.
You can also install the SHIR onto a VM running on the cloud. But your Onprem network needs to be connect to the Cloud VNET using Express route or a VPN.
Laptops is fine for testing but as you said, not for production.
Your IT team should also take care of the patching and updates/maintenance of the new server whether it is on prem or on cloud.
I have deployed Azure Migrate appliance but it seems it can only connect to vCenter server and not a standalone ESXi host. The same seems to be the case with Azure Vmware Solutions by Cloud Simple.
Are there any other simple ways of migrating workloads to Azure ?
Treat it like a physical server and migrate. I have done thousands of VMs this way for a large customer.
https://learn.microsoft.com/en-us/azure/migrate/tutorial-migrate-physical-virtual-machines
Azure at this time only supports Azure Migrate through a VCSA and not a standalone ESXi host.
I have my Application running on AWS containing component as:
Multiple EC2 Instances (3 RHEL as Application Server, 1 Ubuntu as a File Server, 1 Ubuntu as a CronJob Server, 1 Windows as Bastion).
MySQL RDS Instance.
Barracuda WAF as an Instance (Implemented from Marketplace).
Route 53.
Now I want to migrate to Azure. Is there any tool available (free or paid) using which I can migrate whole infra?
I know there are separate steps to move each type of resource separately like ASR for VM etc. But I want to know any standalone tool that will do it for me, with all data. If not, then what are the best steps for migrating each resource separately?
Tools are good, but are no magical, we can also take some best practices to migrate resources from AWS to Azure.
1) Multiple EC2 Instances (3 RHEL as Application Server, 1 Ubuntu as a
File Server, 1 Ubuntu as a CronJob Server, 1 Windows as Bastion) .
For this Windows OS & Red Hat Enterprise Linux on EC2, you can Migrate VMs from AWS to Azure with Azure Site Recovery.
However, these EC2 instance should be running the 64-bit version of Windows Server 2008 R2 SP1 or later, Windows Server 2012, Windows Server 2012 R2 or Red Hat Enterprise Linux 6.7 (HVM virtualized instances only). The server must have only Citrix PV or AWS PV drivers. Instances running RedHat PV drivers aren't supported.
For Ubuntu on EC2, you can refer to this blog to migrate VM from AWS to Azure.
2) MySQL RDS Instance .
You can use common tools such as MySQL Workbench, Toad, or Navicat to remotely connect and import or export data into Azure Database for MySQL.
Use such tools on your client machine with an Internet connection to connect to Azure Database for MySQL. Use an SSL-encrypted connection for best security practices, as described in Configure SSL connectivity in Azure Database for MySQL.
You can create Amazon RDS Read Replicas for your database instance so that you needn't to shutdown your database. However, I'm not sure how long down time will you have. Because it's just for you database.
See more details about Migrating your MySQL database by using import and export in this document.
There is also a blog for this.
3) Barracuda WAF as an Instance (Implemented from Marketplace) .
Barracuda WAF is also available in the Marketplace in Azure. You can just go to azure portal and search Barracuda WAF. Then you see there are many types of Barracuda WAF for you to choose.
4) Route 53 .
On Azure , you can use Azure DNS to achieve this. You can refer to this blog to see details how to delegate DNS domain from AWS to Azure.
Hope this helps!
Sure export and import will work but it can have huge downtime depending on size of data.
If you want zero downtime; then you should first create Read replica from AWS to Azure and then migrate the read replica to master.
I think the best bet would be you do it on your own so that you have understanding of how it works which can further enhance your abilities to troubleshot.
That being said Like AWS have CLoudformation , Azure has Azure Resource Manager , you can create template in JSON like you do in AWS Couldformation and Deploy For Example :
In Cloudformation we have AWS::EC2::Instance you have Microsoft.Compute/virtualMachines in Azure.
You Can Refer this very informative Blog Post and Azure Documentation For Same.
Hope this Helps!
I have just started exploring Azure Service Fabric & I'm finding the concepts involved a little overwhelming
Consider these 2 statements -
"Service Fabric is agnostic to the underlying hosting provider. You
can run it in Azure, you can run it on AWS, you can run it on 5
laptops - it doesn't matter."
"Azure Service Fabric for Windows Server..can be used
to..provision Service Fabric clusters in their own datacenters or
other cloud providers, and run production workloads"...any Windows Server environment...there is no real lock-in to Azure as a cloud platform
As per my understanding,
1) in Azure, app can be deployed to "Azure Service Fabric" PaaS platform.
2) On a local development machine, it can be deployed to physical or virtual machine(S) that support Azure Service Fabric SDK
3) On "other cloud providers", "Azure Service Fabric for Windows Server" has to be installed(?) on VMs before app can be deployed.
So when an app runs on Azure, it is the "Azure Service Fabric" PaaS platform but if it is deployed to any other cloud provider, it is in an IaaS mode and the maintenance of the SF infrastructure & supporting functions have to be done by deployer of the app
Is my understanding correct?
Is there any documentation on running Service Fabric on non-Azure cloud like AWS?
Can someone elaborate on the purpose of "Azure Service Fabric for Windows Server" & Azure Service Fabric SDK?
When using Azure as the cloud platform to host your Service Fabric cluster then you get some benefits from being able to setup and manage (some aspects of) your cluster directly in the Azure portal, as well as connecting it to other Azure resources such as Azure Key Vault for storing your cluster certificate securely and OMS/Azure Log Analytics for analyzing your log data from the cluster. You still get a set of IaaS resources created for you though when you set up a Service Fabric cluster in Azure, a minimum of the following IaaS resources are at least created for you:
Virtual Machine Scaleset
Public IP address
Virtual Network
Load Balancer
Storage accounts
Depending on the number of nodes and nodetypes there may be multiple instances of these. Each of the nodes are in turn a VM running (by default) Windows Server 2012 R2 Datacenter (you can change that in your template as well).
Running Azure Service Fabric on Azure is not really a PaaS solution, you are far to much in contact with the supporting infrastucture for that to be true. It is a mix of IaaS and PaaS I would say.
On you local development machine you can run a local development cluster that emulates running a 1 or 5 nodes cluser on you local machine. It is only intended for development and there are some features of this local cluster that will behave differently (for instance, you cannot run a reverse proxy there). https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-get-started
If you want to run Service Fabric on any other platform than Azure, such as an on premice data center or in another cloud platform (AWS for instance), then you should look at Create and manage a cluster running on Windows Server. You will then need to create an infrastructure similar to the infrastructure created by Azure when you create an Azure Service Fabric resource directly in Azure. You will need to create a number of VMs (or physical machines) with Windows Server 2012 R2 (or later) that are connected on the same network (virtual or physical) and you will likely need some form of load balancer. When you run Azure Service Fabric in this way you are yourself responsible for maintaining your infrastructure in terms of monitoring and maintaining them (patching the OS on your VM's, monitoring the network for vulnerabilities, etc.).
There is also a preview for running Service Fabric on Linux machines but it does not support Standalone installations yet. https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-linux-overview.
When you have your Service Fabric cluster running on either Azure, local development cluster or as a Standalone cluster, then you could in a way consider that installation as your PaaS platform for adding new microservices.