Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*synthetic\s+fullbackup\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*synthetic\s+fullbackup\s*$/: 10 ]

Total 10 documents matching your query.

1. synthetic fullbackup (score: 1): Author: Schwarz Werner <Werner.Schwarz AT BEDAG DOT CH>; Date: Wed, 18 Dec 2002 14:07:36 +0100; We are looking for a solution for the following problem: During a restore of a whole TSM-client we found that the needed ACTIVE backup_versions were heavy scattered around our virtual tape-volumes. T; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-12/msg00710.html (11,812 bytes)
2. Re: synthetic fullbackup (score: 1): Author: Halvorsen Geirr Gulbrand <gehal AT WMDATA DOT COM>; Date: Wed, 18 Dec 2002 14:44:20 +0100; Hi Werner, we might need some clearifying of your setup. What is your server version? Are you backing up to tape, or disk? Generally I can say this: If you are running TSM v. 5.x you have the possibi; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-12/msg00712.html (13,254 bytes)
3. Re: synthetic fullbackup (score: 1): Author: Richard Sims <rbs AT BU DOT EDU>; Date: Wed, 18 Dec 2002 09:21:11 -0500; Werner - As Geirr said, Backupsets are the optimal solution but, as all solutions, will require extra processing time. Another approach is to exploit the often-unexploited MIGDelay value, on the pri; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-12/msg00721.html (11,934 bytes)
4. Re: synthetic fullbackup (score: 1): Author: David E Ehresman <deehre01 AT LOUISVILLE DOT EDU>; Date: Wed, 18 Dec 2002 09:58:06 -0500; In TSM v5, I've replaced my backupsets with MOVE NODE DATA as my preferred way of consolidating a node's backup data onto a minimum number of tapes. David; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-12/msg00731.html (11,181 bytes)
5. Re: synthetic fullbackup (score: 1): Author: Halvorsen Geirr Gulbrand <gehal AT WMDATA DOT COM>; Date: Thu, 19 Dec 2002 09:44:00 +0100; Hi Werner, I'm sorry about a minor error on my side. I said (believed) that move nodedata had parameters to move only active files, but the possibilities for reducing the data to be moved are limited; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-12/msg00791.html (13,311 bytes)
6. synthetic fullbackup (score: 1): Author: Ron Lochhead <RLochhead AT CSE-INSURANCE DOT COM>; Date: Fri, 20 Dec 2002 10:16:28 -0800; Hi Halvorsen: I am trying to implement this same move nodedata idea, but am coming up with problem. My environment is Win2k server running TSM server 5.1.5.2 and same on clients. My goal is consolida; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-12/msg00888.html (14,559 bytes)
7. Re: synthetic fullbackup (score: 1): Author: Mark Stapleton <stapleto AT BERBEE DOT COM>; Date: Fri, 20 Dec 2002 13:14:59 -0600; If you'll read the results of help move nodedata you'll notice that the FROMstgpool (the source) must be a sequential-access pool. -- Mark Stapleton (stapleton AT berbee DOT com); /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-12/msg00892.html (12,070 bytes)
8. Re: synthetic fullbackup (score: 1): Author: "Ford, Phillip" <phillip.ford AT SPCORP DOT COM>; Date: Fri, 20 Dec 2002 13:47:46 -0500; Make the tape pool "collocation enabled" and do a migration on the disk pool (update stg diskpool hi=0 low=0). Also helps to have migration process set to 1 for the disk pool. I don't know if this is; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-12/msg00895.html (15,458 bytes)
9. Re: synthetic fullbackup (score: 1): Author: Zlatko Krastev <acit AT ATTGLOBAL DOT NET>; Date: Tue, 24 Dec 2002 23:17:45 +0200; It is not necessary and will not help (you may even lose performance if several drives are available). TSM server is smart enough and even without collocation setting each process will migrate data; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-12/msg00959.html (12,137 bytes)
10. Re: synthetic fullbackup (score: 1): Author: Halvorsen Geirr Gulbrand <gehal AT WMDATA DOT COM>; Date: Fri, 27 Dec 2002 10:34:08 +0100; Hi Again, you would have to create a collocated storagepool (on tape), and migrate data from the diskpool to the new tapepool. You would have to setup next storagepoole for your diskpool, to point to; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-12/msg00987.html (15,184 bytes)

Current List: 1 - 10
Page: [1]