topic I see, I am looking at that in Wireless

Prime Infrastructure Backups

Neville Price — Mon, 05 Jul 2021 13:29:12 GMT

I am currently trying to restore an application backup from PI 2.2.0 to PI 3.0 I have tried a number of backup files taken over the last few days, but each attempt comes back with an invalid backup file. I have PI 2.2.0 on an appliance and PI 3.0 on a virtual environment. Can anyone help with this please?

Initiating restore. Please wait...
Restore Started at 02/01/17 14:46:52
Stage 1 of 9: Transferring backup file ...
-- completed at 02/01/17 14:52:11
Stage 2 of 9: Decrypting backup file ...
-- completed at 02/01/17 14:53:04
Stage 3 of 9: Unpacking backup file ...
ERROR: Unpacking backup file failed. Invalid backup file. Please retry restore with another backup.
% Backup file could not be unpacked

- Possibly not enough disk

Mark Elsen — Thu, 02 Feb 2017 13:40:05 GMT

- Possibly not enough disk space, (on the partition that is being used for the Unpacking); if possible this could be tracked by watching the partition usage(s); while the backup is being processed. Check if something is gettting near 100% full (e.g.)

Thanks. I will have a look at

Neville Price — Thu, 02 Feb 2017 14:59:05 GMT

Thanks. I will have a look at this, I am at present taking a back up from Pi2.2.0 to a remote server with plenty of space. When this has finished I will attempt to restore to the new PI 3.0 VM Server. I will coment on the success or failure of this attempt.

- I understand, but I am

Mark Elsen — Thu, 02 Feb 2017 15:12:02 GMT

- I understand, but I am especially talking about the available space on the target PI 3.0 server

I see, I am looking at that

Neville Price — Thu, 02 Feb 2017 15:36:35 GMT

I see, I am looking at that now, Backup file was 320G but I believe this file is compressed, please see below the disk space on PI3.0

/dev/mapper/smosvg-rootvol	3430800	332080	9
/dev/mapper/smosvg-varvol	3644356	118524	3
/dev/mapper/smosvg-optvol	904261904	31333576	3
/dev/mapper/smosvg-tmpvol	1829876	36496	2
/dev/mapper/smosvg-usrvol	5243212	1319232	20
/dev/mapper/smosvg-recvol	84616	5664	6
/dev/mapper/smosvg-home	84607	5673	6
/dev/mapper/smosvg-storeddatavol	9238556	153696	2
/dev/mapper/smosvg-altrootvol	84616	5664	6
/dev/mapper/smosvg-localdiskvol	171673560	676428	0
/dev/sda2	88343	5687	6
/dev/sda1	452369	17875	4
tmpfs	10551896	1724988	14

Ok, but as stated; you

Mark Elsen — Thu, 02 Feb 2017 15:48:47 GMT

Ok, but as stated; you should try to followup on these values, at regular intervals, when the backup-restore is being processed on the new Prime server.

Ok just running the restore,

Neville Price — Thu, 02 Feb 2017 16:01:32 GMT

Ok just running the restore, I will keep an eye on the values.

Hi

Neville Price — Thu, 02 Feb 2017 16:07:13 GMT

None of the values changed at all, the restore failed as before

Initiating restore. Please wait...
Restore Started at 02/02/17 15:59:39
Stage 1 of 9: Transferring backup file ...
-- completed at 02/02/17 16:04:23
Stage 2 of 9: Decrypting backup file ...
-- completed at 02/02/17 16:05:16
Stage 3 of 9: Unpacking backup file ...
ERROR: Unpacking backup file failed. Invalid backup file. Please retry restore with another backup.
% Backup file could not be unpacked

This is the volume output

Neville Price — Thu, 02 Feb 2017 16:13:22 GMT

This is the volume output from the 2.2.0 appliance

Disk Source	Available Space(KB)	Used Space(KB)	% Used
/dev/mapper/smosvg-rootvol	3440420	322460	9
/dev/sda2	88339	5691	6
/dev/mapper/smosvg-tmpvol	1828592	37780	2
/dev/mapper/smosvg-localdiskvol	9552568	111129148	92
/dev/mapper/smosvg-home	84608	5672	6
/dev/mapper/smosvg-varvol	2151000	1611880	43
/dev/mapper/smosvg-optvol	186002020	456793980	71
/dev/mapper/smosvg-recvol	84616	5664	6
/dev/mapper/smosvg-altrootvol	84616	5664	6
/dev/mapper/smosvg-storeddatavol	9238552	153700	2
/dev/mapper/smosvg-usrvol	5668596	893848	14
/dev/sda1	452444	17800	4
tmpfs	5497228	2642144	32