Is it possible to recover some folders from a google cloud VM which was deleted 1 month back.
My VM got deleted after the trial period was over. I want to recover the VM or at least recover some folders from that VM.
I checked in the snapshot section, there is no snapshot of the deleted VM.
Once your GCP free trial ends, you have 30 days to upgrade your account and save your data. Once the 30 day grace period ends, your data and resources are permanently deleted.
Related
I had Composer 2 instance and deleted it, but for some reason still being charged a few bucks for Cloud Composer Compute mCPUs and Cloud Composer Compute Memory. Could those be delayed charges or something? I thought it might be, but it has been a couple of days and i am still seeing charges. Cloud Composer Environment Fee is not being charged after deletion, it is only CPU and Memory.
Tried contacting support but no reply yet.
Anyone had the same situation?
Thanks!
I forgot to delete the persistent disk. Deleting the Cloud Composer environment does not delete its persistent disk.
https://cloud.google.com/composer/docs/composer-2/delete-environments
I lost my vm instance and a huge amount of data with it. I even paid the pending amount to google but when i went to the vm instance page, it is showing only create instance menu. How can i recover my old vm instance. Please help
As #John Hanley mentioned in comments " When a Google account is closed, GCP may impose an internal recovery period of up to 30 days, depending on past account activity. Once that grace period expires, it is marked for deletion ."
I am fairly new to Google Cloud platform and cloud computing as a whole. I had af1-micro (1 vCPU, 0.6 GB memory) type of instance running. GCP gave me a warning that the instance was overutilized and I should change it to g1-small (1 vCPU, 1.7 GB memory) type of instance. When I went to upgrade, it began to restart my instance but gave me the error
Starting VM instance '<instance name>' failed. Error: The zone 'projects/<project id>/zones/asia-south1-a' does not have enough resources available to fulfill the request. Try a different zone, or try again later.
I have waited for some time (more than 12 hours) to start it again and getting the same error. I edited the instance manually and changed it to g1-small (1 vCPU, 1.7 GB memory) but still getting the same error.
I tried moving the instance to a different zone in same region using move instances in google cloud SDK Shell, but got an error and found out that instances in terminated state cannot be moved.
I just need to get my instance up and running, so please help here.
Did some further investigation. Indeed the resource shortage is still ongoing in the region. However changing the machine type to E2-micro/small then starting the instance should work for you.
I faced the same issue and I am still facing it. What I ended up doing is I switched to asia-south1-c.
Finally was able to create a snapshot of a terminated instance from the web console and then create a new VM using that snapshot in a different region. Then deleted the old VM and snapshot.
I know there are automatic snapshots created every 24 hours, and that you can recover point in time in a minute timeframe. But what is the Recovery Point Objective (RPO)? Is this a minute? Or 24 hours because you need the latest daily snapshot? The documentation is not clear about this.
RPO Should be 5 mins https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_PIT.html
RDS uploads transaction logs for DB instances to Amazon S3 every 5 minutes. To determine the latest restorable time for a DB instance, use the AWS CLI describe-db-instances command and look at the value returned in the LatestRestorableTime field for the DB instance. In the AWS Management Console, this property is visible as the Latest restore time for the DB instance. You can restore to any point in time during your backup retention period.
Someone tested it back in 2012 with a powershell script. https://www.yobyot.com/aws/aws-rds-backup-recovery/2016/02/09/
As you can see in the screenshot below, a simple PowerShell script that ran for 20 minutes demonstrates that AWS is, indeed, making that very tight RPO possible. My little test instance was off only twice, by an insignificant minute or so.
Archived Link: http://archive.vn/8ZbuS https://web.archive.org/web/20190102131221/https://www.yobyot.com/aws/aws-rds-backup-recovery/2016/02/09/
Does the DigitalOcean control panel offer a way to delete a backup that has been made for a deleted droplet? (NB: backup, not snapshot)
I created a droplet, enabling backups, and deleted it only a few minutes later. DigitalOcean made a backup of the droplet just before completing the deletion. So now I have a backup with no corresponding droplet. I'm being charged for the backup, and would like to delete it.
ADDENDUM: The control panel offers an option to convert the backup to a snapshot. When I did that, the backup disappeared, but it re-appeared a short time later, after I had deleted the snapshot. This left me right back where I started from.
Thank you.
If you want to make sure your backups are deleted when your droplet is destroyed, make sure that "Scrub Data" is checked.
On DigitalOcean, you can not manually delete an individual backup. Backups are automatically generated, and will be automatically destroyed after a period of a few days once the droplet has been destroyed. As the price of enabling backups is calculated as 20% of the price of the running droplet, you are not charged extra after the droplet is destroyed.
Snapshots, on the other hand, are generated on demand and will persist after a droplet is destroyed until you delete it manually from the Images page of the DigitalOcean control panel.
If for some reason, you need to ensure that the back is destroyed sooner and you didn't check "Scrub Data" just open a support ticket and the DO team can do it for you.