Hi Markus, by my opinion you must not make extra schedules for simple clients, because files are migrated form diskpool "per node" at the time. If several migrations occured during backups, I thing your diskpool is too small. It will be better to increase its size to achieve one migration process after all backups and client's data will be grouped by nodes during migration at the same tape without using of collocation. Whole backup window will be usable for all clients and save your backup time and better use all resources (net, server power ...etc.). Moreover, dividing schedules per clients you cannot ensure that only one client will access the server at the time, if backup will be longer then his startup window.
Hope this helps. Wiht best regards Tom -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Markus Veit Sent: Monday, September 30, 2002 11:08 AM To: [EMAIL PROTECTED] Subject: Discussion: 1 server sched for all vs 1 for each node Hi TSMer's if you have several client nodes, would it be better to have one client schedule were all nodes are in or would it be better to have one schedule per node spread over time. My guess is that it woluld be better to spread the start of the backups to keep the TSM server available for one node at a time, so that the data going to the diskpool is more or less together and will be migrated onto tape more compact, saving a lot of tape mounts in case of a restore. Although this is definetly not collocation but the data on tape should be more continious. Any feedback would be appreciated. Mit freundlichen Gr|_en / Best Regards Markus Veit =
