I have a Compute VM attached to a persistent disk instance. I was deleting my other unrelated projects and had downgraded my related firebase project. Somehow, the VM turned off and the disk is stuck at restoring since the last 3 hours. The disk did not have any snapshot. Any way to restore it?
Related
I have GCP instance.
My Database size was 300GB.
but the instance size was growing to 10TB.
where my remaining size going?
I have running ongoing replication from AWS DMS to GCP .
Please help me.
Thanks
Probably your bin logs/wal logs have grown a lot without you noticing it, you can check for this at metrics explorer and check for the detailed storage of your instance. There is no way in GCP to shrink the disk on your own so you will have to either migrate your instance into a new one with an smaller disk or open a ticket to Cloud Support and ask them to shrink your disk once you configure your instance properly
I have a question regarding GCP Persistent Disk (SSD). I created a disk, I created a VM to which I added the disk. Then I ssh'd into the VM, I saw the disk, I formatted it and mounted it to my VM. Everything worked just fine, I was able to create some files there and use it as a normal disk. However, when I deleted the VM and created another VM some time later, mounted the same disk, the data seemed to be lost, I didn't see it.
This contradicts the name "persistent" which means I might be doing something wrong or misunderstanding something. I would be greateful for any help.
It would help if you had posted your VM configuration, but if I had to guess you had the disk deletion rule in your VM set to delete the disk when you deleted your VM.
Edit your VM and make sure the "Deletion rule" setting is set to "Keep disk."
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.
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)
My VM from Virtualbox crashed when I attempted a snapshot. Unfortunately I lost some pretty important data as the VMDK was corrupted. The VM then reverted to a prior snapshot on reboot.
I luckily saved the VMDK files prior to restarting the VM and am now trying to recover the data. I've tried mounting the VMDK but when I do it's like the VMDK that gets mounted is the default snapshot from day 1 w/no changes. I configured my VMDK file to be dynamic and be segmented in 2GB chunks as it grows so I'm thinking the changes from these files aren't loading when I mount.
Any other suggestions?
If you still have the Snapshot and all its files. You cloud try to create a clone from the snapshot, when that is done you could try to mount and repair its virtual hard drive. You also could try merge snapshots by commandline.