Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+TSM\s+for\s+VE\s+7\.1\.2\.0\s+data\s+vs\s+meta\s+question\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+TSM\s+for\s+VE\s+7\.1\.2\.0\s+data\s+vs\s+meta\s+question\s*$/: 3 ]

Total 3 documents matching your query.

1. [ADSM-L] TSM for VE 7.1.2.0 data vs meta question (score: 1): Author: "Schaub, Steve" <Steve_Schaub AT BCBST DOT COM>; Date: Fri, 18 Sep 2015 13:50:06 +0000; 7.1.2.0 Recently, our meta diskpool filled up, and an admin who didn't know any better saw that it didn't have a downstream tapepool (vtl) so he went ahead and added one, to which the meta started fl; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2015-09/msg00056.html (11,490 bytes)
2. Re: [ADSM-L] TSM for VE 7.1.2.0 data vs meta question (score: 1): Author: Michael Prix <mp AT RS6000.DARKTECH DOT ORG>; Date: Fri, 18 Sep 2015 15:58:20 +0200; Steve, if it's really a pool on a VTL, then there are no major implications for you. The reason the metadata should stay on disk is that the metadata is needed for CBT to detect the blocks needed to; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2015-09/msg00057.html (12,389 bytes)
3. Re: [ADSM-L] TSM for VE 7.1.2.0 data vs meta question (score: 1): Author: Stefan Folkerts <stefan.folkerts AT GMAIL DOT COM>; Date: Sat, 26 Sep 2015 13:21:09 +0200; You might want to look into making some full VM backups for the most important vn's to get the relevant metadata to disk asap. I see to many people putting metadata on tape and using incremental fore; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2015-09/msg00072.html (13,347 bytes)

Current List: 1 - 3
Page: [1]