| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 302.1 | | DECWET::RANDALL | | Fri Jan 10 1997 17:02 | 11 |
| 302.2 | | CRONIC::LEMONS | And we thank you for your support. | Fri Jan 10 1997 19:42 | 9 |
| 302.3 | Happening again | CRONIC::LEMONS | And we thank you for your support. | Sun Jan 12 1997 07:27 | 112 |
| 302.4 | | CRONIC::LEMONS | And we thank you for your support. | Tue Jan 14 1997 08:32 | 117 |
| 302.5 | Parallelism issue to consider | SNAX::WITHEROW | | Tue Jan 14 1997 09:03 | 125 |
| 302.6 | Use a few big groups, not many small ones | DECWET::RWALKER | Roger Walker - Media Changers | Tue Jan 14 1997 10:30 | 34 |
| 302.7 | | CRONIC::LEMONS | And we thank you for your support. | Tue Jan 14 1997 11:59 | 15 |
| 302.8 | Looking good! | CRONIC::LEMONS | And we thank you for your support. | Tue Jan 14 1997 22:13 | 7 |
| 302.9 | One last item to ask... | SNAX::WITHEROW | | Wed Jan 15 1997 10:38 | 9 |
| 302.10 | | DECWET::RWALKER | Roger Walker - Media Changers | Wed Jan 15 1997 11:34 | 6 |
| 302.19 | | SANITY::LEMONS | And we thank you for your support. | Fri May 02 1997 15:18 | 12 |
| I now have the case where a script on a database server is going to
execute a 'save' command to inititate a backup. This save command will
use whatever group I want. I believe that, if this save commands
executes at the same time as my nightly backups, but uses a different
group, I will have the problem described in this note thread.
However, if I use the same group in both the script-originated save
command and the NetWorker Server-originated save commands, will
everything work well?
Thanks!
tl
|
| 302.20 | | DECWET::RWALKER | Roger Walker - Media Changers | Fri May 02 1997 22:42 | 9 |
| If you really meen group, then only one instance of a group will
run at a time. It creates a lock file the prevents the same group
from being started again. This is using scheduled starts, starting
a group from the GUI, or running the savegrp command.
You can't mix start methods without risking overlapping groups and
the possible problems that concurent groups may cause.
Pools are a whole different story.
|
| 302.21 | | SANITY::LEMONS | And we thank you for your support. | Mon May 05 1997 10:52 | 16 |
| Hi Roger
Thanks for the response.
>>
If you really meen group, then only one instance of a group will
run at a time. It creates a lock file the prevents the same group
from being started again. This is using scheduled starts, starting
a group from the GUI, or running the savegrp command.
<<
Gotcha. But what if I run a save (not savegrp) command? Will this
'join' an already running savegroup, or be blocked by the lock file
until the already running savegroup of the same name completes?
Thanks!
tl
|
| 302.22 | | DECWET::RWALKER | Roger Walker - Media Changers | Mon May 05 1997 11:22 | 6 |
| Manual saves run independantly and have no relationship to
any group. It doesn't matter what names are used.
The manual save will act just like another single stream
save group was started and the server will just stall any
sessions greater the 'max para'.
|
| 302.23 | | DECWET::RANDALL | | Mon May 05 1997 12:37 | 7 |
| You can run as many ad-hoc saves at one time as want. They won't
"join" any savegroups though, they'll just be another save running.
However, you could run into problems with this if you have a savegroup
running that expects to use up the parrallelism. See notes on
overlapping savegroups for explanation.
-- Rich Randall
|
| 302.24 | | SANITY::LEMONS | And we thank you for your support. | Mon May 05 1997 18:21 | 6 |
| This, indeed, would be a problem for us. I'll make sure that the
script-scheduled saves do not run at the same time as our NetWorker
Server-scheduled saves.
Thanks very much for this clarification!
tl
|