Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+collocation\s+increases\s+tape\s+mounts\s+while\s+backup\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+collocation\s+increases\s+tape\s+mounts\s+while\s+backup\s*$/: 10 ]

Total 10 documents matching your query.

1. [ADSM-L] collocation increases tape mounts while backup (score: 1): Author: chart2 <tsm-forum AT BACKUPCENTRAL DOT COM>; Date: Wed, 16 Dec 2009 16:08:26 -0500; Depending on how you set up your collocation (File Systems, Server or Server Group). If you chose collocation by file system then you would mount a tape for each file sys, if you set by server then a; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-12/msg00171.html (11,408 bytes)
2. [ADSM-L] collocation increases tape mounts while backup (score: 1): Author: EVILUTION <tsm-forum AT BACKUPCENTRAL DOT COM>; Date: Thu, 17 Dec 2009 15:44:07 -0500; We are using an IBM3584 and don't use any kind of collocation. We have found the migration process from diskpool to tape collocates data by node and therefore already does a decent job of grouping no; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-12/msg00207.html (11,718 bytes)
3. Re: [ADSM-L] collocation increases tape mounts while backup (score: 1): Author: Steven Langdale <Steven.Langdale AT CAT DOT COM>; Date: Thu, 17 Dec 2009 22:31:53 +0000; In that case you must be using collocation (albeit by accident). You may want to look at group collocation as it sounds like your tapes are probably underutilised. Unless that is you have manly fewer; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-12/msg00209.html (12,534 bytes)
4. Re: [ADSM-L] collocation increases tape mounts while backup (score: 1): Author: Richard Sims <rbs AT BU DOT EDU>; Date: Thu, 17 Dec 2009 17:46:17 -0500; In that case you must be using collocation (albeit by accident). Not really... Remember that, within Migpr, migration operates serially by node, and thus you get a certain amount of same-node data c; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-12/msg00210.html (11,690 bytes)
5. Re: [ADSM-L] collocation increases tape mounts while backup (score: 1): Author: Steven Langdale <Steven.Langdale AT CAT DOT COM>; Date: Fri, 18 Dec 2009 12:12:26 +0000; Indeed you are correct. Though isn't that collocation going to go out of the window on the 2nd days migrations? The daily chunks of data will be together, but all node data would be on the same tape; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-12/msg00213.html (12,436 bytes)
6. [ADSM-L] collocation increases tape mounts while backup (score: 1): Author: gardenia28 <tsm-forum AT BACKUPCENTRAL DOT COM>; Date: Tue, 24 Nov 2009 00:37:26 -0500; Hi, I find by applying collocation concept, the no.of tape mount increases while taking backup... Could anyone justify it or explain me why it is so? +-- +--; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-11/msg00263.html (11,369 bytes)
7. Re: [ADSM-L] collocation increases tape mounts while backup (score: 1): Author: Mehdi Salehi <iranian.aix.support AT GMAIL DOT COM>; Date: Tue, 24 Nov 2009 10:51:32 +0330; The benefit of collocation is in restore time, because tape mounts will be reduces for restoring each client. If there are not enough tape drives defined in TSM server, more tape mount during backup; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-11/msg00266.html (11,244 bytes)
8. Re: [ADSM-L] collocation increases tape mounts while backup (score: 1): Author: "Huebschman, George J." <GJHuebschman AT LMUS.LEGGMASON DOT COM>; Date: Tue, 24 Nov 2009 11:24:58 -0500; Gardenia? Collocation directs TSM to store the data for a particular group of nodes, node, or filespace on as few volumes as possible. As Medhi Salehi noted, it keeps tape mounts to a minimum for res; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-11/msg00271.html (14,296 bytes)
9. Re: [ADSM-L] collocation increases tape mounts while backup (score: 1): Author: David E Ehresman <deehre01 AT LOUISVILLE DOT EDU>; Date: Tue, 24 Nov 2009 11:34:34 -0500; copy pool as a disaster recovery pool would be ideal to collocate, but if you send off tapes every day you end up with a fragmented set of tapes for each collocation unit anyway. To clean that up wo; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-11/msg00272.html (12,251 bytes)
10. Re: [ADSM-L] collocation increases tape mounts while backup (score: 1): Author: "Huebschman, George J." <GJHuebschman AT LMUS.LEGGMASON DOT COM>; Date: Tue, 24 Nov 2009 12:22:38 -0500; I understand how offsite pool reclamation works, but it is not going to reclaim the entire storage pool unless you set your threshold shockingly low. Otherwise, it is only going to skim off the few h; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-11/msg00273.html (14,655 bytes)

Current List: 1 - 10
Page: [1]