-
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add the latest issues to the ReaR User Guide
- Loading branch information
Showing
54 changed files
with
11,288 additions
and
0 deletions.
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,190 @@ | ||
| [\#2637 Issue](https://github.com/rear/rear/issues/2637) `closed`: Don't deprecate OBDR because it still works and is in use | ||
| ============================================================================================================================ | ||
|
|
||
| **Labels**: `enhancement`, `cleanup`, `no-issue-activity` | ||
|
|
||
| #### <img src="https://avatars.githubusercontent.com/u/1788608?u=925fc54e2ce01551392622446ece427f51e2f0ce&v=4" width="50">[jsmeix](https://github.com/jsmeix) opened issue at [2021-06-22 13:41](https://github.com/rear/rear/issues/2637): | ||
|
|
||
| Usage of OUTPUT=OBDR should be deprecated in next ReaR version (2.7) | ||
| so that the OBDR code could be removed in the version after the next | ||
| version (2.8) | ||
|
|
||
| See | ||
| [https://github.com/rear/rear/pull/2625](https://github.com/rear/rear/pull/2625) | ||
| (excerpts): | ||
|
|
||
| UEFI seems to have broken OBDR support: | ||
| https://github.com/rear/rear/commit/41efc97eb7141c30455df45a871b98cd08e09fa7 | ||
|
|
||
| OBDR probably got broken on ppc64le: | ||
| https://github.com/rear/rear/commit/4ef0f30156f0afea4a02d12f40c2c9d18cbe5e43 | ||
| PR https://github.com/rear/rear/pull/1383 | ||
|
|
||
| in particular | ||
| [https://github.com/rear/rear/pull/2625\#issuecomment-859335712](https://github.com/rear/rear/pull/2625#issuecomment-859335712) | ||
| and some subsequent comments about OBDR therein. | ||
|
|
||
| #### <img src="https://avatars.githubusercontent.com/u/1788608?u=925fc54e2ce01551392622446ece427f51e2f0ce&v=4" width="50">[jsmeix](https://github.com/jsmeix) commented at [2021-06-22 13:51](https://github.com/rear/rear/issues/2637#issuecomment-866002450): | ||
|
|
||
| I wonder what the best way is how to deprecate something in ReaR. | ||
|
|
||
| My personal offhanded idea is to add a new script like | ||
| usr/share/rear/init/default/850\_check\_deperecations.sh | ||
| that errors out when something deprecated is used | ||
| e.g. something like | ||
|
|
||
| test "$OUTPUT" = "OBDR" && Error "OBDR support is deprecated" | ||
|
|
||
| perhaps a bit more user friendly - I only liked to suggest the basic | ||
| idea. | ||
|
|
||
| #### <img src="https://avatars.githubusercontent.com/u/1788608?u=925fc54e2ce01551392622446ece427f51e2f0ce&v=4" width="50">[jsmeix](https://github.com/jsmeix) commented at [2021-06-25 13:35](https://github.com/rear/rear/issues/2637#issuecomment-868504817): | ||
|
|
||
| An offhanded proposal how to make it easier for the user | ||
| to still use deprecated functionality: | ||
|
|
||
| Add to default.conf | ||
|
|
||
| # For now you may set it to 'false' to still use deprecated OUTPUT="OBDR" | ||
| # but OBDR support will be removed in a subsequent ReaR version | ||
| # see https://github.com/rear/rear/issues/2637 | ||
| OBDR_DEPRECATED="OBDR support is deprecated" | ||
|
|
||
| and in a new script | ||
| usr/share/rear/init/default/850\_check\_deperecations.sh | ||
|
|
||
| if ! is_false "$OBDR_DEPRECATED" ; then | ||
| test "$OUTPUT" = "OBDR" && Error "OUTPUT=$OUTPUT - $OBDR_DEPRECATED" | ||
| fi | ||
|
|
||
| #### <img src="https://avatars.githubusercontent.com/in/15368?v=4" width="50">[github-actions](https://github.com/apps/github-actions) commented at [2021-08-25 02:07](https://github.com/rear/rear/issues/2637#issuecomment-905111804): | ||
|
|
||
| Stale issue message | ||
|
|
||
| #### <img src="https://avatars.githubusercontent.com/u/26300485?u=9105d243bc9f7ade463a3e52e8dd13fa67837158&v=4" width="50">[pcahyna](https://github.com/pcahyna) commented at [2023-03-13 14:35](https://github.com/rear/rear/issues/2637#issuecomment-1466260652): | ||
|
|
||
| @maslo64 can you please test OBDR support? | ||
|
|
||
| #### <img src="https://avatars.githubusercontent.com/u/8884065?v=4" width="50">[maslo64](https://github.com/maslo64) commented at [2023-03-20 06:26](https://github.com/rear/rear/issues/2637#issuecomment-1475690995): | ||
|
|
||
| @pcahyna tests were performed with 2.7.1 RPM and in order to restore, | ||
| here are changes which were done to rear. | ||
|
|
||
| Here we need to update config file with `""` and `()` because of tar | ||
| behavior ,mentioned also in | ||
| [https://github.com/rear/rear/issues/2911](https://github.com/rear/rear/issues/2911) | ||
| [https://github.com/rear/rear/blob/7ce864210fc7a7c95a131ea8c933f543b6e3b9cb/usr/share/rear/verify/OBDR/NETFS/default/540\_set\_backup\_compression.sh](https://github.com/rear/rear/blob/7ce864210fc7a7c95a131ea8c933f543b6e3b9cb/usr/share/rear/verify/OBDR/NETFS/default/540_set_backup_compression.sh) | ||
|
|
||
| BACKUP_PROG_COMPRESS_OPTIONS=() | ||
| BACKUP_PROG_COMPRESS_SUFFIX="" | ||
|
|
||
| Here we are missing 'mt' program in order to perform restore , f.x. seek | ||
| with fsf command | ||
|
|
||
| [https://github.com/rear/rear/blob/7ce864210fc7a7c95a131ea8c933f543b6e3b9cb/usr/share/rear/conf/default.conf\#L1283](https://github.com/rear/rear/blob/7ce864210fc7a7c95a131ea8c933f543b6e3b9cb/usr/share/rear/conf/default.conf#L1283) | ||
|
|
||
| what was also needed for restore was to execute script | ||
|
|
||
| bash /usr/share/rear/skel/OBDR/etc/scripts/system-setup.d/43-init-cciss.sh | ||
|
|
||
| and afterwards update `TAPE_DEVICE=/dev/nstX` in config file. | ||
|
|
||
| Thanks | ||
|
|
||
| #### <img src="https://avatars.githubusercontent.com/u/1788608?u=925fc54e2ce01551392622446ece427f51e2f0ce&v=4" width="50">[jsmeix](https://github.com/jsmeix) commented at [2023-03-22 13:52](https://github.com/rear/rear/issues/2637#issuecomment-1479606919): | ||
|
|
||
| Via | ||
| [https://github.com/rear/rear/commit/d600bd776027150628225188c394420e4c6724cb](https://github.com/rear/rear/commit/d600bd776027150628225188c394420e4c6724cb) | ||
| I added 'mt' command to REQUIRED\_PROGS\_OBDR in default.conf according | ||
| to | ||
| [https://github.com/rear/rear/issues/2637\#issuecomment-1475690995](https://github.com/rear/rear/issues/2637#issuecomment-1475690995) | ||
|
|
||
| #### <img src="https://avatars.githubusercontent.com/u/1788608?u=925fc54e2ce01551392622446ece427f51e2f0ce&v=4" width="50">[jsmeix](https://github.com/jsmeix) commented at [2023-03-22 13:58](https://github.com/rear/rear/issues/2637#issuecomment-1479615705): | ||
|
|
||
| @maslo64 | ||
| thank you for your comment. | ||
|
|
||
| As long as current ReaR works with OBDR and | ||
| as long as there are users who use current ReaR with OBDR, | ||
| we will not deprecate OBDR. | ||
|
|
||
| In general: | ||
| Contributions for special use case support in ReaR | ||
| are much appreciated because we at ReaR upstream | ||
| usually cannot test those special use cases | ||
| so we totally depend on contributions from people | ||
| who use and know about those special use cases. | ||
|
|
||
| #### <img src="https://avatars.githubusercontent.com/u/1788608?u=925fc54e2ce01551392622446ece427f51e2f0ce&v=4" width="50">[jsmeix](https://github.com/jsmeix) commented at [2023-03-22 14:06](https://github.com/rear/rear/issues/2637#issuecomment-1479629056): | ||
|
|
||
| Currently I do not understand the third part in | ||
| [https://github.com/rear/rear/issues/2637\#issuecomment-1475690995](https://github.com/rear/rear/issues/2637#issuecomment-1475690995) | ||
|
|
||
| what was also needed for restore was to execute script | ||
|
|
||
| bash /usr/share/rear/skel/OBDR/etc/scripts/system-setup.d/43-init-cciss.sh | ||
|
|
||
| and afterwards update TAPE_DEVICE=/dev/nstX in config file. | ||
|
|
||
| but I never used a tape device with Linux | ||
| so I may not see things that are obvious | ||
| for users who actually use a tape device. | ||
|
|
||
| What confuses me: | ||
|
|
||
| I would assume etc/scripts/system-setup.d/43-init-cciss.sh | ||
| gets automatically run during ReaR recovery system startup? | ||
|
|
||
| I see TAPE\_DEVICE is used a lot in various scripts | ||
| but there is no TAPE\_DEVICE in usr/share/rear/conf/default.conf | ||
| so TAPE\_DEVICE is no user config variable? | ||
|
|
||
| #### <img src="https://avatars.githubusercontent.com/u/8884065?v=4" width="50">[maslo64](https://github.com/maslo64) commented at [2023-03-28 17:03](https://github.com/rear/rear/issues/2637#issuecomment-1487294178): | ||
|
|
||
| `I would assume etc/scripts/system-setup.d/43-init-cciss.sh gets automatically run during ReaR recovery system startup?` | ||
| I did expect that would be the case, but I *think* in my case | ||
| /var/lib/rear/output/rear-${HOSTNAME}.iso, was created using | ||
| 'OUTPUT=ISO', then it changed to 'OUTPUT=OBDR' in config file, so script | ||
| never made it to /etc/scripts/system-setup.d/ so it couldn't be executed | ||
| during startup. | ||
| And reason why it was this was setup this way is that with 'OUTPUT=OBDR' | ||
| the ISO file was never successfully created. | ||
| So we have had 'static' booting ISO always written to tape and data with | ||
| tar was updated regularly. | ||
|
|
||
| I did test it now and it looks better during boot | ||
|
|
||
| Running 43-init-cciss.sh... | ||
| Disable OBDR mode for device /dev/sr0 | ||
| Rescan single device using 1 0 1 0 | ||
| Wait for devices to settle | ||
| Running 45-serial-console.sh... | ||
|
|
||
| ` so TAPE_DEVICE is no user config variable?` after some more testing , | ||
| this seems to be required for successful restore. | ||
| If only OUTPUT\_URL=/dev/stX is specified, restore failed in my case. | ||
|
|
||
| As `TAPE_DEVICE` in recovery environment in OBDR case might not be same | ||
| device file, as new device /dev/stX will be generated when changing | ||
| device from OBDR mode. (considering there could be any number of tape | ||
| drives/changers in recovery environment ) so TAPE\_DEVICE has to be set | ||
| either manually or using `43-init-cciss.sh` somehow. | ||
|
|
||
| #### <img src="https://avatars.githubusercontent.com/in/15368?v=4" width="50">[github-actions](https://github.com/apps/github-actions) commented at [2023-05-28 02:32](https://github.com/rear/rear/issues/2637#issuecomment-1565812540): | ||
|
|
||
| Stale issue message | ||
|
|
||
| #### <img src="https://avatars.githubusercontent.com/u/8884065?v=4" width="50">[maslo64](https://github.com/maslo64) commented at [2023-07-04 19:56](https://github.com/rear/rear/issues/2637#issuecomment-1620667477): | ||
|
|
||
| @jsmeix well ,customer decided that he no longer want to do disaster | ||
| recovery , thus my use case for OBDR is no longer valid. I'm trying to | ||
| get some LTO with OBDR, but I'm skeptical that I get a device. | ||
|
|
||
| #### <img src="https://avatars.githubusercontent.com/in/15368?v=4" width="50">[github-actions](https://github.com/apps/github-actions) commented at [2023-09-03 02:03](https://github.com/rear/rear/issues/2637#issuecomment-1703986548): | ||
|
|
||
| Stale issue message | ||
|
|
||
| ------------------------------------------------------------------------ | ||
|
|
||
| \[Export of Github issue for | ||
| [rear/rear](https://github.com/rear/rear).\] |
Oops, something went wrong.