Need full size img.fidx file

A

ady106034

Member
Dec 20, 2022
34
1
13
Hello,

I have PB Server setup. We are taking the backup for proxmox kvm machines. When I got the PBS GUI I can see the size of the img.fidx file as per the vm disk size.

Now, When I login via ssh to pbs server and go to datastore where the backups are being saved.The files are in KB's only.format.How Can I do it.

/XXdatastore/XXname/vm/VMID/

4.0K client.log.blob
324K drive-virtio0.img.fidx
4.0K index.json.blob
4.0K qemu-server.conf.blob
336K total
You can see the size are in KB but on panel it shows full size.Basically I just want to convert the disk file to vmdk format
 
if you want to extract the drive-virtio0.img raw image file you need to use "proxmox-backup-client restore ..." (or the download button on the PBS UI, if the backup is not encrypted)
 
I need to use the proxmox backup image to use in creating the AWS Ec2 .
When I converted the img file to vmdx it saying wrong format while uploading
 
the .img file is in raw format, if you want a vmdk file you need to convert it (e.g., with "qemu-img convert" or a similar tool)
 
I have converted it and imported to Ec2 but getting below error



"StatusMessage": "CLIENT_ERROR : errorType: CLIENT_ERROR message: ClientError: Disk validation failed [Unsupported VMDK File Format]",
 
please post the output of "qemu-img info file.vmdk"
 
Created from PBS Backup IMG file:

image: /opt/homebrew/Cellar/qemu/9.2.3/bin/test.vmdk
file format: vmdk
virtual size: 40 GiB (42949672960 bytes)
disk size: 2.13 GiB
cluster_size: 65536
Format specific information:
cid: 3209677573
parent cid: 4294967295
create type: monolithicSparse
extents:
[0]:
virtual size: 42949672960
filename: /opt/homebrew/Cellar/qemu/9.2.3/bin/test.vmdk
cluster size: 65536
format:
Child node '/file':
filename: /opt/homebrew/Cellar/qemu/9.2.3/bin/test.vmdk
protocol type: file
file length: 2.13 GiB (2288058368 bytes)
disk size: 2.13 GiB
=======================================================

Created from Vm's thin LVM

qemu-img convert -p $INPUTDISK -O $FORMAT -o subformat=streamOptimized $NEWDISK

=====
image: zeeackup.vmdk
file format: vmdk
virtual size: 60 GiB (64424509440 bytes)
disk size: 3.11 GiB
cluster_size: 65536
Format specific information:
cid: 2797474057
parent cid: 4294967295
create type: streamOptimized
extents:
[0]:
compressed: true
virtual size: 64424509440
filename: zeeackup.vmdk
cluster size: 65536
format:
Child node '/file':
filename: zeeackup.vmdk
protocol type: file
file length: 3.11 GiB (3342464000 bytes)
disk size: 3.11 GiB
 
then ask their support why they don't accept it, the file looks okay.
 
the file is a valid vmdk file, please ask their support about their limitations!
 
You must log in or register to reply here.
Top Bottom