2014-03-03 54 views
5

我正在嘗試將虛擬機大小從-8個內核,14 GB更改爲6 - 4內核,28 GB用於我的MSSQL Azure IaaS服務器之一。無法通過Azure管理門戶增加虛擬機大小

我收到以下錯誤:

Unable to upgrade the deployment. The requested VM size may not be available in the resources supporting the existing deployment. Please try again later, try with a smaller VM size or smaller number of role instances, or create a deployment under an empty hosted service with a new affinity group or no affinity group binding. The long running operation tracking ID was: 1d8145d1977877978d1d8dffdd045d83.

我明白,有從一個訂閱多少人能得到限制。但是,這是實時服務器,我有另外4臺服務器在同一訂閱下運行。有什麼辦法可以將此虛擬機從一個訂閱移動到另一個訂閱?

否則,增加此服務器大小的正確方法是什麼?

請提前通知。

+1

我建議您聯繫支持。 – codingoutloud

+1

訂閱中有多少核心,目前有多少核心正在使用? – BrentDaCodeMonkey

+0

@codingoutloud隊友我已經和支持部門談過了。 – codebased

回答

5

我從支持部門得到了答案:

When customer initially deployed service it got deployed under the cluster which does not support high memory VM's. Since customer is having deployment under the hosted service it cannot be pinned/migrated to a cluster which supports A6 or higher VM size. This is a by design behaviour as of now. Unfortunately, the only way customer can deploy a A6 VM is to delete and recreate deployment with A6 size under the given hosted service. When customer tries to create it, then he/she will be allocated a cluster which supports A6 or higher VM size.