Backup Central

All,

Any body on 7.6.3.1 Networker server version and facing any issues?

Please discuss here.

thanks

Jyo

We upgraded from 7.5.3.3 to 7.6.3.1 a week ago.
What we have seen so far is a problem with groups not closing alright.
The first night all was ok, but not the second night.

Since we are running Windows Server 2003 R2 x64 on the backup server, we installed patch KB979230 to fix the problem.
"KB979230 TCP connections fail intermittently when both endpoints are on the same computer"

It seems to be working now and really good too.

Most of the Windows client problems with VSS, RSM and so on is now working, but you have to install the 7.6.3.1 client as well.

Another MS patch for the client Windows Server 2003 is KB944328, it solves some RSM and VSS problems.
"KB944328 A backup operation fails, and a function failure is reported when no media is in the removable media drive".

Hi Iny,

Do you have any issues on savepnpc and VSS clients?
So the groups are not hung after applying the fix?

Pls advise what VSS issues you had before on W2k3 before you applied the patch.

We are still on 7.6.2.2 and we got VSS hung backups. Expecting that the 7.6.3.1 will fix the issue.

thanks

Sorry, we dont use savepnpc at all right now.
It´s easy to test this functionality with a test environment before you upgrade the production site.

We had this kind of problem with a couple of 2003 clients before we upgraded to 7.6.3.1 and applied the MS patch KB944328.

Removable Storage Database - rsmow: Could not start RSM service for backup operation.
Removable Storage Database - Error saving
39078:save: RPC error: Can't encode arguments
7162:save: save of SYSTEM DB:\ to backup1.orebroll.se failed
<ERROR> : Failed with error(s)


VSS SYSTEM BOOT: ERROR: VSS failed to process snapshot, error=0x8000ffff: Unexpected VSS system error. The error code is logged in the event log.
7162:save: save of VSS SYSTEM BOOT:\ to backup1.orebroll.se failed
<ERROR> : Failed with error(s)

This subject has come up quite a bit for me lately. I thought I would
share what I have and see if any others have updates or more info they
would like to share?

Networker does not control VSS - it simply asks VSS for the files that
are open. Microsoft VSS is problematic at times and I have seen many
times where VSS will not respond properly and Networker (or for that
matter any other backup software I have worked with) is just waiting for
the ack back and then the notification that the files are ready to be
backed up.

Having dealt with VSS issues since Windows 2000, I have compiled a list
of MS KB articles. Here is what I have for Windows through 2008 (note
that some may not apply to our situation, but others may find them
useful):

Knowledge base articles - known Windows 2008 VSS issues:

SYMPTOM: VSS snapshot creation may fail after a LUN resynchronization on
a computer that is running Windows 7 or Windows Server 2008 R2 -
November 25, 2009
ENVIRONMENT: Windows 7, Windows Server 2008 and Windows Server 2008 R2
http://support.microsoft.com/kb/976099


SYMPTOM: Backup fails with VSS Event ID 12292 and 11
ENVIRONMENT: Windows Server 2008 and Windows Server 2008 R2
CAUSE: ServiceDll registry value for Swprv is missing or incorrect
SOLUTION: Edit the Registry following the steps in
http://support.microsoft.com/kb/2009513


No VSS writers are listed when you run the "vssadmin list writers"
command in Windows Server 2008 R2
http://support.microsoft.com/kb/2009550
http://support.microsoft.com/kb/2009533

Windows 2008 R2 64-bit backup failed
http://solutions.emc.com/emcsolutionview.asp?id=esg108377

System State backup using Windows Server Backup fails with error: System
writer is not found in the backup
http://support.microsoft.com/kb/2009272


A VSS hardware snapshot database keeps growing with duplicated
...(959476) - ... VSS) requestor instances with VSS hardware provider to
delete snapshots in Windows Server 2008 ... Important Windows Vista and
Windows Server 2008 hotfixes ...
http://support.microsoft.com/kb/959476

A snapshot may become corrupted when the Volume Shadow Copy ...(975688)
- Fixes a problem in Windows 7 and in Windows Server 2008 R2 in which a
snapshot may become corrupted when the VSS snapshots providers takes
more than 10 ...
http://support.microsoft.com/kb/975688

A virtual machine online backup fails in Windows Server 2008 R2 ... This
issue occurs because the Hyper-V Volume Shadow Copy Service (Hyper-V VSS
... Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are
included in ...
http://support.microsoft.com/kb/2521348

You cannot safely remove volumes after you perform a VSS backup ...
(2487341) - ... files after you perform a Volume Shadow Copy Service
(VSS) backup operation in Windows Server 2008 SP2. ... Windows Vista
hotfixes and Windows Server 2008 hotfixes ...
http://support.microsoft.com/kb/2487341

Also, please note that not all of these fixes come with Windows update
and may be used on a case by case situation. Now, from the client side,
one thing you can do is to check on the status of VSS from the command
line using vssadmin.

Here are a couple of MS KB articles to get you started:

Vssadmin usage
http://technet.microsoft.com/en-us/library/cc754968(WS.10).aspx

Manage Volume Shadow Copy Service from the Vssadmin Command-Line
http://technet.microsoft.com/en-us/magazine/dd348398.aspx

How to enable the Volume Shadow Copy service's debug tracing features in
Microsoft Windows Server 2003 and Windows 2008
http://support.microsoft.com/kb/887013

Oh - one other thing we can do from both the server is to render the
daemon.raw file. To do this, make a copy of the /nsr/logs/daemon.raw
file - I typically rename the copy to be daemon_YYYYMMDD.raw.

From the command line, navigate to the directory the copied daemon.raw
file is in, then run:
nsr_render_log daemon_YYYYMMDD.raw >daemon_YYMMDD.log

ie. nsr_render_log daemon_20120127.raw >daemon_20120127.log

Semper fidelis et paratus, /ALE


-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU] On
Behalf Of bangrn
Sent: Wednesday, February 15, 2012 8:41 PM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: [Networker] Any one on 7.6.3.1 Networker server version?

Hi Iny,

Do you have any issues on savepnpc and VSS clients?
So the groups are not hung after applying the fix?

Pls advise what VSS issues you had before on W2k3 before you applied the
patch.

We are still on 7.6.2.2 and we got VSS hung backups. Expecting that the
7.6.3.1 will fix the issue.

thanks

+----------------------------------------------------------------------
|This was sent by naga.bangaru < at > citec.com.au via Backup Central.
|Forward SPAM to abuse < at > backupcentral.com.
+----------------------------------------------------------------------


type "signoff networker" in the body of the email. Please write to
networker-request < at > listserv.temple.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


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Hi Eddie,

Thanks for the update.

Do you know of any issues with savepnpc (pre/post script) clients on both w2k3 and w2k8 clients?


thanks again for making this thread so discussion friendly.

Do you know of any issues with savepnpc (pre/post script) clients on
both w2k3 and w2k8 clients?

I ran into this recently, with 7.6.2 and Win2008 clients, using savepnpc.
Check the mailing list archives for full details ...

Apparently it was a
permissions issue - the client Networker services were running as SYSTEM,
and SYSTEM can't apparently run scripts (or wouldn't run my scripts, I
don't know which). Regardless, I changed the client Networker services to
run as a user with local admin privileges (that was able to execute the
script), then it all Just Worked. Support also said they had seen issues
where scripts must be invoked in the .RES file with the short 8.3 format
path, and in the CMD file as well.

So ... when doing "savepnpc", make sure the client Networker services are

running as a user account that has access to execute your script, and not
as SYSTEM, under Windows.

Oh, and it seems that Networker will mark the job as completed, when it
calls the post cmd script .. and *not* when that script actually finishes.

It takes approx 5 minutes for my post cmd script to complete resuming the
application services, but Networker reported the job as complete when the

script started, not when it finished .. .even tho the application that the

script was resuming was not yet available.

Just something to be aware of ....


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER