Is smtpmail distributed as standard with Networker? (specifically 7.6.2.1)

Bit of an odd scenario, so apologies in advance!

I’m investigating one of our servers which has a few scheduled tasks running on it, attempting to make use of a ‘smtpmail.exe’. The only reference to any smtpmail executable I could find with the same argument syntax, is the one in EMC networker (as seen in this thread), and there just happens to be an installation of EMC networker on this particular server, with the ‘Legato/nsr/bin’ directory in the PATH. Which seems a pretty good indicator that the intention was for these tasks to be using smtpmail from networker.

However, there is no smtpmail executable in the bin directory, and never having heard of EMC networker until today, I don’t know if it’s something that is actually part of EMC networker and has somehow been removed from this particular installation, or it’s something non-standard and the above thread is just a bit of a red-herring.

Thanks in advance for any insights!

Related:

  • No Related Posts

Unable to restore VM from tape device

Hi folks,

I am trying to do a comlete VM restore from a backup created via the vProxy. The Save Set was written to a Data Domain and later cloned to a tape device. The tape shall be the source for the restore.

I am on NetWorker v18.1 on a Windows Server 2012 R2. Tape Library is a TS4300 with LTO8 drives connected via SAN to the NetWorker Server (physical). There is no additional Storage Node.

So I started the recovery wizard within the NMC and selected everything I needed. At the last page I selected the tape as source and did choose my one and only Data Domain pool as staging pool.

After a few seconds I got the failure:

155752:nsrvproxy_recover: Unable to find a usable device for recovery of saveset 3976587711: Unable to find enabled Data Domain device for volume ‘000061L8’. An attempt will be made to perform automatic clone resurrection

165713:nsrvproxy_recover: Attempting to automatically resurrect clone 3976587711 with 7 days retention to DD volume in pool DATA



I searched the web and support.emc.com without any success. There were two KBs. One mentioned to check DNS which is correct. The second one suggested to mount a boost device from the selected pool which I checked.

Has anyone an advice?

Thanks

beacon

Related:

  • No Related Posts

Re: Troubles with NDMP-DSA Backup NW9.1.1 & NetApp Filer over dedicated Interface

Hello,

Networker Server 9.1.1

Stroage Nodes 9.1.1 with RemoteDevice DD for NDMP-Backups

We added storage nodes to our environment that got a direct 10G Ethernet connection to the NetApp Filers. There is one interface connected to the production network and one interface that is directly connected to the NetApp Filer with a private network address of 10.11.11.12.

NetApp Filer is configured with IP address 10.11.11.11.

We used the wizard to configure the NDMP-DSA Backup. Client Direct is disabled.

Backup command: nsrndmp_save -M -P <StorageNode> -T dump

Additional Information:

BUTYPE=dump

DIRECT=Y

HIST=Y

EXTRACT_ACL=y

UPDATE=Y

USE_TBB_IF_AVAILABLE=Y

In this above configuration backups work and move data over the production network.

Our goal is to use the direct connection to optimize backup. Therefor we added the hostname for the storage node with the private ip address on the netapp filer but the backups still moved over the production network.

In the next step we defined a “virtual” hostname of storagenode-fs with IP 10.11.11.12 and edited the Backupcommand to use P storagenode-fs but this did not work either.

Anyone got some ideas on this situation?

Regards,

Patric

Related:

Re: v-Subscription with ODL query

Hallo Kate Hutchinson

Thanks a lot. Your response has helped me.

I would like your advice. I’m planning to buy a subscription (It is individual not company). The primary reason I wish to purchase this subscription to learn the following products

1. EMC Networker

2. VXRail

3. Data Domain

In all three products, I’m looking for a training. E-learning do not fit my requirements.

Can you help me find that Video ILT for all the above three products is covered by v-Subscription?

Related:

  • No Related Posts

Storage Node Network connectivity to Datadomain best practices

I am looking for some advise on the best practices on connecting networker storage nodes in a environment where clients are having backup IP’s in several different VLAN’s . So basically our storage nodes will contact NDMP clients over their backup networker in layer-2 on diff vlans and need send the backup data to data domain on separate vlan.

To depict this here is how we are currently backing up

NDMPClient1-Backup-vlan1———->Storage Node-Backup-Vlan1( Vlan5)———->DataDomain over Vlan5

NDMPClient2-Backup-vlan2———->Storage Node-Backup-Vlan2( Vlan5)———->DataDomain over Vlan5

NDMPClient3-Backup-vlan3 ———->Storage Node-Backup-Vlan3( Vlan5)———->DataDomain over Vlan5

NDMPClient4-Backup-vlan4 ———->Storage Node-Backup-Vlan4( Vlan5)———->DataDomain over Vlan5

So for every NDMP client backup vlan we defined and interface on storage nodes in the same Vlan.

And from Storage node to Datadomain connectivity we have a seperate backup vlan in layer-2

Since this is a 3 way NDMP backp , the traffic flows from clients to Storage nodes in one network and from storage nodes to Dataomdin in a different paths.

is this is a good model or do we have any other model that we can adopt to have better backup/restore performances.

Thanks in advance

Related:

  • No Related Posts

Re: “save …” command doesn’t reach the client

Backup (file level) on one of the nodes in a SQL cluster is not running.

Networker Server V9.1.1.3.Build.189

Windows Server 2012 Std.

NW client –> 9.1.1.9.Build.394 (also tested 9.1.1.7)

############## another environment with the same issue #############

Windows Server 2016 Std.

NW client –> 9.1.1.9.Build.394

####################################################################


A try to backup C: ends in a time out of pseudo saveset (30 min).

There are no Problems on another MS SQL HAG node, same config.

The backup was runnning before. The communication (IP, port, firewall ect.) is given, checked with tcpdump many times.

DNS is correct for server, client, storage node and data domain. Also checked, many times between the components.


The NIC on both nodes in the cluster has multiple IPv4 addresses.


Already reinstalled the client (incl. deleting …EMC NEtworker) and updated the NSR Peer Information.

The server entry in the servers file is set.

There are no log entries regarding errors or warnings on the server, even in the daemon.raw on the client.

Only with the command “dbgcommand -p PID D=9” on the client I can see more in the daemon.raw, but no errors as well.


Networker checks the backup by savefs (successully) and that’s all. The real “save …” command doesn’t raech the client.

I can start the backup from the client by the “NetWorker User”, it’s running.

Also, I can start the backup by copying the “save …” command from NMC action log.

In both cases the backup is running successfully.

I’ve checked everything … no ideas anymore

Related:

DPA: Networker Job Monitor collection requests time out.

Article Number: 480723 Article Version: 3 Article Type: Break Fix



Data Protection Advisor,Data Protection Advisor Family

Networker Job Monitor collection requests “jobquery” command returns a timeout and may have high CPU when data collection is running.

The Networker application failed to respond within the timeout configured.

Timeout values for job monitor can be increased in DPA as detailed in DPA KB 462807

NetWorker Job Monitor request fails with “Timeout from worker process while running request networker:jobmonitor”

https://support.emc.com/kb/462807

Increasing the timeout as described in the KB for the collection request may help in some cases but not all.

If increasing the timeout does not help, the specific command the agent runs that times out can be identified by review of the DPA module test log.

A backup Administrator can run the command directly on the backup application. If a timeout is returned when run outside of DPA the issue can be investigated by Networker support. The issue may be with the format of the command or some problem with the backup application. Networker Support can offer guidance on this.

Related:

  • No Related Posts

DPA: Data collection for NetWorker Server fails, “Error running jobquery against”

Article Number: 485562 Article Version: 4 Article Type: Break Fix



Data Protection Advisor 6.3,NetWorker 9.0.1,NetWorker 9.0.50

Data collection for the NetWorker job monitor is failing with the error:

Error running jobquery against the server
User-added image

Within the dpaagent.log the following errors are seen as well:

com.base.os – cfindpath(): couldn’t find file jobquery.exe

com.base.runcmd – csystemopen(): cannot find jobquery.exe in path

agent.mod.nsr – nsrRunQuery(): error running jobquery against server “NetWorker_Server

When NetWorker 9 is monitored using local agent all the required binaries will be present.

But if monitoring NetWorker 9 from a remote agent that is either by App Server or Datastore Server or Proxy Server, having the NetWorker 9 client binary is not enough for the data collection to run.

In NetWorker 9 the client no longer contains the jobquery binary, which is required by the DPA agent.

NetWorker Client or Extended Client was not installed or incorrect version was installed or the NetWorker binaries where damaged/missing on the DPA Remote Agent server.

NetWorker server was upgraded from 8.x to 9.0.x.

Install the NetWorker Extended Client package on the remote agent and restart the DPA agent service.

Check the data collection of NetWorker and it should start to work fine. If the issue still presents, contact EMC Technical Support for assistance.

DPA is able to monitor NetWorker 9.x either from an Agent running on the backup server or remotely using an Agent running on the DPA Server or any other remote computer in the environment. If monitoring NetWorker 9.x remotely the NetWorker 9.x Client and Extended Client packages must be installed on the agent system.

The NetWorker Data Collection requests uses commands such as jobquery and nsradmin to communicate with the NetWorker server which are included in the NetWorker Client and Extended Client packages. These requirements are documented in the DPA Installation and Administration Guide:

If you are monitoring NetWorker 9.0.0.4 and later remotely, install NetWorker Client and NetWorker Extended Client. The NetWorker 9 Client and Extended Client must be installed on the DPA Agent host. If you have a previous version of the NetWorker Client, then you need to upgrade. If you are monitoring older versions of NetWorker, use the NetWorker 9 Client and Extended Client to monitor those other versions if the DPA Agent is used to also monitor a NetWorker 9 Server.

Related:

Re: Help on how to backup the media database and client indexes to a single tape for DR purposes

I’m running networker version v8.2.4 on a windows server 2008 R2. Our external DR environment has the same physical infrastructure and also same OS version and same hostnames for clients and the networker server.

Does this DR site have the same networking setup?

If your production environment depend on DNS for name resolution, are the DR’s DNS servers all populated with the same host info as the production server?

If the DR’s DNS is not setup, does each of the DR NetWorker hosts all have their local host file populated with the needed hosts and ip. addresses?

Many people performing DR tests has encountered seeing the NetWorker server starting up the NetWorker server application very slow or even appear hung because host name lookup was not defined at the DR site. The lookup happens because when nsrd is started, it reads the nsrdb database, and then afterwards when nsrmmdbd opens and reads the media database. In both cases, essentially, if it finds a hostname (or FQDN), it will perform a name lookup for its IP address. And if it fails, it will retry a few times before finally giving up.

This behavior can also happen in production sites if the name lookup service is unavailable when NetWorker server is started.

The more hosts that are not resolvable, the longer the NetWorker server startup will take.

During previous DR testings on this external environment, we were using the scanner command to scan the tapes and rebuild the media database and indexes, but this is taking 2 days or more to complete.



In a pure DR scenario, after installing NetWorker in the DR server, you need to locate the volume that has the most recent NetWorker bootstrap backup. And if you have the ssid of that most recent bootstrap, then even better. With that, then all you have to do is to create the NetWorker device that can read that volume, put that volume into that device, and (prior to nw 9) run mmrecov. After that, you stop nw, make an online backup copy of res.R and mm, replace res with res.R, then restart NetWorker and complete the recovery. Note: after the recovery is complete, you should also scan that same bootstrap tape.

If you only know the volume that has the most recent bootstrap, then load the tape and use “scanner -m” so that it can catalog the tape. “mminfo -avot (volume)” will then tell you what is on the tape, and you can then find the bootstrap info from that output.

If you do not know which volume has the most recent bootstrap, then unfortunately you will need to scan each volume until you locate it. You should only need to scan tapes until the bootstrap is located.

After the bootstrap is recovered, you can then recover some or all of the client file index using: “nsrck -L7”.

EMC Networker Disaster Recovery Guide suggests I should backup the media database and client indexes to a single tape…

Ideally that would be convenient for DR purposes, so that all you would need is minimal set of tapes to recall for recovery. This can be achieved by creating a pool to store index and bootstrap backups. To create a set of volumes that will contain the bootstrap and index:

– label a new tape with the pool you will use to hold the bootstrap

– load that new tape so that new tape will be used

– create a NetWorker Group that has all the clients that you want to backup their client file indexes. Or just add the clients used for the DR testing.

– backup the bootstrap and indexes with: savegrp -O -l full -b (pool) (Group)

The “savegrp -O” will backup the client file index databases first before finally backing up the bootstrap.

In a pure DR scenario, you would need to rebuild your NetWorker server, and possibly your networking infrastructure. For your DR testing, I would recommend creating a text file containing all the hostnames and ip’s in your NetWorker environment. Save that file to a memory stick, and bring it along to the DR site.

Related:

  • No Related Posts

Re: NetWorker 9.2.1.5 global directive problems

Hi there,

we’ve got a fresh installed NetWorker 9.2.1.5 environment running on CentOS 7.5 Linux. We have five database servers running Oracle 10g on it. The database files are stored in the following folders:

Server 1 => /oracle1

Server 2 => /oracle2

Server 5 => /oracle5

For the database backup we’re using the NMDA Module so we have this and the NetWorker client software (9.2.1.5) installed on this systems (CentOS 5.11). I want to do a file system backup for this systems as well and don’t want to save the oracle folders because they are very big. I decided to create a directive that looks as follows (due to NetWorker Admin Guide):

<< */oracle[1-5] >>

+skip: *

In the client setup I chose this directive for each client and set the save set to All.

When I start the Workflow for this group the backup action monitor shows the following save sets:

Server 1:

/

/boot

/oracle1

Server 2:

/

/boot

/oracle2

and so on…

It seems, that the directive is not working. I can’t find anything in the logs that says the client tries to use the directive.

I also created a directive for each client because I wasn’t sure about the new wildcard syntax for the folders:

<< /oracle1 >>

+skip: *

Can someone please help me with this?

Regards

Hendrik

Related:

  • No Related Posts