Thierry,
when you say "and schedule nsrstage from each SN, not from the server." I'm
not sure what you're saying.
We have a NetWorker Server and a StorageNode with a bunch of disk on the
storage node configured for adv_file type disk.
We use "staging policies" defined on the NetWorker server for each adv_file
device - once a device gets over 95% full then the system starts staging the
oldest saveset to tape and continues doing that until it gets back down to
under 80% full.
On the same storage node we have 2 tape-drives dedicated via the SAN of the
tape-library (the NetWorker server has the other 5 drives of the library
dedicated). Then we also have a special tape pool created for the target
clones and that tape pool is restricted to only be written to via the
tape-drives on the storage node.
And this seems to work ok. And we don't busy up the NetWorker server or LAN
while the migration is going on - and the migration typically runs at least
some during backups too.
thanks - John
-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]On Behalf Of
thierry.faidherbe AT HP DOT COM
Sent: Friday, April 08, 2005 8:15 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Problem with staging to storage node
>Make sure that the storage nodes are listed in the storage nodes field
>on the networker server. Then you can restrict the pool that you are
>staging to to devices on the storage nodes.
Not only : You must have all SN is server clone storage node affinity list,
having SN name listed in each SN's Clone storage node affinity.
and schedule nsrstage from each SN, not from the server.
I think it should work.
HTH,
Thierry
> Thanks Lee,
>
> Legato have had this call for a few days now :)
>
> Kevin
>
> -----Original Message-----
> From: Lee Hanel [mailto:lhanel AT rackspace DOT com]
> Sent: 08 April 2005 15:25
> To: Allan, Kevin; Legato NetWorker discussion
> Subject: Re: [Networker] Problem with staging to storage node
>
> Make sure that the storage nodes are listed in the storage nodes field
> on the networker server. Then you can restrict the pool that you are
> staging to to devices on the storage nodes.
>
>
> Lee
>
>
> On Fri, 2005-04-08 at 06:28 -0700, Allan, Kevin wrote:
>> I am currently in the process of setting up our first adv_file type
> devices
>> and staging policies but have hit a problem,
>>
>>
>>
>> We have one networker server and two storage nodes, each with local tape
> and
>> adv_file devices.
>>
>>
>>
>> I had hoped to configure the system so that all staging would be
>> localised
>> to the server in question, thus removing any network traffic during the
>> staging process.
>>
>>
>>
>> I.E.
>>
>> Staging on the networker server would only use the local adv_file device
> and
>> stage to a local LTO drive.
>>
>> Staging on the storage node would only use the local adv_file device and
>> stage to a local LTO drive.
>>
>>
>>
>> Unfortunately I cannot seem to get this working, all staging at the
>> moment
>> has to stage to a LTO device attached to the networker server.
>>
>> If I do not include a device from the networker server in the stage
>> policy
>> destination pool, I end up with the following error:
>>
>>
>>
>> 04/08/05 12:06:16 nsrd: media notice: no matching devices; check storage
>> nodes, devices or pools for save of client `networker server'
>>
>> nsrstage: error, no matching devices; check storage nodes, devices or
> pools
>>
>> nsrstage: Cannot open nsrstage session with kirkbkp01
>>
>> nsrstage: Failed to clone any save sets
>>
>>
>>
>> I would appreciate any pointers.
>>
>>
>>
>> Regards,
>>
>> Kevin
>>
>>
>>
>>
>>
>>
>> --
>> Note: To sign off this list, send a "signoff networker" command via
>> email
>> to listserv AT listserv.temple DOT edu or visit the list's Web site at
>> http://listserv.temple.edu/archives/networker.html where you can
>> also view and post messages to the list. Questions regarding this list
>> should be sent to stan AT temple DOT edu
>> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listserv.temple DOT edu or visit the list's Web site at
> http://listserv.temple.edu/archives/networker.html where you can
> also view and post messages to the list. Questions regarding this list
> should be sent to stan AT temple DOT edu
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
