Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+slow\s+restore\s+performance\s+on\s+tsmve\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+slow\s+restore\s+performance\s+on\s+tsmve\s*$/: 3 ]

Total 3 documents matching your query.

1. [ADSM-L] slow restore performance on tsmve (score: 1): Author: TSM <tsm AT PROFI-AG DOT DE>; Date: Sat, 26 Apr 2014 08:23:04 +0200; Hello, our restore performance (restore vm) is very poor. We see this on custom installations and also in some test areas. Environment: TSMVE 7.1 / 7.1.0.1, tsm ba client 7.1.0 and 7.1.0.2 TSM-Server; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2014-04/msg00202.html (10,937 bytes)
2. Re: [ADSM-L] slow restore performance on tsmve (score: 1): Author: Marcel Anthonijsz <marcel AT ANTHONIJSZ DOT NET>; Date: Sat, 26 Apr 2014 11:37:35 +0200; Stefan, Make sure your VMCTL data is on a diskpool. TSM needs the metadata for backups and restores. Next, I have found after extensive testing (and a PMR with IBM) that the transport method NBD is m; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2014-04/msg00203.html (12,954 bytes)
3. Re: [ADSM-L] slow restore performance on tsmve (score: 1): Author: Shawn DREW <shawn.drew AT US.BNPPARIBAS DOT COM>; Date: Tue, 29 Apr 2014 22:01:55 +0000; If you are using the mode=ifincr parameter, it might be the same problem we had a while ago. We started using ifincr as soon as it was added, but found our restores were horribly slow if we did not p; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2014-04/msg00214.html (12,647 bytes)

Current List: 1 - 3
Page: [1]