Networker

Re: [Networker] Looking at RepliStor

2003-04-17 11:40:42
Subject: Re: [Networker] Looking at RepliStor
From: Mark T Wragge <storage AT TTT DOT IE>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Thu, 17 Apr 2003 16:39:15 +0100
I know that RepliStor can use a many to one configuration.    IF I would
like to have two sites replicating to one RepliStor server, what kind of
permissions can I set so that Administrators of one set of data cannot see
the second set of data.

Server One replicates to the Replistor server
Server Two replicates to the same RepliStor server
Server One and Two are in a different domain - Is this possible?

This is so that there is not the cost of hardware for two replistor servers.

----- Original Message -----
From: "Peacock, Tom" <TPeacock AT DETMA DOT ORG>
To: <NETWORKER AT LISTMAIL.TEMPLE DOT EDU>
Sent: Thursday, April 17, 2003 12:20 PM
Subject: Re: [Networker] Looking at RepliStor


> Hi Cyndi,
>
> I am at a similar site and I am also looking at this possibility for a 28
> remote sites (3 hubs site) environment.  The remote sites have very little
> changes and network bandwidth requirements with Replistor can be throttled
> not to exceed somemany KB/s or a % of the line.  It makes sense from a
cost
> and admin standpoint.  At $1850 or so, this is comparable to a slim DLT or
> LTO drive alone.  With a pure NetWorker solution, you would additionally
> need the NetWorker "license", media, training, time and more time (oh
> yeah..don't forget logs).  You could consider Legato Management Console to
> manage all of the sites, but then that is $4000 for the management server
> and $2000 for each managed/monitored NetWorker server on top of all of the
> other NetWorker "needs".  Gets pricy and shows that RepliStor is a valid
> avenue to explore.
>
> RepliStor is very simple to setup and configure.  You could get a 30 day
> eval code and setup a test environement and have your network team monitor
> the "traffic" for proof of concept.
>
> Don't forget that with your existing NetWorker environment you need to
> always keep the "best practices" model in mind when designing NetWorker
> backup and _recovery_ solutions.  Review what is critical at these sites
and
> play out various scenarios on replication and access to replicated data in
> the event of a link down, drive failure or failed system.  I know you plan
> on backing up the replicated data once it is at the "hub" site.  Consider
> the entire data protection (and restoration) environment as your team
plans.
>
> -Tom
>
>
>
>
> -----Original Message-----
> From: Cyndi Smith [mailto:Cyndi.Smith AT ASPENTECH DOT COM]
> Sent: Tuesday, April 15, 2003 6:30 PM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: [Networker] Looking at RepliStor
>
>
> Is anyone using Replistor? We are thinking about it for a backup solution
> for remote offices. We have several offices that do not have an "IS"
> presence. In a few of those, we currently run Networker and have a local
> (non-technical) person change tapes in a changer at the direction of one
of
> our Networker admins.  We would like to simplify this so that we do not
need
> local assistance.  To this end, we were thinking about Replistor (or it's
> competitor, DoubleTake from NSI). We would replicate several machines --
> perhaps from several different remote sites -- over the WAN to a server at
> one of our "hub" offices. This server would then be backed up at that hub
> office. Our network people are understandably apprehensive.
> Can someone who is more familiar with this sort of set up please tell me
of
> their experiences?
>
> Thanks for any input.
>
> Cyndi
> ---
> Cyndi Smith
> Senior System Support Engineer - Unix
> Aspen Technology, Houston, TX
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

<Prev in Thread] Current Thread [Next in Thread>