Networker

[Networker] : NW test server

2007-07-27 12:59:08
Subject: [Networker] : NW test server
From: Fazil Saiyed <Fazil.Saiyed AT ANIXTER DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 27 Jul 2007 11:55:21 -0500
Hello,
I am not advocating any changes to Networker environment, pools, policies 
etc, the testing i am talking about is verification whether or not a 
client backups will be successful or not, is the name resolution working 
or not , client side scripts functionality?
Not sure what risk are introduced when a newly created client is placed in 
Default group with no other backup actively on the server and verified its 
backup ?
We do not have parallel Networker environment where i have the luxury to 
test routine client installs, either way no two server\backup environments 
would be completely equal any way. In any case due diligence and proper 
change control procedures should be followed.
If in  your environment you can manage to have couple of servers available 
for testing well and good, but i would imagine that scenario is not very 
common, i appcreate your concern though and yes we have good change 
controls.
Thanks



Davina Treiber <Davina.Treiber AT peevro.co DOT uk> 
07/27/2007 08:41 AM

To
EMC NetWorker discussion <NETWORKER AT listserv.temple DOT edu>, Fazil Saiyed 
<fazil.saiyed AT anixter DOT com>
cc

Subject
Re: [Networker] : NW test server






Fazil Saiyed wrote:
> the other thing is you can always use production 
> Networker server during off peak hrs to do client testing, scripts etc.

I don't know about you but in most environments I have worked in this 
would be a complete no-no.

Can you spell "change control"?




To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

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