Mwclearning.com Website Review

a lot of people need to do offsite backups for aws rds – which can be done trivially within aws. if you need offsite backups to protect you against things like aws account breach or aws specific issues – offsite backups must include diversification of suppliers. the new (2018) aws data migration service solve offisite rds backup problems create network on azure and place a vm in the network with 2 interfaces. one interface must have an public ip, call this one ‘external’ and the other inteface will be called ‘internal’ – once you have the public ip address of your windows 2016 vm, create a ‘customer gateway’ in your aws vpc pointing to that ip. you will also need a ‘virual private gateway’ configured for that vpc. then create a ‘site-to-site vpn connection’ in your vpc (it won’t connect for now but create it anyway). configure your azure win 2016 vm to make an ipsec tunnel by following these instructions (the instructions are for 2012 r2 but the only tiny difference is some azure vm are trying to connect to each other. ensure that the azure vm has its security groups configured to allow your aws site-to-site vpn to get to the azure vm (i am not sure which ports and protocols specifically, i just white-listed all traffic from the two aws tunnel end points. once this is done it took around 5 mins for the tunnel to come up (i was checking the status via the aws console), i also found need to add routes to your applicable aws route tables and update aws security groups for the azure subnet as required.. 3 – install matching version of oracle on the windows 2016 vm. vm (well atleast pick a size, security group, type etc). note that the security group that you add the replication host to must have access to both your rds and your azure dbs – i could not pick which subnet the host went into so i had to add routes for a couple more subnets that expected. next you will need to add your source and target databases. when you add in the details and hit test the wizard will