-
Notifications
You must be signed in to change notification settings - Fork 249
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
Feature Idea: Create portable rear recover solution OUTPUT=PORTABLE #3190
Comments
@schlomo My reason (as far as I understand it) is that |
Only an offhanded thought FYI
I wonder if this may overwrite things Therefore I am wondering if it is possible
If this is possible, then with OUTPUT=PORTABLE
What I mean is to get what belongs to The idea behind is that what "rear recover" needs Or in other words: |
Update: Started to work on this in In this test it failed to install the boot loaded because ReaR thinks it is running on Arch Linux (SysRescueCD) and not the restored OS. Looks promising, but I need to make the system read the Your thoughts are welcome.
|
Hard-code ReaR paths in rescue system and use relative links to non- standard ReaR directories in rescue system to allow running portable ReaR Fixes #3190
Hard-code ReaR paths in rescue system and use relative links to non- standard ReaR directories in rescue system to allow running portable ReaR Fixes #3190
Hard-code ReaR paths in rescue system and use relative links to non- standard ReaR directories in rescue system to allow running portable ReaR Fixes #3190
Implemented via a9594b0 |
DeaR @rear/contributors I'd like to collect your thoughts on the following proposal to create a portable rear recovery solution.
Problem
The problem to solve is to use
rear recover
based on another (non-ReaR) rescue system instead of the ReaR rescue system. The reasons are due to corporate requirements of a customer environment or due to software compatibility problems between the ReaR rescue system and proprietary backup software.Solution Approach
The idea is to create a new
OUTPUT=PORTABLE
method that will produce an "ReaR Portable Recovery" archive containing/etc/rear
/usr/share/rear
/usr/sbin/rear
/var/lib/rear
For recovery the user would to the following:
$HOSTNAME
etc.)/
rear recover
as usualI expect users to potentially run into trouble with the automated migration of hardware IDs for network, but for simple cases I expect this to "just work".
What do you think? What did I forget?
The text was updated successfully, but these errors were encountered: