Examples of using Multi-az deployment in English and their translations into German
{-}
-
Colloquial
-
Official
-
Ecclesiastic
-
Medicine
-
Financial
-
Ecclesiastic
-
Political
-
Computer
-
Programming
-
Official/political
-
Political
Dropping a Database in a Multi-AZ Deployment.
Best practices for a Multi-AZ deployment with a SQL Server DB instance include the following.
Renaming a Database in a Multi-AZ Deployment.
Multi-AZ deployment- For high availability, set to Create replica in different zone.
Specifies if the replication instance is a Multi-AZ deployment.
For Multi-AZ deployment, choose whether or not you want a Multi-AZ deployment.
Load data before converting the DB instance to a Multi-AZ deployment.
Multi-AZ Deployment: Choose Yes to deploy your DB instance in multiple Availability Zones; otherwise, No.
Combining Provisioned IOPS Storage with Multi-AZ deployments, or Read Replicas.
When working with a Multi-AZ deployment of SQL Server, remember that Amazon RDS mirrors all SQL Server databases on your instance.
You can run your DB instance in several Availability Zones, an option called a Multi-AZ deployment.
When a DB instance is modified to be a Multi-AZ deployment, during the modification it has a status of modifying.
If you want your data load to be as fast as possible,complete the loading before you convert your DB instance to a Multi-AZ deployment.
Using the RDS console, you can create a Multi-AZ deployment by simply specifying Multi-AZ when creating a DB instance.
For Multi-AZ deployment, choose Yes to create a standby of your replica in another Availability Zone for failover support for the replica.
Amazon RDS manages failover by actively monitoring your Multi-AZ deployment and initiating a failover when a problem with your primary occurs.
Choosing a Multi-AZ deployment ensures that your database will failover and continue to be available if the master DB instance goes out of service.
Updated for support for forced failover, Multi-AZ deployment of Oracle DB Instances, and nondefault character sets for Oracle DB Instances.
On Amazon RDS, a Multi-AZ deployment creates a primary DB instance and a secondary standby DB instance in another Availability Zone for failover support.
If you specify that your DB instance should be a Multi-AZ deployment, you are billed according to the Multi-AZ pricing posted on the Amazon RDS pricing page.
If your DB instance is a Multi-AZ deployment, you can force a failover from one availability zone to another when you reboot.
Amazon RDS actively maintains your Multi-AZ deployment by automatically repairing unhealthy DB instances and reestablishing synchronous replication.
If your DB instance is part of a Multi-AZ deployment(using SQL Server Mirroring), then when you fail over, your time zone remains the local time zone that you set.
Running a DB instance as a Multi-AZ deployment can further reduce the impact of a maintenance event, because Amazon RDS will apply operating system updates by following these steps.
However, if the DB instance already uses a Multi-AZ deployment, switching to a Single-AZ deployment for data loading is not recommended, because doing so only provides marginal improvements.