so how to calculate the randomization percentage and client backup scatter time ....
is there any best practise ...
Main Topics
Browse All TopicsHi
what is randomising in tsm .how to enable it , in which situation it should be used ...in which schedule mode can it be used
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
1) Generally, leave at default if possible.
2) If you have many clients in single schedules and/or experience communication errors because of network/server congestion, raise the randomization value.
3) If you have many retries because of connection establishment failures and a very short startup window, either lower the randomization percentage (if (2) above is not true), or (if (2) above is true) enlarge the startup window.
There is no exact calculation method. If your backup window (the time your business allows for backups to run) is not too short, leave randomization at default and raise the startup window to let's say three hours or so and watch what it brings. In almost any case you should not have any problems with that setting.
wmp
Business Accounts
Answer for Membership
by: woolmilkporcPosted on 2009-08-27 at 05:52:52ID: 25197398
Hi,
Schedule Randomization is used in TSM to scatter start times of client backups triggered by a schedule across its startup window.
It is useful to avoid communication errors which could occur when all clients belonging to a schedule would contact the server at the same time. So use it in situations where lots of client backups are started by a single schedule, and/or when your network or TSM server tends to get overloaded, to balance that load.
The randomization is measured in percent of the schedule startup window, and is a system wide setting.
The startup window of a schedule is set using the DURATION (1,2,3,4,....) and DURUNITS (days, hours, minutes...) when defining or updating a schedule.
So, if you have a startup window of 1 hour (DURATION 1 , DURUNIT HOURS , the default), and a randomization of 25% (the default), client backup start times will be scattered across the first 15 minutes from STARTTIME on.
Randomization occurs independently of whether the SCHEDSTYLE is classic or enhanced. The client's SCHEDMODE should be POLLING (the default).
Randomization is enabled by default with a value of 25%. Disable Randomization by setting it to zero using SET RANDOMIZE 0
wmp