Skip to content

Cumulative NetWorker hotfix 7.6.2.6 build 689 has been released

Cumulative hotfix 7.6.2. 6 includes the following fixes  :

NW131423 – nsrvadp_save crashes during incremental save
http://solutions.emc.com/emcsolutionview.asp?id=esg125281

NW133164 – JB resource updates result in excessive updates to media database by nsrmmgd daemon
http://solutions.emc.com/emcsolutionview.asp?id=esg125138

NW129444 – nsrinfo Core dump on Solaris NetWorker server when run against Windows 2008 Clients
http://solutions.emc.com/emcsolutionview.asp?id=esg124017

NW131688 – NetWorker is not creating the dataset attribute cacheprefix for VADP Avamar deduplication clients
http://solutions.emc.com/emcsolutionview.asp?id=esg125090

NW132690 – NMO Backup and Restores fail: ‘(Resource temporarily unavailable)’
http://solutions.emc.com/emcsolutionview.asp?id=esg125100

NW131825 – Scanner fails with error: ‘unexpected file number’
http://solutions.emc.com/emcsolutionview.asp?id=esg125151

NW132481 – gstd daemon dumps core when NMC GUI is closed
http://solutions.emc.com/emcsolutionview.asp?id=esg124920

NW133031 – NMC upgrade to Apache 2.2.21 due to Apache vulnerability CVE-2011-3192
http://solutions.emc.com/emcsolutionview.asp?id=esg125152

NW130276 – savegrp hangs waiting on session
http://solutions.emc.com/emcsolutionview.asp?id=esg123307

NW128816 – NMC compatibility issues with Java 7 and Java 1.6.0_27 and above
http://solutions.emc.com/emcsolutionview.asp?id=esg124036

This package is available at: ftp://ftp.legato.com/pub/NetWorker/Cumulative_Hotfixes/7.6

Windows 2008 System backups fails with the error Failure status of writer ASR Writer – VSS_WS_FAILED_AT_PREPARE_SNAPSHOT Or VSS failed to get comp=BCD FileGroup list, writer=ASR Writer, error=0x80070008: Not enough storage is available

Windows 2008 System backups fails with the error:

5388:save: Failure status of writer ASR Writer – VSS_WS_FAILED_AT_PREPARE_SNAPSHOT

VSS SYSTEM BOOT: ERROR: VSS failed to process snapshot, error=0x800423f0: The shadow copy set contains only a subset of the volumes needed by the writer to correctly backup the application.

Or you may have this error as well:

43705:save: Save Operations value is ignored on this OS platform.

ERROR: VSS failed to get comp=BCD FileGroup list, writer=ASR Writer, error=0x80070008: Not enough storage is available

To solve this issue, run firstly the command vssadmin list writers to check the VSS writers states, if you have some writers not in stable state or having some errors, you need to restart the Volume Shadow Copy service and COM+ Event System service , and then re-check again using the command vssadmin list writers

If all writers are in stable state, you have to assign a drive letter to the system reserved drive from the Windows Disk Management in Windows 2008 , but a drive letter other than X: ,as  X: drive is used by the WinPE image as the system drive. ( assign B: drive letter as an example)

Re-run again the backup and problem should be fixed.

System State backup using Windows Server Backup fails with error: System writer is not found in the backup – System Writer is missing

When you perform a system state backup using Windows Server Backup on Windows Server 2008, the backup fails with the error:

System writer is not found in the backup.

When you run the command vssadmin list writers , you will find that the System Writer is missing from the writers list , this is because permissions to files in the %windir%\winsxs\filemaps\ or %windir%\winsxs\temp\PendingRenames directories are incorrect.

To solve this problem and populate the System Writer back again to the list, run the following commands from the command prompt in order:

Takeown /f %windir%\winsxs\temp\PendingRenames /a

icacls %windir%\winsxs\temp\PendingRenames /grant “NT AUTHORITY\SYSTEM:(RX)”

icacls %windir%\winsxs\temp\PendingRenames /grant “NT Service\trustedinstaller:(F)”

icacls %windir%\winsxs\temp\PendingRenames /grant BUILTIN\Users:(RX)

Takeown /f %windir%\winsxs\filemaps\* /a

icacls %windir%\winsxs\filemaps\*.* /grant “NT AUTHORITY\SYSTEM:(RX)”

icacls %windir%\winsxs\filemaps\*.* /grant “NT Service\trustedinstaller:(F)”

icacls %windir%\winsxs\filemaps\*.* /grant BUILTIN\Users:(RX)

net stop cryptsvc

net start cryptsvc

Then run vssadmin list writers command to verify that the system writer is now listed.

Error while creating a SQL Client instance using Client Configuration Wizard, the error is: “Referenced object does not exist”

Cause:

Client Wizard uses SQL Distributed Management Objects (SQL-DMO) to communicate with SQL Server to populate its databases to be configured as savesets from the wizard.

It used to be part of the SQL Server package before. However, with SQL Server 2008, it was split out into a separate feature pack. So to use Client Wizard for SQL Server 2008 you have to install SQL-DMO separately on the SQL Server Client.

Resolution

Install the SQL Server 2005 Backward Compatibility Components, Which can be downloaded from the following Microsoft Website:

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=16177

Download the SQL Server 2005 Backward Compatibility Components correspond to your SQL platform (x86, x64 or IA64)

Firstly, Make sure that the Strong Authentication (nsrauth) is Enabled on the client as it is a required setting for the wizard and the browse icon features to function. To check if it is enabled or not, try the following steps:

Open a cmd prompt from the client, and run:

nsradmin -p nsrexec

nsradmin> show auth methods

nsradmin> print type: nsrla

auth methods: “0.0.0.0/0,nsrauth/oldauth”;

Note: make sure nsrauth is on

If nsrauth not on, so you have to enable it on the NetWorker Client. Here are the steps to accomplish this task from the command prompt on the client:

C:\nsradmin -p nsrexec
NetWorker administration program.
Use the “help” command for help.
nsradmin> . type: nsrla
Current query set
nsradmin> show auth methods
nsradmin> print
auth methods: “0.0.0.0/0,oldauth”;
nsradmin> update auth methods: “0.0.0.0/0,nsrauth/oldauth”
auth methods: “0.0.0.0/0,nsrauth/oldauth”;
Update? y
updated resource id 2.3.80.1.70.157.87.68.67.190.164.357(32)
nsradmin> print
auth methods: “0.0.0.0/0,nsrauth/oldauth”;
nsradmin> quit

Restart the NetWorker services on the NetWorker Client.

If the problem still exists, you have to delete the nsr peer information from the client.

Use the following commands to delete the NSR Peer Information

C:\nsradmin -p nsrexec
NetWorker administration program.
Use the “help” command for help.
nsradmin> . type: nsr peer information

Current query set

nsradmin> print

type: NSR peer information;
administrator: Administrators,
“group=Administrators,host=Egy”;
name: Bebo;
peer hostname: Bebo;
Change certificate: ;
certificate file to load: ;

nsradmin> delete

delete? y

deleted resource id 2.3.80.1.70.157.87.68.67.190.164.357(32)

nsradmin> quit

Note: Delete all ‘nsr peer information’ entries on that client.

Restart Networker services on client.

nsrexced.exe binary faults and crashes on librpc.dll and produces an application error after updating to NetWorker 7.6.1.x on Windows 2008

  • The nsrexced.exe binary faults and crashes on librpc.dll and produces an application error after updating to NetWorker 7.6.1.x on Windows 2008.
  • Nsrexecd service is always crashes once it has been started.
  • No errors in the daemon.raw while the following is logged in the Windows Application Event log.

Faulting application nsrexecd.exe, version 7.6.1.4, time stamp 0x4d6800a8, faulting module LIBRPC.DLL, version 7.6.1.4, time stamp 0x4d67f7ed, exception code 0xc0000005, fault offset 0x0000000000017a04, process id 0x1b54, application start time 0x01cbe980df9e6d2e.

Cause

  • Known issue: NW127771: NetWorker for Windows 7.6.1.4 nsrexecd.exe faults on librpc.dll
  • Possible corruption of one of the entries in nsrladb.

Resolution

  • Install the latest Cumulative Fixes package for NetWorker 7.5 and 7.6.
    • You can download the latest Cumulative Fixes package for NetWorker 7.5 and 7.6 from the following locations:

ftp://ftp.legato.com/pub/NetWorker/Cumulative_Hotfixes/7.5

ftp://ftp.legato.com/pub/NetWorker/Cumulative_Hotfixes/7.6

  • If the problem still exists after updating to the latest cumulative fix, stop the nsrexecd service on the storage node or the client producing this error and rename the nsrladb folder under the res directory then restart nsrexecd. This time nsrexecd stays up and running.

VADP Recovery Error “media is write protected.” OR “Error Writing to VMDK: 0 bytes written intstead of”

Recovery of a VM using SAN or hotadd transport mode on Windows 2008

When using SAN transport or HotAdd mode on a Windows Server 2008 proxy, make sure to set the Windows SAN policy to onlineAll, otherwise writes produce the error messages “media is write protected.” OR “Error Writing to VMDK: 0 bytes written intstead of”

Perform the following one-time configuration on the proxy host before initiating the recovery:

1. Open a command prompt on the proxy host.

2. Run the following command:

DISKPART

3. Enter SAN and check for the SAN policy.

4. If the policy indicates offline, enable the policy by entering the following:

SAN POLICY=OnlineALL

You can now initiate the VM recovery using san or hotadd mode.

Note 1: If recovery is initiated from a Windows machine other than the proxy, these steps need to be performed on the machine where the recovery is initiated.

 Note 2: For image recovery via SAN mode, ensure that the VADP proxy has read-write access to the SAN LUNs hosting the virtual machines. To ensure read-write access, add the VADP proxy to the same fabric zones to which the ESX server system belongs.

NDMP level 1-9 backup failed

NDMP backup aborted frequently on incremental (level 1-9 backups) due to inactivity timeout. There is a group inactivity timeout setting in the Group Resource in NetWorker. The default value is 30 minutes.

NAS devices takes a very long time to first walk the filesystem and compare file headers to determine which files have changed since the last lower level backup. When this exceeds the group timeout, the backup will fail.

Change the group inactivity timeout setting to 0 (zero) which is infinite and then see how long it is really taking to finish the backup and adjust the group inactivity timeout accordingly.

Disaster Recovery: X drive is detected as a critical volume but cannot be included in the savesets

Conflict with drive letter X: because the drive letter X: is used by the WinPE image as the system drive. This creates a conflict with any critical volume that uses the drive letter X:

If a critical volume uses the drive letter X:, the disaster recovery backup will fail with error message:

Disaster Recovery: X drive is detected as a critical volume but cannot be included in the savesets.

To remedy the situation, Change the Drive letter to any other letter rather than X: ( as an example assign B: as a drive letter instead of X:)

EMC to Acquire Greenplum

EMC TO ACQUIRE Greenplum

Disruptive Data Warehousing Technology Enables New Era of
“Big Data” Clouds and Self-Service Analytics

http://www.emc.com/about/news/press/2010/20100706-01.htm

NetWorker Cumulative Fixes Are Now Available

NetWorker Cumulative fixes (7.6.0.3, 7.5.2.1, and 7.4.5.6) are now available , Here is the official release announcements and hotfixes included:

For 7.6:
http://powerlink.emc.com/km/live1/en_US/Offering_Basics/Articles_and_Ann ouncements/NetWorker7_6_0_CumulativeHotfixes.pdf
For 7.5 SP2:
http://powerlink.emc.com/km/live1/en_US/Offering_Basics/Articles_and_Ann ouncements/NetWorker7_5_2_CumulativeHotfixes.pdf
For 7.4 SP5:
http://powerlink.emc.com/km/live1/en_US/Offering_Basics/Articles_and_Ann ouncements/NetWorker7_4_5_CumulativeHotfixes.pdf