Skip to content
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

Give more time for entering TSM restore options #24

Closed
dagwieers opened this issue Mar 28, 2012 · 8 comments
Closed

Give more time for entering TSM restore options #24

dagwieers opened this issue Mar 28, 2012 · 8 comments
Assignees
Labels
enhancement Adaptions and new features waiting for info
Milestone

Comments

@dagwieers
Copy link
Contributor

Reported by hreif as SF#2939418

In verify/TSM/default/40_verify_tsm.sh user has 30 secs to enter the number for the filespaces to recover. For more complex setups this is not enough, especially if not all filesystems are to be recovered (e.g. they are non-locallly)

Therefore I added a timed question whether he want to change something.
If he wants then user has all the time he needs to choose the right spaces.

In principle, verify/TSM/default/39_request_point_in_time_restore_parameters.sh has the same problem, but there 30 secs might be enough for entering a date there.

@dagwieers
Copy link
Contributor Author

An interesting discussion and code examples are provided in the original feature request at SF#2939418

@ghost ghost assigned schlomo Mar 28, 2012
@hreif
Copy link

hreif commented Jul 25, 2012

SF tracker has been disabled for this project. Are those code snippets and discussions preserved?

@dagwieers
Copy link
Contributor Author

Yes, we have a backup of all content. There does not seem to be an option to leave the SF tracker in read-only mode, so I decided to disable it to prevent people from reporting issues there. (Only a handful of issues from SF are open, so the impact was not that big)

Is there something specific you like ? I can try to copy&paste the original content, but it might not be that easy :-/

@hreif
Copy link

hreif commented Jul 25, 2012

I was just curious, where my script went ;-)

In fact I was looking for the current version in order to update our
private 1.7.22d version. I found that the 40_verify_tsm.sh patch was
missing and that both dr/GNU/Linux/10_describe_diskbyid_mappings.sh and
finalize/GNU/Linux/16_remove_diskbyid.sh (other Ticket) were not present.
So I raised my voice ;-)

Another thing: there is still the old webpage like
http://rear.sourceforge.net/documentation.php which doesn'T point to the
new location (okay, deep linking sometimes guides you wrong ;-)

Viele Grüsse

Holger Reif

@dagwieers
Copy link
Contributor Author

@hreif Let me know if I should bring anything back from SF though !

And yes, the old website should disappear (or redirect). The current implementation is problematic (to say the least). I will open another ticket for this. Thanks for reporting !

@gdha
Copy link
Member

gdha commented Mar 15, 2013

@hreif Has everything being restored (patches/updates)? Otherwise, we can close this issue, right?

@gdha
Copy link
Member

gdha commented Oct 2, 2013

In the conf/default.conf file we introduced (since rear-1.15) a new variable:

# some external backup software give you the opportunity to enter paths to exclude ...
# we tend to use a timer in seconds we wait before continuing (we do not want to break the automated restores)
WAIT_SECS=30

With this the original question has been fulfilled - we're good to finally close this issue.

@gdha gdha closed this as completed Oct 2, 2013
@schlomo
Copy link
Member

schlomo commented Oct 2, 2013

Hmm. Maybe we should name the parameter something like
"INTERACTIVE_PROMPT_TIMEOUT"? Much more explaining what it does...

On 2 October 2013 08:27, gdha notifications@github.com wrote:

In the conf/default.conf file we introduced (since rear-1.15) a new
variable:

some external backup software give you the opportunity to enter paths to exclude ...

we tend to use a timer in seconds we wait before continuing (we do not want to break the automated restores)

WAIT_SECS=30

With this the original question has been fulfilled - we're good to finally
close this issue.


Reply to this email directly or view it on GitHubhttps://github.com//issues/24#issuecomment-25515759
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Adaptions and new features waiting for info
Projects
None yet
Development

No branches or pull requests

4 participants