-
Notifications
You must be signed in to change notification settings - Fork 258
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing backup in recovery iso for IBM PowerVM LPAR #697
Comments
The 81_prepare_multiple_iso.sh script is missing for Linux-ppc64 so ISO_MAX_SIZE should not be used? |
@TobiasKarnat If you add |
@TobiasKarnat Is your question answered? Do you still need further assistance? |
Sorry about the late response. We do actually always want to add the backup to the ISO image. I opened this issue to inform the developer that there is a bug and for others which might need the same workaround. Thank you. |
I don't see it as a bug, it is a missing feature nobody added (yet). You could add it yourself like I explained before, or sponsor the code ( |
Some time ago, I was thinking of kind of "feature" for ebiso, that would just take finished tar archive and simply add it to bootable iso. But after a while I put it "on hold" as it didn't look to have much of a value for me... |
Re-open this issue when we found a sponsor to implement this missing feature |
@schabrolles Quick question: are you dealing with this item in your tests as well? |
@gdha No ... As you said, ISO image is just a bootable image that allow you to start a recovery, recreate the disk FS structure and start the restoration which is stored from on a separate DISK, Network Serveur (NFS/FTP/SSHFS etc..) or backup server like TSM etc ... If this function is available for x86, I should have a look ... |
@gdha regarding your above If you add $TMP_DIR/isofs to the array ISO_FILES then you will always add the backups to the ISO image even when you do not want to do this. I think only with things like BACKUP_URL=iso://backup But I could be wrong - this is only how the code looks to me |
@jsmeix I made a simple "prototype" which seems to work. |
@schabrolles Reason: ReaR's internal backup methods are not meant Accordingly there are some limitations what ReaR is meant to recover the basic (operating) system |
With #1383 merged @schabrolles |
Environment: LPAR on IBM Power7 with PowerVM
OS: SUSE Linux Enterprise Server 11 SP3
Rear 1.17.2
local.conf
'rear -v mkbackup' runs successfully and creates the bootable iso and the backup.tar.gz file.
But the backup.tar.gz file is not included in the final iso image.
I had to modify the following script to include it, but haven't tried a restore yet.
The text was updated successfully, but these errors were encountered: