I'll admit it does all get a bit confusing and, sometimes, you have to
take a step back and say 'what am I trying to achieve here?'
Here's what I think you want to do
You have a bunch of data at a remote site that you want to backup and
keep a copy offsite.
You have a central networker server that backs up other stuff and you
want this data offsite too.
To backup the remote stuff you have a storage node.
The question is where to put the index files for the remote node and
where they should be kept offsite?
Is that the case?
Now, if we think of how the data would be restored we can get a clearer
picture of where we want the data and the index files.
The data for the storage node will get restored from the tapes at the
storage node
The index files used in the restore will be used by the Networker server
(so they need be at the same site as the Networker server), they don't
need to be at the remote site at all.
Ah, I hear you ask, what about a disaster recovery situation? What
indeed. Well, there's no problem, if it is data lost at the remote
storage node, retrieve the tapes and proceed with the restore as normal
(index files will still be on the Networker at the central site).
If it is the central site that has data loss, then having the index
files offsite at the remote end isn't going to help that much.
All I'm saying is that the index files really belong with the Networker
server and should be treated as part of the central site's data (unless
you replicate your index files, but that's a different strategy
altogether).
Hope it helps
Bob
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On Behalf Of Robert Maiello
Sent: 13 May 2004 15:55
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Dedicated Storage Node
I'm a bit confused with the explanations. I have a pool that exists on
the main server and storage node. The indexes are backed up to a
tape/pool on the main server. The data is all on the storage node.
When we clone the storage node data we send the indexes back out to the
storage node so they go offsite with the data they represent (we don't
want indexes offsite at location A and the data offsite at location B).
The only drawback we seem to have:
The backup of the indexes on the main server does take up a tape drive
for its duration. It would seem I could free up a tape drive if the
indexes are backed up to the storage node (sent back out). Are you
saying there is
a way to do this? I understand the indexes are on the main server
and
associated with the main server, and having a tape copy of them there is
a good thing. I just wanted to know if its possible.
Robert Maiello
Thomson Healthcare
On Thu, 13 May 2004 12:08:21 +0100, Wood, R A (Bob)
<WoodR AT CHEVRONTEXACO DOT COM> wrote:
>If you want the data at the storage node and the indexes at the nsrhost
>then just select the client instead of the group in the pool selection
>(the indexes belong to the networker server but you've selected
>everything in the group go to that pool).
>
>Bob
>
>-----Original Message-----
>From: Legato NetWorker discussion
>[mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
>On Behalf Of Davina Treiber
>Sent: 12 May 2004 22:12
>To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
>Subject: Re: [Networker] Dedicated Storage Node
>
>
>johan.gislen AT hik DOT se wrote:
>> I'm currently in the process of setting up a dedicated storage node
>> with a jukebox attached to it, and thought it would be a good idea to
>> create a dedicated volume pool for the media in that jukebox.
>>
>> In the settings for the volume pool (called "StorageNodePool"), I
>> selected the group "StorageNode" which contains only the client that
>> is the dedicated storage node. The client data gets written to the
>> locally attached jukebox, but when it gets to the client index it
>> wants a volume from the "StorageNodePool" at the main Networker
>> server.
>>
>> Is there any way that I can direct the storage node client's index to
>> the "Main" pool that I use for the rest of my backups?
>>
>> Platform: Windows 2000
>> Networker: 7.1.1
>
>This is expected behaviour. I'm not sure that creating this pool is a
>particular wise move. IMHO you should have a very good reason for
>creating a new pool, and I wouldn't usually class having a storage node
>as one of these reasons. Normally the best reason is to accommodate
>different retention policies, or perhaps because you have some specific
>offsite requirement.
>
>However I'm not telling you how to configure your system, so let's
>consider the question. You can configure a pool to receive your indices
>(and bootstraps if required) although I'm not sure whether it's going
>to be so easy to make that pool the same one as you are using on your
>server-as-a-storage-node. What you would do is as follows: for the
>index pool, configure the save sets fields with values of ^index: and
>^bootstrap$. You should recognise these as standard regular expressions
>that match the index and bootstrap save sets. Now - I'm not sure
>whether doing this to your main pool will create further complications,
>I'll leave that to you to consider.
>
>--
>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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
