Networker

Re: [Networker] VCB and Networker 7.4.x

2009-03-31 11:51:44
Subject: Re: [Networker] VCB and Networker 7.4.x
From: Fazil Saiyed <Fazil.Saiyed AT ANIXTER DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Tue, 31 Mar 2009 10:46:03 -0500
Hello,
I believe 7.5 addresses this , please check the release notes, i believe 
you can create each client the way you do normally in Networker then 
designate the proxy server and so the indexes will be separate also, this 
would be a huge improvement in which the proxy server functionality 
handles recovery of VM backups.
7.51 will take it little further by having single step recovery for VM ( 
as in release notes)
Thanks



Chester Martin <cmartin AT SPP DOT ORG> 
Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
03/31/2009 10:32 AM
Please respond to
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>; Please respond 
to
Chester Martin <cmartin AT SPP DOT ORG>


To
NETWORKER AT LISTSERV.TEMPLE DOT EDU
cc

Subject
Re: VCB and Networker 7.4.x






ALLVMFS does a file level backup <-----doesn't backup system
state...found that out the hard way... :)
*FULL* does a image level backup.

When you define a save set as VM:guest:*FULL* in the save set of the
proxy server, when you go to restore your restorable save sets will be
under the proxy server's name.  When you pull up the proxy's save set
listing you need to know the date and time that the actual save set was
backed up.  If you put in the exact date and time the os for the vm
guest will show up, but networker doesn't actually tell you what host
you're looking at.  Its save sets will still be stored under the proxy
server's name.  When I first experienced it I was thrown for a HUGE
loop.  I still don't like that it shows up like that..  Or at least this
was how it was in 7.4.1 and 7.4.2.  I trashed backing up that way
because of this... 

When you create an actual client and put *FULL* in its save set field
when you go to recover you can browse save sets under the actual client
name.

-----Original Message-----
From: John Chaney (CF) [mailto:john AT chaneyfamily DOT biz] 
Sent: Tuesday, March 31, 2009 10:10 AM
To: Chester Martin; 'EMC NetWorker discussion'
Subject: RE: [Networker] VCB and Networker 7.4.x

Chester,

Thanks for the info.

So far the only way I can backup in the environment I'm at is by using
VM:Guest:*FULL* as the saveset on the proxy host, no matter what version
of
Networker I put on the proxy host or what version of Networker I'm
running
on the Networker server (Windows or AIX).

Another item I ran across this morning is the virus scanner on the proxy
host.  I looked at the log and I see a lot of messages pertaining to
vcbmounter.  Not sure if this is the issue but I'm going to see if I can
disable the virus scanner for a test.

I just don't understand what the VM:guest:*FULL* is working but defining
the
guest as a client with *FULL* is not.  Everything works the same up to
the
point of Networker backing up the copied image.

I really do appreciate the responses from all of you.

John

-----Original Message-----
From: Chester Martin [mailto:cmartin AT SPP DOT ORG] 
Sent: Tuesday, March 31, 2009 9:51 AM
To: EMC NetWorker discussion; John Chaney (CF)
Subject: RE: [Networker] VCB and Networker 7.4.x

We're running 7.4.4 with vcb 1.5, we've done image(windows/linux) and OS
level (windows).  We're using the proxy server as a storage node.  It's
been running pretty solid.  We've upgraded from 7.4.1 to 7.4.2 to 7.4.3
to 7.4.4.
 
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of John Chaney (CF)
Sent: Monday, March 30, 2009 8:50 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] VCB and Networker 7.4.x

The Proxy is windows 2003 and I'm using the latest VCB module 1.5.

 

I have logging in the config.js set to 6 but cannot find a log file
anywhere
other than what is displayed on the screen during the snapshot and copy
of
the images.

 

I have run save.exe with -D6 to capture as much info as I can using
Networker but nothing is being sent to any logs.

 

It just seems that the symptom happens when I use the Proxy as a Storage
Node.  I'm going to back down the Networker on the proxy to 7.4.2 and
see
what I get.  Has anyone testing 7.4.4 with VCB yet?

 

Thanks,

 

John

 

From: Fazil.Saiyed AT anixter DOT com [mailto:Fazil.Saiyed AT anixter DOT com] 
Sent: Monday, March 30, 2009 8:25 AM
To: EMC NetWorker discussion; John Chaney
Cc: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: VCB and Networker 7.4.x

 


Hello, 
VCB backups rely on configures (module  from vmware, installed on proxy
server) and vcenter integration as well as ability of proxy ( SN )
server to
see all VM Data store that you backup, has this been looked at ? which
version of integration module are you using as well as vmware version ? 
Proxy server has to be Windows 2003 & preferably, drive automounting on
windows should be turned off. 
There a few log files in the SN servers install directory that may
explain
why the images are being deleted before backup, check your config.js
options. 
HTH 





John Chaney <john AT CHANEYFAMILY DOT BIZ> 
Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU> 

03/28/2009 09:23 AM 


Please respond to
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>; Please respond
to
John Chaney <john AT CHANEYFAMILY DOT BIZ>


To

NETWORKER AT LISTSERV.TEMPLE DOT EDU 


cc

 

Subject

VCB and Networker 7.4.x

 

 




Hey everyone,  I would like to know what your experiences have been with

VCB and Networker 7.4.x. 

I did my first VCB implentation about 18 months ago at a customer site
with 
Networker 7.4.  Off the top of my head I can't rememeber the VCB version

but after much trial and error I was able to get it to work by using the

Proxy Host (storage node) and defining the savesets as
VM:guestname:backup 
type in the saveset field, plus defining save_vcb.bat in the backup
command 
field.  Of course, we had the normal issues that made EMC change their 
method of backing up VM's in 7.4.1 but at least it backed up.

Later I installed VCB with Networker 7.4.1 at some other sites and had
to 
figure out the new method of creating a client for each Guest and using
the 
VCB option on the client definition.  This was better although the
customer 
was upset because now it required a client license.  In any case it
backed 
up.

Recently I have been contracted to implement VCB with Networker again.
The 
Networker server is 7.4.2 on AIX and we have 7.4.4 on the Proxy Host.
For 
some reason when we define the Guest as a Networker client and set all
of 
the parameters the backup part fails.  It will create the snapshot, copy

the vmdk's to the proxy host, but as soon as the copy finishes, the copy

directory gets deleted and then the snapshot gets cleaned up.

If I define the guest the old way (as a saveset on the proxy host) then
it 
backs up.

My first guess was the Networker 7.4.2 vs. 7.4.4 compatibility issue.
We 
had a DR Networker server running 7.4.4 so I tried testing it there and
got 
the same results.

My second guess was that the Networker server was running AIX.  Of the
17 
years I've been running Networker, I only know two company's running it
as 
a server on AIX.  So I created a Networker 7.4.4 server on a Windows 
system.  Got the same results.

What is strange is I can install Networker server on the Proxy host and 
everything works as expected.  All methods of VCB backups work.

I have other toughts on what the issue may be (such as they run Netware 
Directory Services for authentication) that may be the culprit, but I 
wanted to run it by you guys to see if you've experienced anything like 
this.

Just so you know, we are just going to backup the image level.  They
also 
backup at the file level using Networker client.  We will just backup
the 
images one a week or month.  Should a system crash or we need to do a
DR, 
we will restore the image and then just do a file level restore to bring

the system up to date.

Thanks in advance for any hepful responses.

Sincerely,

John Chaney

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


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

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


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