如何迁移旧的Google Compute Engine磁​​盘? [英] How to migrate old Google Compute Engine disks?

查看:87
本文介绍了如何迁移旧的Google Compute Engine磁​​盘?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在欧洲使用Google Compute Engine,维护窗口只是点击我们. 自动迁移"不起作用,因此我们所有的服务器都处于脱机状态.从备份恢复期间,我们发现缺少一些文件.

I am using Google Compute Engine in Europe and the maintenance window just hit us. The "automatic migration" didn't work, so all of our servers are offline. During the recovery from backup, we found a few files missing.

我有一个根据带有数据的debian-7-wheezy-v20130617 图片,我正在尝试访问该图片.

I have a persistent boot disk created from the debian-7-wheezy-v20130617 image with data, which I am trying to access.

我想出了两种可能的方法来访问数据:

I came up with 2 possible solutions to access the data:

  1. 使用旧的引导盘创建新的VM.听起来很简单,但是Google进行了一些更改,并且VM无法启动.

  1. Create a new VM with the old bootdisk. Sounds easy, but Google changed something and the VM won't boot.

使用新映像创建新的VM,并附加旧的启动盘.听起来很简单,但是使用良好的旧safe_format_and_mount无法识别旧磁盘.

Create a new VM with a new image and attach the old bootdisk. Sounds easy, but the old disk is not recognized using good old safe_format_and_mount.

有什么想法如何从磁盘访问数据? 迁移文档并没有真正的帮助,似乎他们认为您一直拥有旧磁盘仍在运行的旧VM.

Any ideas how to access the data from the disk? The migration doc didn't really help, it seems they assume you always have the old VM with the old disk still running.

推荐答案

由于磁盘是在迁移到当前v1 API之前创建的,因此必须先升级磁盘以使用嵌入式内核.

As your disks were created before the migration to the current v1 API, before you can re-attach the disk to a new instance, you must upgrade the disk to use an embedded kernel.

这篇关于如何迁移旧的Google Compute Engine磁​​盘?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆