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

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Copy\s+Serialization\s+Dynamic\s+Impact\s*$/: 3 ]

Total 3 documents matching your query.

1. Copy Serialization Dynamic Impact (score: 1): Author: Scott Walters <scott_walters AT MACKTRUCKS DOT COM>; Date: Thu, 3 Oct 2002 14:17:11 -0400; Hey all, In setting up our TSM server, we've noticed that many clients have large sessions because they have been re-transmitting files that are changing. We had the Copy Serialization set to Shared; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-10/msg00151.html (11,439 bytes)
2. Re: Copy Serialization Dynamic Impact (score: 1): Author: Mark Stapleton <stapleto AT BERBEE DOT COM>; Date: Thu, 3 Oct 2002 22:56:17 -0500; Occasionally. You need to get good copies of your data. You can either 1) shut down the app that creates the files while you back them up, 2) use a TDP agent to get a good backup, 3) use an open file; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-10/msg00170.html (11,063 bytes)
3. Re: Copy Serialization Dynamic Impact (score: 1): Author: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>; Date: Fri, 4 Oct 2002 12:46:14 -0400; If the large files are SEQUENTIALLY written files, a fuzzy backup is usually OK. An example of this is the dsmsched.log file - it's always being written to during a backup. Same thing on some AIX cli; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-10/msg00207.html (12,782 bytes)

Current List: 1 - 3
Page: [1]