-
Notifications
You must be signed in to change notification settings - Fork 246
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
Comments
An interesting discussion and code examples are provided in the original feature request at SF#2939418 |
SF tracker has been disabled for this project. Are those code snippets and discussions preserved? |
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 :-/ |
I was just curious, where my script went ;-) In fact I was looking for the current version in order to update our Another thing: there is still the old webpage like Viele Grüsse Holger Reif |
@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 ! |
@hreif Has everything being restored (patches/updates)? Otherwise, we can close this issue, right? |
In the
With this the original question has been fulfilled - we're good to finally close this issue. |
Hmm. Maybe we should name the parameter something like On 2 October 2013 08:27, gdha notifications@github.com wrote:
|
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.
The text was updated successfully, but these errors were encountered: