EMC ELECT 2016

Friends I would like to share that I am elected as EMC Elect 2016 with another 70 experts from 150 finalists.

Below is the link for your reference to see the list of elected candidates

https://community.emc.com/community/connect/emc_elect/blog/2016/01/31/the-emc-elect-of-2016--the-official-list

This is a very funny incident with me about EMC elect. When I started working on EMC product and I heard from someone that there is one kind of election EMCElect. I was very surprised because I thought EMC is also conducting election like politicians  but after reading about EMC Elect I got to know that this is an honor for EMC expertise.

So that time I was very excited to grab much information about EMC Elect. I always share my knowledge regularly on EMC Community Network, sharing on Twitter too. I also started sharing my technical tips through blogs and on EMC community forum for knowledge sharing.

I was shortlisted For EMC ELECT 2013 but was not selected, and I took it as a challenge and I said to myself that next time I will take more efforts and again participate in 2014 and finally I got first EMC honor in 2014 and again in 2016.

I would like to thanks all who voted me and fulfil to complete this program.

This is unique initiative by EMC and I am really enjoying to participate year again year.

Special thanks to Mark Browne ‏@DathBrun and all known unknown people who were involved in this activity.

VSS System Writer is not found on this system

The VSS System Writer is not found on this system:

While backing up Windows 2008 and 2012 server on EMC Networker and you are getting below error, there will be many causes for this error. This is a very common permission issue.

98266:save: The VSS System Writer is not found on this system.  The backup is stopping because the System Writer is required for a successful system state backup.  Have the system administrator check the VSS infrastructure and fix the issue.

You should first try below solution:

Start or Restart below services:

1. COM+ Event System

2. COM+ System Application

3. Distributed Transactions Coordinator

4. Microsoft Software Shadow Copy Provider

5. Volume Shadow Copy service

6. Networker remote exec service

And try to take test backup, if it fails again then you should go with below Microsoft solution.

The system writer fails because permissions to files in the %windir%\winsxs\filemaps\ or %windir%\winsxs\temp\PendingRenames directories are incorrect.

Solution:

To resolve this issue, type the following commands from an elevated command prompt:

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

Type the following command to verify that the system writer is now listed: vssadmin list writers


If the system writer is missing, check the Application event log for the following event

for more info check Microsoft Technical Tips :

https://support.microsoft.com/es-ar/kb/2009272#/es-ar/kb/2009272

How to BACK UP the NetWorker Management Console (NMC)

How to BACK UP the NetWorker Management Console (NMC):

We can backup NMC through command line as well as GUI method.

First we will see the command line method:

Open the command line interface and run the command “savepsm” which will backup the NMC database. The normal Networker “save” command cannot back up NMC database successfully if it is open during backup hence it is always better to use "Savepsm" command.

Now we will see using GUI method:

Login to NMC console

Go to SETUP

Click the SETUP button on the toolbar

Select “Set Database Backup Server”

 Mention the NetWorker server name that you want to back up the NMC database.

Check "Create client resource on this server".

Set Client name to the hostname of the machine that has the NMC database.

Click OK.

After successfully configuration connect to the NetWorker server. When you look at the list of clients, you will get there a new client.

You will also see that client configuration saveset name starting with "NMCASA:/gst_on_NMC-Server-name/lgto_gst" with Backup Command attribute: savepsm (for a Windows Console server) or savepsm.sh(for a UNIX Console server).

You should verify the backup which you configured after successful first backup with mminfo command.

On Windows: mminfo -avot -s (NetWorker server) | find /i "gst"

On UNIX: mminfo -avot -s (NetWorker server) | grep -i gst

This are the method you can use to backup your NMC database.

NSR peer information' provided did not match

NSR peer information' provided did not match

nsrexecd GSS critical An authentication request from backupclient.com  was denied

If you experience errors in the backup server daemon log such as this:

89879 07/04/14 04:04:13  nsrexecd GSS critical An authentication request from backupclient.com  was denied. The 'NSR peer information' provided did not match the one stored by backupserevr. To accept this request, delete the 'NSR peer information' resource with the following attributes from backupserevr's NSRLA database: name: backupclient.com; NW instance ID: XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX; peer hostname: backupclient.com

It is because a client has been re-installed, renamed or the NSRLADB has been rebuilt.

To resolve this, delete the NSR peer information for the client on the backup server.

For example:

# nsradmin -p nsrexecd

NetWorker administration program.

Use the "help" command for help, "visual" for full-screen mode.

nsradmin> . type:NSR peer information;name:backupclient.com

Current query set

nsradmin> delete

                        type: NSR peer information;

               administrator: "isroot,host= backupserevr ",

                              "isroot,host=backupserevr.com",

                              "user=root,host=localhost";

                        name: backupclient.com;

               peer hostname: backupclient.com;

          Change certificate: ;

    certificate file to load: ;

Delete? y

deleted resource id 0.0.XX.XXX.0.0.0.XXX.83.XXX.XXX.XXX.XXX.XX.XX.11(1)

nsradmin> quit

EMC Data Domain Advanced Command Troubleshoot

EMC Backup and Recovery with Data Domain

Differences between NetWorker 9.0 and previous releases Part 1

Differences between NetWorker 9.0 and previous releases Part 1

Note : Reference by EMC Networker

This Post given comparison of NetWorker 9.0 with the previous

Major release, NetWorker 8.2.

First we are going through NetWorker installation changes: