Hej Kjell I had a look at Azure some time ago, the showstopper for me was the SLA, in order to get 99.95% uptime you had to use availability sets, as Azure would reboot your virtual machine for platform maintenance, and leve the other(s) in the availability sets online. For this to work, Firebird has to provide a Active/passive solution. However there is now a 99.9% Uptime SLA on single VM’s (https://buildazure.com/2016/11/24/single-instance-vms-now-with-99-9-sla/)
I believe that the planned platform maintenance is exclude from those 99.9% and from what I can read you have to manually move your server single instance VM’s to avoid downtime. From: firebird-support@yahoogroups.com [mailto:firebird-support@yahoogroups.com] Sent: Wednesday, June 21, 2017 12:09 To: firebird-support@yahoogroups.com Subject: [firebird-support] FB in Azure VM? Hi, We're considering a move from dedicated server (at a hosting provider) to hosting "everything" in the cloud, namely Azure. They don't provide FB as "app as a service", so we're forced to go with a VM where we maintain our own FB installation, which is not a problem per se, but means we'll have to manage it more ourselves. What experiences do you have with deploying FB in an Azure VM or similar? If I understand MS correctly, they can provide a locally mounted high-performance disk, but I'm not sure if they can provide mirroring, e.g. RAID 1. On our dedicated server we have a local RAID 1 volume (mechanical 10k or possibly 15k rpm SCSI) for the databse, and make full nightly backups. Forced writes off. Transaction load isn't very high, but we do need to be able to execute long-running and "heavy" queries while at the same time a web app makes short transactions that require short response times. I'd like to know if you think the cloud VM approach for a FB installation is viable, any special consideration we should be aware of, etc. I do know that the wire protocol is not very efficient if the network latency is high, so you don't have to mention that aspect. I.e. we're probably better of having both FB and the apps hosted in the same cloud... But... do you know if this is a problem if FB is in an Azure VM and the app is hosted in an Azure App Service? Network latency ok in that scenario? Regards, Kjell -- Marknadsinformation logotyp Kjell Rilbe Telefon: 08-761 06 55 Mobil: 0733-44 24 64 Marknadsinformation i Sverige AB Ulvsundavägen 106C 168 67 Bromma www.marknadsinformation.se<http://www.marknadsinformation.se> <http://www.marknadsinformation.se> 08-514 905 90 Företagskontakt.se <http://xn--fretagskontakt-vpb.se> Personkontakt.se <http://personkontakt.se> [Non-text portions of this message have been removed] Venlig hilsen Thomas Kragh, Udvikler [uvdata logo] A part of KMD Stigsborgvej 60, 9400 Nørresundby E-mail t...@uvdata.dk Web www.uvdata.dk<http://www.uvdata.dk> Telefon +45 72287030 [http://res.uvdata.net/mailsignatur/kmdsammenudviklervidanmark.jpg] Vi gør opmærksom på, at denne e-mail kan indeholde fortrolig information. Hvis du ved en fejltagelse modtager e-mailen, beder vi dig venligst informere afsender om fejlen ved at bruge svarfunktionen. Samtidig beder vi dig slette e-mailen i dit system uden at videresende eller kopiere den. Selvom e-mailen og ethvert vedhæftet bilag efter vores overbevisning er fri for virus og andre fejl, som kan påvirke computeren eller it-systemet, hvori den modtages og læses, åbnes den på modtagerens eget ansvar. Vi påtager os ikke noget ansvar for tab og skade, som er opstået i forbindelse med at modtage og bruge e-mailen. Please note that this message may contain confidential information. If you have received this message by mistake, please inform the sender of the mistake by sending a reply, then delete the message from your system without making, distributing or retaining any copies of it. Although we believe that the message and any attachments are free from viruses and other errors that might affect the computer or it-system where it is received and read, the recipient opens the message at his or her own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this message.
