Skip to content

Cumulative Hotfixes included in 7.6.3.2 Build 860

Cumulative hotfix 7.6.3.2 includes the following fixes

NW135020 – nsrwatch core dumps 7.6.2

esg127221: http://solutions.emc.com/emcsolutionview.asp?id=esg127221

NW133029 – Autochanger unlimited/32767 License is automatically deleted from NLM when the autochanger slots exceed 32767

esg126103: http://solutions.emc.com/emcsolutionview.asp?id=esg126103

NW131986 – Nsrexecd core dumps on Windows 2003 backup server after upgrade to NW7.6.2.2

esg127052: http://solutions.emc.com/emcsolutionview.asp?id=esg127052

NW135040 – GSTD Core when marking an unlabelled volume readonly

esg127288: http://solutions.emc.com/emcsolutionview.asp?id=esg127288

NW134973 – VADP backup failing for clients in DMZ (internal error occurred: libcurl error: Timeout was reached)

esg127348: http://solutions.emc.com/emcsolutionview.asp?id=esg127348

NW135221 – nsr_render_log not rendering all required information

esg127342: http://solutions.emc.com/emcsolutionview.asp?id=esg127342

NW132517 – Able to re-label WORM volumes

esg127345: http://solutions.emc.com/emcsolutionview.asp?id=esg127345

NW129960 – Save.exe uses 99% CPU usage when Avamar node is used for backup on the client

esg127371: http://solutions.emc.com/emcsolutionview.asp?id=esg127371

NW134618 – Image recover for VADP backup reports error “Failed to propagate handle”. Recover successful

esg127370: http://solutions.emc.com/emcsolutionview.asp?id=esg127370

NW133248 – lgtolmd poll() error: Invalid argument

esg127376: http://solutions.emc.com/emcsolutionview.asp?id=esg127376

VADP backup fails with “Identified an independent disk with label “Hard disk 1″ within the VM. This disk shall not be part of backup.” AND “Parser failed because of a non-NTFS volume inside the VM.”

Symptoms:

82788:nsrvadp_save: Identified an independent disk with label “Hard disk 1” within the VM. This disk shall not be part of backup.

There are no available virtual disks for backup.

80432:nsrvadp_save: Parser failed because of a non-NTFS volume inside the VM.

Backup of the non-NTFS volume Success.

Cause:

Independent persistent disks are not backed up:
VADP does not support the backup and recovery of independent persistent disks. If
such disks are detected during backup, they are skipped and a message is logged that
indicates the disks were skipped. However, during an image level recovery, the disk
is recovered without any data. If using independent persistent disks, you must use
the traditional NetWorker style backup for protecting the data on the independent
persistent disks via the backup client installed inside the VM.

How to mark a ssid/clone id as suspect/notsuspect without using scripts

This article if you have multiple savesets in suspect mode or not suspect mode and you want to change their mode one time without using scripts.

Firstly you will need to run the mminfo command to get the details of the savesets which are marked as suspect, run the following command:

mminfo -avot  -q suspect -r ssid,cloneid,volume

In which command will give you the set of ssid, cloneid and the volume name in which the savesets are marked as suspect.

Copy the output of the suspect save sets in an Microsoft Excel Sheet with the command on the first column and the ssid/clone id in the second column like the following example:

Command                                                 ssid/cloneid

nsrmm -y -o notsuspect  -S                      2617625/1346792

nsrmm -y -o notsuspect  -S                      3615675/1526718

nsrmm -y -o notsuspect  -S                      5317721/1746601

Then copy the list from the Microsoft Excel and then paste it in the Command Line (cmd) of the backup server where the commands will be running one by one automatically.

The list of the entire ssid/clone id will be marked as notsuspect and then can be shown for running a clone job or for a recovery.

Note:

The same method is used for deleting multiple save sets or clone id by using the nsrmm -d command

Replace the above example with the right command and the correct SSID or Clone id

Make sure the SSID’s before deletion as once deleted cannot be retrieved.

How to install Networker 7.6.2 client on Debian GNU Linux Or Ubuntu Platforms

As Debian GNU Linux &  Ubuntu are not officially supported platforms for NetWorker by EMC, Also there currently is no out of the box install procedure as there is only .rpm install files available from the NetWorker Installation Packages for Linux. So to be able to install NetWorker on Debian GNU or Ubuntu , you have to use a tool like “alian” to convert the .rpm to .deb format, Here is the steps for this UNSUPPORTED installation.

  1. Install alien package converter on the linux box by running the following :

root@bebo:~# apt-get install alien

  1. Extract the NetWorker Package, then Convert the NetWorker client from rpm format to deb format, as rpm :

root@bebo:~# alien lgtoclnt-7.6.2-5.x86_64.rpm

  1. Install the new converted deb package by running the following ( Take care that name will be changed for amd64 for the x64 packages):

root@bebo:~# dpkg -i lgtoclnt_7.6.2-5_amd64.deb

  1. Start the NetWorker client. Which will create the /nsr directory :

root@bebo:~# nsrexecd

  1. Then kill the NetWorker client daemon ( you have to get the Process ID by the ps -ef | grep nsr command )

root@bebo:~# kill PIDof nsrexecd

  1. Create the /nsr/res/servers file under the /nsr/res directory and put inside it the FQDN of the backup server to be like that:

root@bebo:~# cat /nsr/res/servers

bkp.ntwrkr.local

7.   Create the /etc/init.d/networker script file under the /etc/init.d directory and paste in it the following script:

#! /bin/sh

# Copyright (c) 1990-2009, EMC Corporation

# All rights reserved.

### BEGIN INIT INFO
# Required-Start: syslog network
# Required-Stop: syslog network
# X-UnitedLinux-Should-Start: portmap
# Should-Start: portmap
# Default-Start: 3 5
# Default-Stop: 0 1 2 6
# Description: EMC Networker. A backup and restoration software package.
### END INIT INFO

case $1 in
    start)
        (echo 'starting NetWorker daemons:') > /dev/console
        LD_LIBRARY_PATH=/usr/lib/nsr:$LD_LIBRARY_PATH
        export LD_LIBRARY_PATH
        if [ -f /usr/sbin/nsrexecd ]; then
                if [ -f /usr/sbin/NetWorker.clustersvr ]; then
                        if [ -f /nsr.NetWorker.local -o -h /nsr.NetWorker.local ]; then
                                if [ -h /nsr ]; then
                                        rm -f /nsr
                                        ln -s /nsr.NetWorker.local /nsr
                                fi
                        fi
                fi
            (/usr/sbin/nsrexecd) > /dev/console 2>&1
            (echo ' nsrexecd') > /dev/console
        fi
        if [ -f /usr/sbin/lgtolmd ]; then
            (/usr/sbin/lgtolmd -p /nsr/lic -n 1) > /dev/console 2>&1
            (echo ' lgtolmd') > /dev/console
        fi
        if [ -f /usr/sbin/nsrd -a \
             ! -f /usr/sbin/NetWorker.clustersvr ]; then
            (/usr/sbin/nsrd) > /dev/console 2>&1
            (echo ' nsrd') > /dev/console
        fi
        ;;
    stop)
        (echo 'stopping NetWorker daemons:') > /dev/console
        if [ -f /usr/sbin/nsr_shutdown ]; then
            if [ -f /usr/sbin/NetWorker.clustersvr ]; then
                (/usr/sbin/nsr_shutdown -q) > /dev/console 2>&1
                (echo ' nsr_shutdown -q') > /dev/console
            else
                (/usr/sbin/nsr_shutdown -q) > /dev/console 2>&1
                (echo ' nsr_shutdown -q') > /dev/console
            fi
        fi
        ;;
    status)
        if [ -f /usr/sbin/nsr_shutdown ]; then
            /usr/sbin/nsr_shutdown -l
        fi
        ;;
    *)
        echo "usage: `basename $0` {start|stop|status}"
        ;;
esac

8.   Run the following command to update the rc script of that client:

root@bebo:~# update-rc.d networker defaults

9.  Start the NetWorker client process again:

root@bebo:~# nsrexecd

NOW, you have NetWorker running on Debian GNU or Ubuntu platforms , but still it is UNSUPPORTED by EMC.

Announcing EMC NetWorker 7.6 SP3

Today EMC announced the availability of NetWorker 7.6 SP3.  This release delivers NetApp SnapMirror to tape backups, a new Mac recovery GUI and accumulated fixes.  This release addresses disaster recovery of high density NetApp filers using SnapMirror, answers customer requests for a native Mac recovery GUI and maintains high quality with accumulated fixes.

Key features of NetWorker 7.6 SP3 include:

  • NetApp SnapMirror to tape is designed to provide a true DR copy of the NetApp data volume. SnapMirror brings value in scenarios where there are millions of files residing on the filer.  Support for NetWorker, NetWorker Module for Microsoft Applications and NetWorker Module for Databases and Applications with NetApp SnapMirror will help significantly reduce backup windows.
  • The new Mac recovery graphical user interface (GUI) allows identical recovery functionality that is available with standard recovery GUI. Not included are archive set recovers, BMR recovers, NDMP recovers and file exclusion lists.  See demonstration below.
  • OS Currency with: IBM AIX 7.1, MAC OS X 10.5 (Lion), Oracle Solaris 11 Express
  • Support for VMWare vSphere 5.0
  • Improved multiplexing to DataDomain VTL
  • Accumulated fixes

This release is being made available under a phased product release lifecycle.  Production ready software is first released to Restricted Availability (RA). RA releases are fully-tested and production-ready, however, software and documentation are made available through an alternate process that lets EMC track adoption to ensure the early roll out meets customer expectations. After initial monitoring of progress in the marketplace, the software and documentation will be transitioned to General Availability (GA).

NetWorker Backup Levels

Because it may not be practical or efficient to run full backups every day, you can specify the level of the backup to be performed during scheduled backups. By limiting the frequency of full backup, you help maintain server efficiency, while still ensuring that data is protected. Different backup levels enable you to trade off the number of volumes and amount of time required to complete a backup with that required to recover from a disk crash.

NetWorker has five kinds of backup levels, which are:

1- Full : Backs up all files, regardless of whether or not they have changed ( called Level Zero)

2- Level [1 – 9] : Backs up files that have changed since the last backup with a lower-numbered backup level.
For example:
• A level 1 backup backs up all files that have changed since the most recent full backup.
• A level 3 backup backs up all files that have changed since the most recent backup at level 2, level 1, or full. For example, if the most recent backup was at level full, then a level 3 backup will back up all files that changed since the full backup. However, if the most recent backup was at level 2, then a level 3 backup will back up only those files changed since the level 2 backup.
• A level 9 back up backs up all the files that have changed since the most recent backup of any level except level 9.

Note: The NetWorker software ignores any incremental-level backups when determining what files should be backed up.

3- Incremental : Backs up files that have changed since the last backup, regardless of level.

4- Consolidated: Backs up all data that has changed since last full backup and then merges these changes with the last full backup.

5- Skip : Skips the scheduled backup. For example, you can skip a backup on a holiday if no one will be available to change or add more media volumes.

Configuring NMC LDAP Authentication Error “External Role is invalid”

While Configuring login through external authentication via LDAP, you get the following error when adding the sAMAccountname in the external role window:

Error: “External Role <username> is invalid”

This issue is cased by either mismatching in the supplied username with what is retrieved by NMC from the Active Directory Or  an all lowercase username is entered in the External Role window, but an all uppercase username was retrieved by NMC.

Simply, to solve this issue, you have to enter an all uppercase sAMAccountname in the External Role window. As an example if the Account name is called ADMin , you cannot add it as admin or Admin , you have to add it like ADMin as it exists in the Active directory ( Case Sensitive)

How to Enable and Configure LDAP Authentication Login for NetWorker Management Console

IMPORTANT NOTE: once you set up LDAP authentication you can’t use the built in administrator account to log on NMC unless you reset it again (Check at the end of the article how to reset it back again)

  1. Create a user as an example called NsrValley where its logon name is NsrValley in the “Users” Container in the Active Directory.
  2. Launch Management Console.
  3. Select Setup Button.
  4. Select Setup Pull-Down Menu.
  5. Select Configure Login Authentication
  6. Select External Repository and click Next
  7. Click Add and then provide information in the following Attributes:
  • Authority Name: Any Name of this LDAP authority. ( let’s say LDAP).
  • Type: The types of protocol used. Example: LDAP-v3 or AD.
  • Provider Server Name: Hostnames or IP addresses of the LDAP server to use for authentication. Put the domain controller FQDN or the IP address of it. (let’s say as an example dc.domain.root)
  • Distinguished Name:Distinguished name (DN) of the privileged account used to perform operations, such as searching users and groups, on the LDAP directory. There is no default value. An example distinguished name in the prescribed format is: “cn=NsrValley,cn=Users,dc=domain,dc=root “                      Note: Spaces are only allowed within this attribute
  • Password: Password created above for the account created called NsrValley
  • User Search Path: The distinguished name (dn) at which to begin user searches on the node.  Example: cn=Users,dc=domain,dc=root
  • Group Search Path: The distinguished name (dn) at which to begin group searches on the node.   Example: cn=Users,dc=domain,dc=root
  • Group Name Attribute: Attribute identifying the group name. The default attribute is cn.
  • LDAP Timeout (millisecond): Timeout for the LDAP calls. The default timeout is (30000).

In the Advanced section provide the following:

  • User ID Attribute: Attribute identifying the user login ID in Active Directory (AD), the attribute used for user account names is typically sAMAccountName. For other directories, the default user id uid is often used. So specify this attribute as  sAMAccountName
  • User Object Class: specify this attribute as User
  • Group Object Class: specify this attribute as group
  • Group Member Attribute: specify this attribute as member
  • Protocol: Protocol to use is LDAP or LDAPS (SSL)
  • Port Number: The port number of the LDAP service. Valid values are 1 through 65535. Value for LDAP is 389 and for LDAPS is 636.
  • Click Next
  • On the “Setup Console Security Administrator Role” screen, under External Roles , you have to specify and add the logon name of at least one account or group from Active Directory, The users or groups added must be located in active directory where the search paths were defined (Like in our example cn=Users,dc=domain,dc=root)
  • Click Finish
  • Restart the EMC GST Service.
  • You should now be able to login using the account specified in the External Roles. You can add more users and groups in the External roles (one external role per line)

If you run into an issue and can’t login, you can override to the internal authentication or reset it back again to the internal authentication, you have to perform the following steps:

  • Navigate to the following directory

  <NMC install path>\cst

  • Create a zero-byte file with the following name and with no extension

authoverride

  • Restart “EMC GST Service”
  • Now you should be able to login back in using the internal defined accounts used previously before attempting the “Configure Login Authentication” wizard

VADP backup of virtual machine fails with Unable to find the VM with VM name

VADP backup of virtual machine fails with the following error

Application information attribute VADP_VM_NAME for client “<xyz>” is set to “<xyz.nsrvalley.com>”.

Trying to connect to the VM using VM name ‘< xyz.nsrvalley.com >’.

80398:nsrvadp_save: Unable to find the VM with VM name: < xyz.nsrvalley.com >.

Temporary directory ‘c:\mnt\<xyz>’ for VADP deleted.

To Solve this issue you have to:

1- Create the Virtual Machine client instance using the actual name or DNS name.

2- DO NOT use the inventory name which is only meant for vCenter management as Inventory names are not DNS resolvable

3- In the application information attribute VADP_VM_NAME= use the Actual name/DNS Name

 Note That : VADP_VM_NAME is case-sensitive. For example, if the VM host name is upper-case (such as BEBO), the value of VADP_VM_NAME must be set to BEBO. Also, if the name entered for VADP_VM_NAME contains spaces, the name must be contained within quotation marks (for example, VADP_VM_NAME=”this is my machine”)

Exchange 2010 Backup fails with the error : A COM error occurred while validating the version of Exchange. The error code is 0x80010105. The error message is: The server threw an exception , Validation failed

Backup of Exchange 2010 server database fails with the following error:

savegrp: suppressed 24 lines of verbose output

83164:nsrsnap_vss_save:NMM .. An error was detected during the replica creation.  Details in nmm.raw on <ServerName> and in the Windows Application or System Event Log.

49931:nsrsnap_vss_save:RM .. 026671 ERROR:A COM error occurred while validating the version of Exchange. The error code is 0x80010105. The error message is: The server threw an exception..

49931:nsrsnap_vss_save:RM .. 102206 ERROR:Validation failed.

63335:nsrsnap_vss_save:NMM backup failed to complete successfully.

This error occurs because the SSL certificate for Exchange was not bound to the Default Website.

To solve this error message, perform the following procedures on the Exchange server

  1. Start IIS Manager
  2. Navigate to <Exchange-host> >> Sites >> Default Web Site
  3. Select ‘Bindings’ under Actions – Edit Site or right click ‘Default Web Site’ and do properties -> Bindings.
  4. Under Site Bindings, look for ‘https’ entry, select it and do ‘Edit’
  5. In Edit site Bindings Ensure ‘SSL certificate’ shows Microsoft Exchange (The certificate name may be different)
  6. If the https binding does not exists for Exchange, create a new binding. (One for all ‘all assigned’ IP address and one for the local host (127.0.0.1))
  7. Restart IIS.
  8. Rerun the backup.