Saturday, November 26, 2016

RPC error: RPC program or version mismatch

We have looking today for RPC error: RPC program or version mismatch

There is a mismatch between the version of the Remote Procedure Call (RPC) service requested by the client and the service available on the server. 

This problem might be the result of an incorrect "Name to Address" resolution. 

There is a mismatch between the version of the RPC service used by the License Manager (lgtolmd) and the services available on the server. The default RPC version for lgtolmd is two.

Use rpcinfo to verify that the server and the clients are running the same version of RPC. For operating systems without the rpcinfo utility, it is provided on the EMC product CD.

Update the NetWorker software on the client or server.

Verify that the "Name to Address" resolution is correct. Test by running nslookup using the fully qualified domain name of the computer. On Windows systems, this verification also can be performed from the Network control panel.

Specify the same version of RPC for lgtolmd that is used by the other backup services on the backup server. This can be specified by either:

Entering the following command at the command line:

# lgtolic -s hostname:rpc_number:rpc_version


Setting the LMD_VERSION environment variable.

Monday, October 31, 2016

Networker backup group hung and unable to stop by GUI

Networker backup group hung and unable to stop by GUI

Error: "Group must be started either automatically or from the GUI and must be currently running in order to be stopped"

You can handle this scenario in two ways.


  •         You can kill the job PID by command line (make sure not PPID, read differenbetween PID and PPID)


  •                Another way is, use to savegrp command.


                  bash-$ savegrp -pvvv groupname

Make sure use first savegrp option if not resolved then you can use kill PID option

Thursday, September 8, 2016

EMC NetWorker backup logs files paths and details for Windows

Hi,

Today here I would like to provide details of the log files available on a Windows Networker server and log
file management.

Windows Networker Server Log Files:-







Windows NMC Server Log files:




Windows Networker client Log Files:-





There is two types of logs files:

*.log >> It is plan text file and human readable
*.raw>> It is not human readable format


You can view manually raw files with help of nsr_render_log Networker command.
You can also set it in runtime with help of nsradmin and "update runtime rendered log" Networker configuration commands.

The nsr_render_log send the output result to stdout

You can also rollover the files by time and size with help of below commands:

nsradmin
update runtime rollover by time
update runtime rollover by size


Thanks



Tuesday, August 30, 2016

EMC NetWorker backup logs files paths and details for Unix/Linux

Hi,

Today here I would like to provide details of the log files available on a Unix Net-worker server and log
file management.

Networker Server Log Files:-




Networker Server Log Files:-


Networker Client Log files:-



There is two types of logs files:


*.log >> It is plan text file and human readable
*.raw>> It is not human readable format


You can view manually raw files with help of nsr_render_log Networker command.
You can also set it in runtime with help of nsradmin and "update runtime rendered log" Networker configuration commands.


The nsr_render_log send the output result to stdout


You can also rollover the files by time and size with help of below commands:


nsradmin
update runtime rollover by time
update runtime rollover by size


Thanks

Thursday, June 30, 2016

How to Delete VBA Node in Networker

How to Delete VBA Node in Networker

Networker Ver: 8 to 9

If you want to remove VBA node entirely and delete it's backups from Networker server. The VBA node is online and responding to request from Networker server. Before Doing anything please consult with EMC Support for Assistance because VBA Node delete/remove is not recommended by EMC as a troubleshooting step.

Before starting any critical configuration you should take first backup of nsrdb and mm directories (Particular directory which related with that configuration)

Connect to Networker backup server and open the following directory

 <networker-install>\nsr

e.g   
·         Unix: /nsr/ 
·         Windows C:\Program Files\EMC NetWorker)

Make a copy of the following directories:

res\nsrdb
res\mm

After successfully copied mentioned directories you can start your actual configuration.

Remove all save sets for the client-id for this VBA node

List the Saveset:

mminfo  –c  <vba-name>  -kot

Remove Saveset:

nsrmm -d -S <SSID>

If the VBA is NOT online, then use the -X option to delete the Save set:

nsrmm -X -d -S <SSID>

Remove all workflows associated with the VBA and Delete VBA Mtree

Using GUI (NMC):

1. Login to NMC

2. Go to Configuration tab and click VMware Protection Policies

3. Sort the policies by VBA List

4. Open the first policy that has this VBA listed, go to VMware Backup Appliance Selection      tab and uncheck the VBA name.

5. Wait for the State column to change to Success


Using CLI (nsradmin):

nsradmin> p type: nsr hypervisor; name: <vcenter-name>
nsradmin> Delete

Remove VBA server resource using nsradmin

 d type: NSR VBA Server; name: <vba>

Note: This step may need to be done using offline nsradmin if VBA is NOT responding

Delete the VBA Appliance Delete the relevant VBA node VM from the vCenter server

On the NetWorker server, run nsradmin command utility to find the VBA DPN ID:

nsradmin> show name

nsradmin> show DPN ID

nsradmin> p type: nsr vba server; name: VBA-FQDN

To delete the storage unit on Data Domain:

Login to Data Domain as Admin and run command,

ddboost storage-unit delete <storage-unit>

Clean file system if required using command, filesys clean start


If the External proxy is no longer needed delete the external proxy virtual machine

Tuesday, May 31, 2016

How to check validcopies in NetWorker 9 with mminfo

How to check validcopies in NetWorker 9 with mminfo:

In your backup environment data clone going to a disk media, I suspect that we are rarely will see a save set with clflg mminfo attributes. The reason is that 'faulty/aborted' save sets will automatically be deleted.

If you want to know whether a save set has successfully been cloned you better check with 'validcopies' mminfo attribute:


mminfo -r "client,name,ssid,validcopies,pool"

or to verify all save sets with only one copy

mminfo -q "validcopies<2" -r "client,name,ssid,validcopies,pool"

Thursday, March 31, 2016

Browse and retention time raised Script for multiple SSID

Today I would like to explain How Browse and retention time period extend by Script for multiple SSID

bash-$ mminfo -avot -q "savetime>=02/01/2016,savetime<=03/31/2016" -r client,ssid,group,ssbrowse,ssretent >ssid.txt 2>&1

Select the respective SSID which need to extend and put in to one text file ssid-re.txt. After that run the below script for extend the Browse and retention period;

Today Date : 04/01/2016

bash-$ for i in `cat ssid-re.txt`; do sudo nsrmm -S $i -e "6 months" -y; done

bash-$ for i in `cat ssid-re.txt`; do sudo nsrmm -S $i -w "6 months" -y; done

You will get the error browse time should be less than retention time.

You should mention commands like as 

for i in `cat ssid-re.txt`; do sudo nsrmm -S $i -w "Sun Feb 28 06:16:05 2016" -y; done

After extended the both policy verify it.

for i in `cat verifyssid.txt`; do mminfo -q ssid=$i -r 'client,ssid,sscreate,ssbrowse,ssretent' >>output.txt; done 

Sunday, February 7, 2016

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




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.

Tuesday, February 2, 2016

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




Monday, January 4, 2016

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.

How to configure the Avamar Event notifications

Today we are go through with how to configure Avamar alert Notification :- A.       Log into the Avamar Server using the Avamar Admini...