With regards to functionality, both of schedmodes are equivalent. But there
are some arguments in different environments which prefers any of these
modes.
Schedmode pooling is better for example for clients, which are not up
allways at their backup the time. Server then didn't try to get them and
initialize backup, but client himself start action, if it is running - you
can avoid the server messages like "Session open failed due to connection
refusal" ... and other.
Pooling mode is also better for environment with hundreds of clients (like
yours I think), because lowers the server load. In prompting mode are all
scheduled actions in server regie otherwise to pooling mode. On the other
hand, one of disadvantages of pooling mode is time synchronization of server
and clients which you have to control to reach consolidated backup
environment
My opinion.
Hi Tom
Tomas Hrouda, AGCOM Smirice
Tivoli Certified Consultant
Storage Manager Specialist
[EMAIL PROTECTED]
+420 49 5941312, +420 604 296521
ICQ#77892561
-----Original Message-----
From: Glass, Peter [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 06, 2001 11:17 PM
To: [EMAIL PROTECTED]
Subject: schedmode: polling vs. prompting
Which client schedmode -- polling or prompting -- is the better practical
choice for a large TSM environment of 300+ clients?
We would welcome any thoughts or suggestions on the relative
merits/drawbacks of either mode.
Thanks in advance.
Peter Glass
Distributed Storage Management (DSM)
Wells Fargo Services Company
> * 612-667-0086 * 866-407-5362
> * [EMAIL PROTECTED]
>
---
Odchozi zprava neobsahuje viry.
Zkontrolovano antivirovym systemem AVG (http://www.grisoft.cz).
Verze: 6.0.276 / Virova baze: 145 - datum vydani: 3.9.2001
