Mailing-List: contact user-help@oodt.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@oodt.apache.org
Received-SPF: pass (nike.apache.org: domain of lmzxq.tom@gmail.com designates
 209.85.213.43 as permitted sender)
MIME-Version: 1.0
Date: Fri, 16 Mar 2012 15:57:00 +0200
Message-ID: 
 <CA+j8pPbGm6PHdRZKAe6DwHbqchFmPPtDqPb2ZVRhkb359rSBpw@mail.gmail.com>
Subject: Data transfer questions
From: Thomas Bennett <lmzxq.tom@gmail.com>
To: OODT <user@oodt.apache.org>
Content-Type: multipart/alternative; boundary=047d7b2e4cdc2926e704bb5c9532

--047d7b2e4cdc2926e704bb5c9532
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I have a few questions about data transfer and thought I would roll it into
one email:

1) Local and remote data transfer with the same file manager

   - I see that when configuring a cas-crawler, one specifies the data
   transfer factory by using --clientTransferer
   - However in etc/filemgr.properties the data transfer factory
   is specified with  filemgr.datatransfer.factory.

Does this mean that I if I specify a local transfer factory I cannot  use a
crawler with a remote data transferer?

I'm wanting to cater for a situation where files could be ingested locally
as well as remotely using a single file manager. Is this possible?

2) Copy and ingested product on a back up archive

For backup (and access purposes), I'm wanting to ingest the product into an
off site archive (at our main engineering office) with it's
own separate catalogue.
What is the recommended way of doing this?

They way I currently do this is by replicate the files using rsync (but I'm
then left with finding a way to update the catalogue). I was wondering if
there was a neater (more OODT) solution?

I was thinking, perhaps using the functionality described in OODT-84
(Ability for File Manager to stage an ingested Product to one of its
clients) and then have a second crawler on the backup archive which will
then update it's own catalogue.

I just thought I would ask the question in case anyone has tried something
similar.

Cheers,
Tom

--047d7b2e4cdc2926e704bb5c9532
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,<div><br></div><div>I have a few questions about data transfer and thoug=
ht I would roll it into one email:</div><div><br></div><div>1) Local and re=
mote data transfer with the same file manager</div><div><ul><li>I see that =
when configuring a cas-crawler, one specifies the data transfer factory by =
using --clientTransferer=A0<br>


</li><li>However in etc/filemgr.properties the data transfer factory is=A0s=
pecified=A0with =A0filemgr.datatransfer.factory.</li></ul>Does this mean th=
at I if I specify a local transfer factory I cannot =A0use a crawler with a=
 remote data transferer?<br>

</div><div><br></div>
<div>I&#39;m wanting to cater for a situation where files could be ingested=
 locally as well as remotely using a single file manager. Is this possible?=
</div><div><br></div><div>2) Copy and ingested product on a back up archive=
<br>
</div><div><br></div><div>For backup (and access purposes), I&#39;m wanting=
 to ingest the product into an off site archive (at our main engineering of=
fice) with it&#39;s own=A0separate=A0catalogue.</div>
<div>What is the recommended way of doing this?=A0</div><div><br></div><div=
>They way I currently do this is by replicate the files using rsync (but I&=
#39;m then left with finding a way to update the catalogue). I was wonderin=
g if there was a neater (more OODT) solution?</div>

<div><br></div><div>I was thinking, perhaps using the functionality describ=
ed in=A0OODT-84 (Ability for File Manager to stage an ingested Product to o=
ne of its clients) and then have a second crawler on the backup archive whi=
ch will then update it&#39;s own catalogue.<br>

</div><div><br></div><div>I just thought I would ask the question in case a=
nyone has tried something similar.</div><div><br></div><div>Cheers,<br>Tom<=
/div><div><br></div><div><br></div>

--047d7b2e4cdc2926e704bb5c9532--