Restoring a VM that has been deleted, correctly restores the VM. Is there any way of backing up the associated VM RBAC role assignments so that we dont have to manually recreate them after restoration ?
Related
I have created a backup plan for a test cluster and created a manual backup of cluster. I have restored the cluster to another cluster when cluster is alive with restore plan. when I have to test for disaster scenario, I have deleted original cluster, the backup plan associated with cluster also got deleted but backups are present.
when i tried to create a new restore plan it says only alive cluster backup plans will be selected. I have a backup of cluster but i can not restore into another cluster.
Any other solution to restore cluster with GKE Backup-restore agent in GCP in above scenario where backups are present but backup plans are not there.
Hope all are safe and doing well.
I have few running servers on google cloud and for them, snapshots are scheduled on daily basis in an incremental way.
I am trying to create a new instance on a different VPC zone by using the same snapshots but it will be giving me an error.
For reference, I have added an attachment to this question.
Please help me to resolve this issue and thanks in advance.
Assuming that you have created a Snapshot with Application consistency(VSS) enabled:
When you create a VSS snapshot, Windows Server marks the volume in the
snapshot as read-only. Any disks that you create from the VSS
snapshot are also in read-only mode. So, the read-only flag on the new
boot disk prevents the VM instance from booting correctly.
You can follow this documentation to resolve your issue here.
If the disk you created from the VSS snapshot is a boot disk and you want to use it to boot a VM instance, you must temporarily attach the disk to a separate, existing VM instance. Once you complete the following steps, you can detach the disk from that existing VM instance and use it to boot a new VM instance.
When creating an AMI image from an existing EC2 instance, does it require the restart of the existing instance?
I make a copy of the instance, and subsequently the server went down because it turned off a process monitor which led to downtime, but I can't remember if it was because I rebooted the system (I can't remember if I rebooted it), or if it was because I made a copy of the image.
There's option to enable No reboot during create AMI
When creating an AMI image from an existing EC2 instance, does it require the restart of the existing instance
to answer this yes, when ami is being created aws the instance for ensuring data integrity.
doc says this "Amazon EC2 powers down the instance before creating the AMI to ensure that everything on the instance is stopped and in a consistent state during the creation process."
you can override this behaviour by enabling no reboot while creating ami.
No reboot – This option is not selected by default. Amazon EC2 shuts down the instance, takes snapshots of any attached volumes, creates and registers the AMI, and then reboots the instance. Select No reboot to avoid having your instance shut down.
refer 6 point of this https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/creating-an-ami-ebs.html.
also whenever you are unsure about anything just follow the docs of that service, it will be define in one way or the another.
I accidentally deleted my ai notebook vm and I hadn't downloaded the notebooks connected to it. I still have the url. Does anybody know if there's a way for me to recover my work?
According to the documentation, there is a life cycle for the instances. Verify the state of your AI Notebook VM to make sure that it is deleted or just turned off.
Unfortunately, if an AI Notebook instance is deleted and there is no snapshot configured, there is no way to restore that instance neither recover the notebooks stored there. There are three ways to prevent this from happening in the future:
Create snapshots to periodically or schedule back up data from your zonal persistent disks (snapshot can be located in multiple zones) or regional persistent disks (You must indicate the region where the disk is located ).
Edit VM instance, go to the deletion protection checkbox to enable it as this option is disabled by default. This setup will avoid that your Notebook instance was deleted by accident.
In the VM instance, go to boot disk, in the drop down list under “When deleting instance” select “Keep Disk” (or you can use gcloud command to disable set-disk-auto-delete)
In case any VM instance gets deleted accidentally then is there any way to recover it in Dataproc cluster. In case there is no way to recover a deleted VM instance then can we create a new VM instance and connect to an existing DataProc cluster?
Please suggest.
There is no way to recover data on deleted VMs. Also manually removing workers carries a possibility of bricking the cluster. If your goal is to shrink the cluster we recommend option #1 below.
There's a few ways to add back a deleted VM:
Resize the cluster down and up using gcloud dataproc clusters update --num-workers, you'll want to ensure the deleted VM is in the set of VMs to be removed by downsize operation (this is not always possible)
From Developers Console go to Compute > Instances select any regular worker VM and clone it such that name matches the deleted VM.
Both of these approaches carry identical billing implications.