►
From YouTube: NUG webinar recording, Dec 2020
Description
Nick from NERSC's storage team tells us about NERSC's archival system HPSS, including the challenges of smoothly moving over 150PB of data from Oakland to our new data center at Berkeley
A
So
quick
plan
of
the
day
we've
been
doing
this
for
a
few
months
now,
so
hopefully,
people
are
starting
to
get
familiar
with
the
new
format
that
we're
using
we're
aiming
to
be
quite
interactive
here.
So
please,
yeah
speak
up,
participate
type
things
in
probably
the
nurse
user
slack
webinars
channel
is
a
easier
and
and
more
you
know
long
lasting
place
to
put
a
chat
but
yeah,
also
in
the
in
the
zoom
chat.
A
We
have
a
few
announcements
and
also
open
the
floor
for
announcements
that
any
of
our
users
here
would
like
to
make
there's
a
good
opportunity
for,
like
your
course
for
participation,
and
so
on
a
particular
thing.
We're
going
to
talk
about
a
little
bit.
There
is
preparation
for
the
ay
allocation
year
transition,
which
is
coming
up
in
january.
A
Then
our
topic
of
the
day
is
hpss
nusk's
archival
system
and
nick
from
nurse
storage
team
is
here
and
he's
going
to
tell
us
a
little
bit
about
hpss,
and
you
know
some
of
its.
I
guess
tips
and
topics
and
history
and
we'll
talk
a
little
bit
also
about
using
it
and
then
we'll
finish
up
with
sort
of
last
month's
numbers
and
and
what's
coming
up.
A
These
are
also
kind
of
your
opportunities
to
you
know,
make
yourself
and
your
your
work
known
for
you
know
potential
nomination,
for
you
know,
science
highlights
or
high
impact
scientific
achievement
awards
or
for
innovative
use
of
high
performance
computing
awards.
So
there's
a
awards
that
nurse
awards
to
users
each
year.
A
A
See
I
have
some
yeah
quite
encouraging
news.
It's
also
kind
of
a
a
bit
of
a
thank
you
to
users
who
have
answered
so
far.
We
have.
Our
annual
nurse
survey
is
currently
open
and
you
know
surveys.
There
are
a
lot
of
them
nowadays
and
you
know
it's
quite
a
challenge
getting
a
good
response
rate,
but
it's
quite
important
to
us
to
get.
A
You
know
our
users
feedback
on
what's
going
on,
and
I
was
looking
at
the
numbers
that
we've
had
the
responses
that
we've
had
coming
in
just
the
other
day
and
yeah.
So
far,
we've
had
a
really
good
participation
rate.
So
that's
really
encouraging
and
you
know
thank
you
users
who
have
participated
if
you
haven't
there's
still
time.
You
know
please
send
in
your
feedback.
There
is
a
link
in
your
emails.
A
A
Just
achievements
that
might
have
yeah
might
have
come
in
a
slightly
more
painful
way,
and
the
idea
here
is
to
recognize
that
things
don't
necessarily
come
easily,
and
you
know
there's
there's
plenty
that
we
can
learn
from
challenges,
and
you
know
it's
helpful
to
each
other
and
other
users
to
to
know
about
the
things
that
we
tripped
up
on
and
yeah,
even
if
we
didn't
solve
them.
Yes,
challenges
and
ideas
that
you
know
others
might
be
able
to
help
us
through.
A
A
So
I-
and
I
suspect
others
at
nurse-
have
been
learning
in
the
last
couple
of
weeks
about
the
degree
of
complexity
of
all
the
different
systems
that
make
up
nersk.
So
we've
been
planning
for
this
power
maintenance.
That's
currently
going
on,
and
it's
it's
quite
a
complex
sequence
of
operations,
all
the
different
systems
and
services
that
use
just
some
element
of
infrastructure.
That's
in
the
nurse
building.
Since
for
this
maintenance,
we
need
to
actually
turn
off
all
power
to
the
building.
It's
it's
kind
of
a
step
beyond.
A
Even
what
we've
had
to
do
in
the
past
for
public
safety
power
shut
offs
in
that
in
the
psps
you
know
we
can
usually
keep
something
going
on
on
a
backup
generator,
but
because
this
time
it's
the
actual
power
infrastructure,
that's
being
upgraded.
Everything
needs
to
be.
You
know,
carefully,
shut
down
and
brought.
A
A
A
So
we
have
oh.
As
always,
please
check
the
weekly
email.
There
are
new
news.
There
I
mentioned
before
the
nurse
user
survey
is
currently
open.
Thanks
to
those
who
have
responded
and
if
not
please
do
and,
as
I
think
everybody
is
quite
aware,
we
currently
have
a
power
maintenance,
which
means
that
all
systems
and
services
are
available
this
week
and
that
even
includes
actually
the
help
system.
So
one
of
the
services
that's
unavailable
is
our
authentication
service,
which
prevents
logging
in
to
help.nurse.gov.
A
A
B
A
A
A
So
tuesday
january
19
is
when
the
current
allocation
year
will
finish,
we'll
have
our
monthly
scheduled
maintenance
on
the
wednesday
and
when
we
return
from
maintenance
we'll
be
in
the
new
allocation
year
helen,
I
know
you've
done
a
lot
of
the
preparation
and
planning
for
this.
Would
you
like
to
talk
a
little
about
the
allocation?
Your
plans.
B
B
So
for
premium
it's
normally
not
not
used
for
your
regular
computing
and
nurse
it's
for
an
emergency
not
for
like
when
you
try
to
use
up
all
your
alkene.
It's
for
emergency
publication
deadline
experiment,
so
it
should
be
used
infrequently,
and
so
we
have
decided
that
we
need
to
have
a
sort
of
threshold
for
the
charging
factor.
So
once
the
over
20
of
the
allocation
high
water
mark,
the
premium
will
be
charged
double
of
its
premium.
So
normally
premium
is
two
times
of
your
regular
qos
charge
charges.
B
So
when
it's
over
twenty
percent
of
the
allocation
it'll
be
charges
four
times
of
a
regular
qos
charge,
and
this
this
is
temporary
and
we
may
decide
to
change.
Depending
on
how
this
is
usage.
I
will
be
observing
this.
A
new
policy,
and
also
a
a
new
set
up,
is
that
we
are
not
going
to
have
premium
being
enabled
by
default
for
all
the
users,
so
pis
have
to
decide
which
users
in
their
project
can
use
premium
qos.
B
B
So
another
recommendation
is
that
the
jobs
in
the
queue
right
now
is
premium
and
if
you
want
to
avoid
a
surprising
two-time
charge
because
those
jobs
may
start
in
ay
21
instead
of
now,
and
that
you
may
think
this
job
or
not,
you
know
as
the
premium
priority
anymore.
You
can
change
it
now
to
to
regular
or
make
sure
your
users
are
running
having
these
jobs
in
the
queue
they
do
have
access
to
premium,
but
you
still
want
them
those
jobs
to
be
run
in
the
premium.
Qos
next
slide,
please.
B
So,
on
the
day
when
ay
21
starts,
which
is
wednesday
january
20th,
we'll
have
iris
down.
First
then
we'll
have
the
new
allocation
year
data
switch
over
then
corey
does
start
at
the
same
time.
But
then,
during
this,
when
iris
transition
is
over,
corey
is
going
to
correspond.
Slurm
scheduler
will
have
the
access
to
the
new
iris
data.
Then
we
then
will
do
some
processing.
B
The
list
of
the
jobs
lists
on
this
page
are
the
jobs
in
the
queue
that
we
will
delete
when,
after
curry
comes
back,
those
jobs
will
be
gone.
So
so
those
are
the
jobs
that
if
the
the
project
is
not
continued
for
this
year's
allocation,
all
these
jobs
will
be
deleted
or
if
a
jobs,
the
allocation
is
still
is
continued.
But
pi
didn't
select
this
user
to
continue
in
the
next
like
allocation
year.
B
Those
jobs
will
also
have
the
invalid
slum
association
to
be
allowed
to
run
jobs,
so
those
jobs
will
be
deleted,
so
pis
make
sure
to
to
can
select
your
users
that
you
you
desire
to
continue
and
premium
qrs
as
well
since
they're,
not
defaulting
anymore.
If
a
user
is
not
enabled
for
a
premium,
those
jobs
will
be
deleted.
B
I
want
to
just
call
out
normally
we
at
allocation
year
during
the
startup
electric
new
allocation
year,
we
change
our
software
default.
Intel
compilers
create
pe
software.
This
year
we
decide
to
keep
those
the
same
as
is,
and
we
do
have
a
potential
to
upgrade
os
in
the
middle
of
the
year
and
we
may
change
a
default
at
that
time.
A
B
B
C
D
A
A
E
F
E
E
E
So
this
is
about
our
move
out
of
the
oakland
scientific
facility
that
happened
in
between
mostly
between
2018
and
2019,
and
early
2020.
I'll,
introduce
the
team
really
quickly.
So
again,
I'm
nick
balthazar,
I'm
an
hpss
admin
in
the
storage
systems
group
I
deal
mostly
with
day-to-day
operations
and
before
shelter
and
place
happened.
E
Melinda
jacobson
is
an
hpss
developer.
She
spends
half
of
her
time,
actually
writing
hpss
code
and
contributing
it
back
to
the
hpss
collaboration,
which
is
a
collaboration
between
ibm
and
five
doe
labs,
including
ersk,
and
she
spends
the
other
half
of
her
time.
Helping
nurse
with
software
process
improvements
and
our
own
internal
hpss
code
and
modifications
owen
james,
who
I
mentioned,
is
a
member
of
the
otg
operations
technology
group.
He
is
our
man
in
the
field.
E
He
deals
with
a
lot
of
the
on-site
day-to-day
operations
to
keep
hpss
running
and
he's
also
responsible
for
knowing
a
lot
of
fun
facts
about
hpss.
Like
you
know
how
many
mp3s
could
you
hold
in
three
tape,
libraries
and
stuff
like
that
which,
unfortunately,
I
don't
know,
but
he's
always
fun-
to
talk
to
you
about
interesting,
hpss
and
storage,
trivia
christie,
callback
rose,
is
our
group
lead
and
she
also
has
a.
She
also
is
on
the
hpss
technical
committee
driving
future
hpss
features,
and
finally,
carrillozynski
works.
E
So
usually,
when
I
give
a
presentation
about
nurse,
I
have
a
few
introductory
slides
about
what
sort
of
work
we
do
and
how
many
users
we
have
and
their
distribution
across
the
world
in
the
country.
But
since
everybody
here
is
a
nurse
user,
I
I'm
going
to
go
ahead
and
skip
that,
but
I
did
want
to
mention
a
bit
about
nurse
compute
infrastructure,
in
particular
the
storage
tiers.
E
So,
as
you
may
know,
storage
is
arranged
in
tiers
that
form
a
hierarchy.
The
top
of
the
hierarchy
is
typically
a
very
fast
storage
that
is
load
capacity
and
the
bottom
tier
of
storage
is
a
slower
but
higher
capacity.
And,
of
course
everybody
wants
the
top
tier
to
have
more
capacity.
That's
faster
and
everybody
wants
the
lower
tier
to
have
more
speed
and
be
easier
to
use,
and
these
tiers
are
arranged
mostly
due
to
cost
the
higher
tiers
of
storage
just
cost
more.
E
The
second
tier
storage
is
corey's
scratch
file
system,
which
is
luster
on
spinning
disk.
I
believe
it's
next
young
hardware
that
is
30
petabytes
and
can
move
data
at
700
gigs.
A
second,
the
third
tier
of
storage,
is
also
a
file
system
on
spinning
disk.
It's
a
gps
file
system
called
our
community
file
system,
it's
running
on
ibm
ess
hardware
and
can
move
data
at
a
100
gigs,
a
second
and
finally,
the
last
but
not
least,
the
bottom
tier
of
storage
with
the
least
convenience.
E
E
E
E
All
of
our
data
transfers
so
far
are
via
client,
interface,
htar,
pftp
and
globus.
We
don't
have
any
direct
file
system
interface
yet,
but
that
is
a
topic
that
we're
looking
at
and
actively
exploring
so,
for
instance,
ghi
gpfs,
hpss
integration.
There's
a
project
right
now,
that's
looking
at
that
and
we're
looking
at
other
interfaces
as
as
well
such
as
the
hpss
fuse
interface,
which
is
kind
of
like
nfs.
E
Historically,
we've
grown
the
archive
at
1.4
times
per
year,
so
this
is
a
growth
chart.
When
I
joined
the
group
in
2007,
we
had,
I
think,
a
petabyte,
and
now
we
have
230
petabytes,
so
it
just
keeps
growing
archive
is
an
orange
and
this
is
a
stack
chart.
The
region
doesn't
actually
have
230
petabytes,
it's
actually
only
30
petabytes
represented
in
green,
so
the
topic
of
the
day
is
moving
out
of
osf,
which
we
did
between
2018
and
actually
early
2020.
E
E
So
we
had
a
multiple
year
evaluation
of
where
to
put
the
tape.
I
should
also
mention
which
isn't
in
the
slide
that
oracle
our
principal
tape
and
drive
vendor
at
the
time
decided
to
stop
supporting
oracle
enterprise
media,
which
is
high
performance,
high
speed
tape,
media
that
we
use
for
the
archive.
So
we
were
also
stuck
for
a
decision
as
to
what
technology
to
move
the
archive
to,
because
our
principal
vendor
of
drives
and
media
decided
to
end
of
life,
their
enterprise
product.
E
Relative
humidity
is
where
we
want
tape
to
be,
and
we
don't
want
any
rapid
fluctuations.
It's
supposed
to
be
a
very
consistent
environment,
so
the
the
berkeley
data
center
just
could
get
too
hot
or
too
humid
or
fluctuate
too
rapidly
to
be
safe
for
tape.
Another
issue
that
we've
been
encountering
since
2017
is
airborne.
Particulate
tape
does
not
like
dirty
air.
E
E
E
So
a
quick
look
at
the
process
of
of
the
move
there
were.
You
know
this
is
obviously
kind
of
a
condensed
view
of
it.
There
were
an
awful
lot
of
steps
and
it
took
a
long
time,
but
one
of
the
issues
is
that
the
ibm
media
is
incompatible
with
the
oracle
media,
so
we
couldn't
just
load
it
up
all
in
a
truck
and
transfer
it
from
oakland
to
to
berkeley
what
we
did
was
run
some.
E
E
E
E
This
is
a
visualization
of
the
data
copy
operation
that
our
team
lead.
Wayne
did.
I
know
the
numbers
are
probably
way
too
small
to
read
on
zoom,
but
basically
you
can
see
that
on
some
of
our
peak
days,
we
sustained
about
half
a
petabyte
a
day
for
the
large
files
which
stream
better
than
small
files
and
and
that
went
on
for
quite
a
while.
We
were
also
dealing
with
regular
user
ingest,
which
is
between
150
and
300
terabytes
a
day.
E
The
smaller
system
was
a
lot
easier
to
move
and
we
just
did
a
forklift
move.
We
packed
up
all
the
cartridges
into
you
know
hundreds
of
boxes
moved
them
all
by
truck
and
shut
the
system
down
and
moved
it
in
one
single
14-hour
downtime.
So
again,
owen
and
his
team
were
critical
in
packing
up
the
media,
and
you
know
ejecting
tapes
packing
them
up
early
in
the
morning
and
late
at
night
and
arranging
for
all
the
media
movement.
E
So
wayne
led
that
effort,
and
it
was
it
took
a
good
couple
of
months
to
get
all
of
the
old
stuff
out
of
there
and
I
believe
the
oakland
scientific
facility
is
now
like
a
hole
in
the
ground.
I
don't
even
I
think
it's
been
demolished,
but
glenn
can
probably
speak
to
that,
since
I
think
he
has
a
view
of
it
from
his
his
window.
D
Any
oh
yeah,
sorry,
this
is
koichi
from
vienna.
Thank
you
for
very
interesting
presentation.
I
really
love
to
know
those
behind
the
scenes
efforts
going
on
nice
and
it's
yeah.
It's
really
a
lot
of
work.
I
can
see
that
just
a
quick
question
because
you
mentioned
the
current
system
has
this,
you
know,
is
equipped
with
this
kind
of
air
conditioning,
so
that
keeps
the
tape
in
a
good
condition,
but
I'm
just
wondering
what's
going
on
right
now,
because
there's
no
power
at
the
facility
this
week.
E
E
So
as
long
as
there
are
no
reads
or
writes
being
done
to
the
tape
system,
it
should
be
fairly
safe
if
the
temperature
fluctuates
as
long
as
it
stays
within
that
I
showed
you
that
chart
the
cyclo
psychometric
chart
with
the
the
blue
area
as
long
as
the
overall
temperature
remains
there.
As
long
as
we're
not
doing
I
o
to
the
tape
system,
it
should
be
okay
and
we
will
probably
have
the
libraries
powered
up
for
a
few
hours
before
we
start
the
system
to
let
the
temperature
inside
the
libraries
become
optimal.
A
So
you
so
you
there
was
a
couple
of
things
in
your
slides
there
and
that
you
talked
about
that
that
jumped
out
at
me.
So
one
was,
you
talked
about
the
size
of
the
data
on
hpss
increasing
by
1.4
times
per
year,
which
sort
of
just
sounds
like
a
number.
But
then
I
noticed
in
that
inside
hpc
article
that
was
published
february
2019
and
it
said
120
petabytes
of
data
and
so
a
little
less
than
two
years
later,
we're
up
at
230
petabytes
nearly
twice
as
much.
E
It's
a
lot
of
data,
it's
an
average
over
many
years,
so
we
do
have
fluctuations
actually
in
spite
of
what
the
numbers,
in
spite
of
what
the
numbers
say
in
inside
hpc,
I
believe
wayne
has
observed
that
our
ingest
rate
is
down
a
little
bit
over
the
last
couple
of
years,
so
maybe
the
last
few
years
have
been
1.3
or
1.2
but
yeah.
We
we
handle
a
lot
of
data.
A
E
So
right
now
we're
running
15
terabyte
cartridges
and
I
believe
at
crt
sitting
in
pallets.
Right
now
are
the
next
generation
of
tape
drives,
which
will
run
20,
terabyte
cartridges
and
wayne,
and
I
will
go
ahead
and
implement
the
new
drive
technology
and
then
copy
all
of
the
15
terabyte
media
onto
the
20
terabyte
media,
and
that's
just
a
constant
thing
that
happens
with
hpss
every
couple
of
years.
We
change
the
the
underlying
media
technology.
A
E
A
E
E
A
E
Yeah,
not
not
many
sites
have
a
point.
Two
point:
four
hundred
gigabit
link
that
that
is
quite
fast.
We
have
100
gigabit
moving
to
the
hpss
movers
and
they're
they're
dual
connected,
so
a
single
I
o
mover
can
push
maybe
200
gigs
a
second
or
two
gigabits.
A
second
that's
you
know
divided
by
eight
for
gigabytes,
but
yeah.
We
spinning
up
multiple
tape
drives.
Each
tape.
Drive
can
do
maybe
300
or
350
megs
a
second.
A
D
D
Maybe
I
can
go
ahead,
go
ahead!
Yes,
yes,
yeah,
which
questions
to
first.
So
this
from
your
presentation.
I
you
mentioned
this.
The
old
system
from
oracle
in
the
new
system
from
ibm
were
not
compatible
or
consistent,
and
then
I
just
didn't
get
how
you
guys
solve
the
problem.
Did
you
guys
have
to
copy
from
oracle
to
one
something
and
then
copy
again,
or
did
you
guys
do
anything
more
sophisticated.
E
That's
essentially
the
gist
of
it
thanks.
That's
another
really
good
question,
so
that's
right!
The
oracle,
media
and
tape
drive
technology
is
not
compatible
with
ibm.
They
won't
read
each
other's
media
or
cartridges.
So
what
we
did
was
what
you
might
do
in
any
file
system.
If
you
were,
you
know,
maybe
copying
from
your
mac
desktop
to
a
windows
machine
or
something
we
just
kind
of
copied.
The
files
over
the
network.
E
You
know
read
them
out
of
the
oracle
infrastructure
over
the
network,
to
the
ibm
infrastructure
and
just
rewrote
them
onto
the
the
ibm
tapes-
and
you
know
the
metadata
is
all
handled
by
hpss,
so
the
files,
the
bits
all
of
that
stuff
end
up
intact
in
in
the
metadata
database
and
yeah.
It
was
basically
just
a
big
big
copy
or
an
rsync.
If
you
you
want
to
think
of
it.
That
way,.
D
Thank
you
and
thanks
for
the
question,
I
have
two
more
questions
actually
sure
you
can
ask.
The
second
question
is
about
it's
kind
of
related
follow-up,
but
security
of
this
hps
system.
I
mean
security
both
in
terms
of
any
potential
data
loss,
or
I
don't
know
some
confusion
between
metadata
and
actual
data,
and
then
also
I
don't
know
if
any
outside
hackers
attack
hpss
system.
Just
to
I
don't
know
for
for
my
field,
my
climate
science
data,
nothing
is
really
sensitive,
but
maybe
some
more
different.
D
You
know
space
physics
or
some
other
national
security
have
maybe
sensitive
data,
and
then
some
hackers
may
just
want
to
give
trouble
to
other
people,
so
I
they
might
do
try
to
get
access
to
storage
so
yeah,
just
just
accidental,
you
know
erase
or
loss
of
data
security
and
a
more
intentional
attack
kind
of
security
is
any.
Do
you
have
to
do
something
against
those
issues
to
maintain
hbss.
E
Well,
those
those
are
also
very
good
questions,
so
one
is
sort
of
a
data
integrity.
How
do
we
protect
the
metadata
and
the
other
is
more
about
a
cyber
security?
How
do
we
protect
hpss
against
cyber
security
attacks
right?
Okay?
So,
as
far
as
the
metadata
goes,
we
back
it
up
every
day
and
we
use
you
know
we.
We
use
disk
arrays
that
are
our.
You
know
raid
six
plus
two,
so
we
can
lose
disks
and
we
have
metadata
backups.
E
But
to
your
point,
if
you
know
if
an
asteroid
were
com
were
to
come
and
like
wipe
out
crt
off
the
face
of
the
map,
that
would
be
it
for
hbss.
We
don't
have
off-site
copies
of
the
data.
We
do
have
off-site
copies
of
the
metadata.
But
of
course,
if
your
data
is
gone,
the
metadata
doesn't
do
much
good.
E
So
we
do
what
we
can
to
to
make
sure
the
metadata
is
protected
and
backed
up
and
not
corrupt
and
all
of
that
stuff,
and
we
do
have
off-site
copies
of
that,
but
not
off-site
copies
of
the
data.
As
far
as
the
cyber
security
question
we're
prone
to
cred,
you
know
stolen
credentials,
just
like
any
other
system.
So
if
somebody
say
it's
difficult
to
steal
your
credential
these
days
because
we're
using
one-time
passwords
so
we're
a
little
bit
more
protected
at
nurse
than
we
used
to
be.
E
D
E
E
They
wouldn't
be
able
to
read
other
users
files
if
they
still
say
you
know
my
identity
or
your
your
identity,
but
I
think
the
identity
theft
risk
is
a
lot
lower
these
days
with
with
one-time
passwords,
and
of
course
you
know,
if
we
do
find
out
about
a
breach,
we
can
re,
we
can
revoke
somebody's
hpss
token,
but
yeah.
If
somebody
were
to
go
in
there
and
erase
all
your
data,
we
couldn't
get
it
back.
So
we
do
advise
you.
You
know
if
there's
something
that
is
super
critical
for
multiple
reasons.
E
E
E
E
A
E
E
A
A
G
I
think
the
main
thing
that
I
would
emphasize
to
users
is
to
remember
what
nick
pointed
out
is
that
at
its
heart,
it's
a
tape
system,
there's
a
disk
archive,
that's
at
the
top.
That
makes
it
respond
like
a
file
system,
but
underneath
its
tapes,
and
so
that
makes
things
doing
things
like
putting
a
hundred
thousand
small
files
into
it.
That
would
normally
be
kind
of
okay
on
a
file
system.
A
A
Maybe
we'll
keep
that
one
on
the
on
the
slack
channel
and
just
to
finish
up
a
quick
run
over
last
month's
numbers,
so
corey's
availability
was
yeah,
quite
high,
98.7
scheduled
a
little
lower
when
you
include
the
maintenance
scheduled
maintenance
in
there.
Normally,
I
have
a
you
know,
a
little
graphic
here,
kind
of
showing
a
timeline
of
when
and
for
how
long,
the
various
yeah,
outages
and
so
on
were,
but
my
script
for
doing
that
is
on
cory,
which
is
currently
unavailable.
A
A
A
A
D
D
Actually,
if
you
go
back
to
the
slide
for
the
hpss,
I
just
wanted
to
know
reminded
more
detail
about
how
to
use
globus
to
hpss.
I
got
a
question
from
yeah
here,
for
you
know
globus
warning
or
file
systems
not
append.
I
think
I
asked
this
question
before
here,
but
I
also
asked
by
one
of
the
members
in
my
division
or
project.
E
E
F
D
A
F
E
That's
part
of
the
reason
for
wide
area
network
transfers.
Yes,
globus
is
only
single
stream,
so
the
only
way
to
the
only
way
to
move
data
effectively
from
a
external
file
system
to
hpss
is
to
fire
up
multiple
jobs.
You
know
to
move
data
concurrently,
because
on
the
hpss
side
it's
only
a
serial
protocol,
it's
an
enhancement
is
coming,
but
it's
going
to
be
a
while.
E
E
So
we
prefer
people
to
tie
up
their
files
on
the
remote
side
and
then
send
us.
You
know
large
tar
files
as
opposed
to
just
sort
of
do
an
rsync
like
thing
that
globus
allows
you
to
do
where
it
just
you
know,
drag
and
drop
a
whole
directory
full
of
files,
so
that
that's
another
issue
we've
seen
with
globus
is
sort
of
deluging
the
the
arc.