103 lines
2.5 KiB
Markdown
103 lines
2.5 KiB
Markdown
|
# Migration Storage Issue - Analysis
|
||
|
|
|
||
|
|
**Date:** 2025-01-20
|
||
|
|
**Status:** Issue Identified
|
||
|
|
**Problem:** Direct migration fails due to storage name mismatch
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Problem
|
||
|
|
|
||
|
|
Migration of VMs from r630-02 to r630-01 fails with error:
|
||
|
|
```
|
||
|
|
ERROR: migration aborted: storage 'thin1' is not available on node 'r630-02'
|
||
|
|
```
|
||
|
|
|
||
|
|
**For VMIDs 7800-7811:**
|
||
|
|
```
|
||
|
|
ERROR: migration aborted: storage 'thin4' is not available on node 'r630-01'
|
||
|
|
```
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Root Cause
|
||
|
|
|
||
|
|
### Storage Configuration Mismatch
|
||
|
|
|
||
|
|
**r630-02:**
|
||
|
|
- VMs use `thin1` and `thin4` storage
|
||
|
|
- These storage pools exist on r630-02
|
||
|
|
- thin1 on r630-02 is a different volume group than thin1 on r630-01
|
||
|
|
|
||
|
|
**r630-01:**
|
||
|
|
- Has `thin1` storage (pve/thin1)
|
||
|
|
- Does NOT have `thin4` storage
|
||
|
|
- Storage names are the same but volume groups are different
|
||
|
|
|
||
|
|
**Issue:** Proxmox migration tries to preserve storage names, but:
|
||
|
|
- thin1 on r630-02 ≠ thin1 on r630-01 (different VGs)
|
||
|
|
- thin4 doesn't exist on r630-01
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Solutions
|
||
|
|
|
||
|
|
### Option 1: Manual Config Move + Storage Migration (Complex)
|
||
|
|
|
||
|
|
1. Move VM configs (already done for visibility)
|
||
|
|
2. Manually copy storage volumes using LVM commands
|
||
|
|
3. Complex and risky
|
||
|
|
|
||
|
|
### Option 2: Backup/Restore (Recommended but has issues)
|
||
|
|
|
||
|
|
1. Create backup using vzdump
|
||
|
|
2. Restore to target node with new storage
|
||
|
|
3. **Current issue:** vzdump also fails with same error
|
||
|
|
|
||
|
|
### Option 3: Enable thin4 on r630-01 (If needed)
|
||
|
|
|
||
|
|
If we want to preserve thin4 storage name:
|
||
|
|
1. Create thin4 storage on r630-01
|
||
|
|
2. Then migration might work
|
||
|
|
3. But still has VG mismatch issue
|
||
|
|
|
||
|
|
### Option 4: Use Different Storage Names
|
||
|
|
|
||
|
|
Migrate VMs to storage with different names:
|
||
|
|
- VMIDs 100-130 → thin1 on r630-01 (already exists)
|
||
|
|
- VMIDs 7800-7811 → local or local-lvm on r630-01
|
||
|
|
|
||
|
|
**This requires backup/restore method.**
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Recommended Solution
|
||
|
|
|
||
|
|
### Use vzdump with --remove (if supported) or manual backup
|
||
|
|
|
||
|
|
Since vzdump is also failing, we need to:
|
||
|
|
|
||
|
|
1. **Check if storage volumes can be accessed directly**
|
||
|
|
2. **Use alternative backup method**
|
||
|
|
3. **Or manually copy storage volumes**
|
||
|
|
|
||
|
|
### Alternative: Change VM Storage First
|
||
|
|
|
||
|
|
1. On r630-02, change VM storage to a compatible storage (like `local`)
|
||
|
|
2. Then migrate normally
|
||
|
|
3. Then change storage on target if needed
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Next Steps
|
||
|
|
|
||
|
|
1. Investigate why vzdump fails (may need to check storage access)
|
||
|
|
2. Consider using `dd` or `lvconvert` to copy storage volumes
|
||
|
|
3. Or change VM storage configuration before migration
|
||
|
|
4. Or use shared storage (NFS) as intermediate
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
**Last Updated:** 2025-01-20
|
||
|
|
**Status:** Issue Identified - Solution Investigation Needed
|