From: "Andrew Raibeck" <[EMAIL PROTECTED]>
> What is the storage pool's COLLOCATE value set to? Collocate = Group From: "Thorneycroft, Doug" <[EMAIL PROTECTED]> >Are there also backups running during this period, If the diskpool doesn't >have enough space, or a client has files that exceed the diskpools >maxsize then some of your backups could be using the extra tapes. Backups are running during the whole day, also during migration. And we migrate (automaticly) during backup. There is enough space, hi=50%, lo=10%, size=2400GB, we don't get above the 80% during the top backups. There is no maxsize threshold defined. From: "Volker Maibaum" <[EMAIL PROTECTED]> > I don't think that TSM uses only 1 tape per collocgroup when you have > set maxpr=3. What if only data of one collocgroup is on the diskpool? > TSM would waste resources. > If you turn collocation=none for the tape pool than TSM also uses three > tapes at a time. The doc's said that when a migrate starts, it selects a node or group to migrate (with biggest FS or biggest node in case of colloc.groups) and does the migration in 1 stream, so it "must" always use 1 tape at the time. (see page 259 in 5.3 Admin Guide) ---------------------------------------------------------------------------- --- -----Original Message----- From: Maurice van 't Loo Sent: Tuesday, September 06, 2005 11:38 PM To: ADSM-L@VM.MARIST.EDU Subject: Multiple fillings per node with collocate is group Hi *SM'ers After migration from diskpool to tapepool, we see every day that several nodes or collocation groups have 2 or sometimes even 3 filling tapes. As far as i know, migration is always 1 stream per node/collocgroup, so there must be only 1 filling max. Right? Is this a bug, a feature or misunderstanding?? Tapepool: 3584 libr. with 5 drives Migration: hi=50 lo=10 maxpr=3 Server 5.3.1.2 @ aix Regards, Maurice van 't Loo
