Cloud SQL Tasks:
Task 1 : Edit SQL instance on GCP and suggest in which condition restart required. (5-5 example)
Lets create a SQL instance, and then check the conditions for Edit SQL instance without restart and the ones when needed restart.
The instance is in creating stage.
Lets Start editing.
For edit SQL instance following Updates don’t need restart SQL instance.
Changes in storage :
While changing disk size it dont need to restart the SQL instance.
The instances is edited without restart.
Changes in Data Protection :
By making any changes here , it doesn’t need restart instance.
it doesn’t required Restart.
Enabling Deletion Protection :
By enabling or disabling Deletion protection it doesn’t required restart.
It doesn’t required restart instance
Maintenance :
By making any changes here , it doesn’t need restart instance.
Doesn’t need restart instance.
Query Insights :
By enabling query insights it doesn’t restart instance.
Labels :
By making any changes here , it doesn’t need restart instance.
Changing Backup Location :
By changing Location of backup also doesn’t need restart the instance.
For edit SQL instance following Updates need restart SQL instance.
Multiple Zone to Single zone :
By changing from multiple zone to single zone , it gives a notificatioon for restart.
It gives a notification to restart the instance.
Machine type changes :
By making any changes here, it need to restart the instance.
Creating Flags :
By creating flags ,it needs to restart the instance.
By changing Primary Zone :
By changing primary zone it needs to restart the instance.
Task 2 : Verify the Zonal Failover with an example.
For these we have to create the SQL Instance in multiple zones, if it made in single zone then failover option is not enabled it SQL instance.
So we make a SQL instance in multiple zone.
Now click on the Failover button .
Now Write the instance id and then click trigger failover.
Now you will see the Location is changed from us-central-a to us-central-b.
Because the primary zone is now failover , so secondary zone comes in command.
Now lets try again the FailOver.
write the instance id and click on trigger failover.
Now you see the Location of SQL instance is changed from us-central-b to us-central-a.
Here , secondary zone is in failover , so the primary zone takes te command and use of the database is running continously.
Task 3 : Enable automated backups in GCP sql instances.
Creating SQl instances maked default enable Automated backups, but we can take on demand backups.
Here you see Automated bckups is enabled default. And we can’t disable these setting because they are required for replication and high availabiltity.