Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Ang\:\s+Re\:\s+\[ADSM\-L\]\s+Ang\:\s+Re\:\s+\[ADSM\-L\]\s+Ang\:\s+Re\:\s+\[ADSM\-L\]\s+Ang\:\s+Re\:\s+\[ADSM\-L\]\s+vtl\s+versus\s+file\s+systems\s+for\s+pirmary\s+pool\s*$/: 3 ]

Total 3 documents matching your query.

1. [ADSM-L] Ang: Re: [ADSM-L] Ang: Re: [ADSM-L] Ang: Re: [ADSM-L] Ang: Re: [ADSM-L] vtl versus file systems for pirmary pool (score: 1)
Author: Daniel Sparrman <daniel.sparrman AT EXIST DOT SE>
Date: Tue, 4 Oct 2011 07:41:13 +0200
And if you have a logical error on your primary box, which is then replicated to your 2nd box? Or even worse, a hash conflict? I dont consider someone putting a bullet through both the boxes a high
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2011-10/msg00017.html (16,748 bytes)

2. Re: [ADSM-L] Ang: Re: [ADSM-L] Ang: Re: [ADSM-L] Ang: Re: [ADSM-L] Ang: Re: [ADSM-L] vtl versus file systems for pirmary pool (score: 1)
Author: Steven Langdale <steven.langdale AT GMAIL DOT COM>
Date: Tue, 4 Oct 2011 07:57:52 +0100
The "logical error" question has come up before. With no TSM managed copy pool you are perhaps at a slightly higher risk. An option is to still have a copy pool, but on the same DD. So little real di
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2011-10/msg00020.html (18,348 bytes)

3. Re: [ADSM-L] Ang: Re: [ADSM-L] Ang: Re: [ADSM-L] Ang: Re: [ADSM-L] Ang: Re: [ADSM-L] vtl versus file systems for pirmary pool (score: 1)
Author: Shawn Drew <shawn.drew AT AMERICAS.BNPPARIBAS DOT COM>
Date: Tue, 4 Oct 2011 14:07:18 -0400
The other side of this is that with 3rd party deduplicated replication, my offsite copy is rarely more than one hour behind the source copy. Before I moved to this, we would schedule our backup-stg p
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2011-10/msg00035.html (20,119 bytes)


This search system is powered by Namazu