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:

NetWorker 9.1: If short name for the NetWorker server is not resolved, the recently upgraded client fails with “The Index session is invalid”

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



NetWorker 9.1.1

Since updating the NetWorker client for Windows from 8.2.4.7 to 9.1.1.3 the backups are failing for the drive letters with

— Job Indications —

<SystemDrive_Letter>:: File index could not be obtained due to <Unable to do Index lookup of path ‘<SystemDrive_Letter>:’. The Index session is invalid.

>. Contents of this directory may not be properly backed up. See save man page (Command Reference Guide) for more information.

While the pseudo_saveset reports in the <Get Full Log>:

89982:save: Only one server can be specified, using the last server entry ‘<NetWorker_server_FQDN>’.

89982:save: Only one server can be specified, using the last server entry ‘<NetWorker_server_FQDN>’.

89982:save: Only one server can be specified, using the last server entry ‘<NetWorker_server_FQDN>’.

89982:save: Only one server can be specified, using the last server entry ‘<NetWorker_server_FQDN>’.

(Note: has save -s <NetWorker_server_FQDN> in the Backup command of the client resource, removed it)

98519:save: Unable to setup direct save with server <NetWorker_server_FQDN>: Failed to connect to storage node on <NetWorker_server_short_name>: Failed to connect to host ‘<NetWorker_server_short_name>’: Unknown host.

98520:save: Falling back to agent-assisted indirect save

98519:save: Unable to setup direct save with server <NetWorker_server_FQDN>: Failed to connect to storage node on <NetWorker_server_short_name>: Failed to connect to host ‘<NetWorker_server_short_name>’: Unknown host.

98520:save: Falling back to agent-assisted indirect save

98519:save: Unable to setup direct save with server <NetWorker_server_FQDN>: Failed to connect to storage node on <NetWorker_server_short_name>: Failed to connect to host ‘<NetWorker_server_short_name>’: Unknown host.

98520:save: Falling back to agent-assisted indirect save

100690:save: C:: File index could not be obtained due to <Unable to do Index lookup of path ‘C:’. The Index session is invalid.

>. Contents of this directory may not be properly backed up. See save man page (Command Reference Guide) for more information.

C:: File index could not be obtained due to <Unable to do Index lookup of path ‘C:’. The Index session is invalid.

>. Contents of this directory may not be properly backed up. See save man page (Command Reference Guide) for more information.

90096:save: save of ‘C:’ to ‘<NetWorker_server_FQDN>’ failed: Can’t encode arguments

99123:save: Handling an abort while processing Windows backup.

90097:save: ASR Backup: aborting VSS volume save because Quit flag is set.

100690:save: E:: File index could not be obtained due to <Unable to do Index lookup of path ‘E:’. The Index session is invalid.

>. Contents of this directory may not be properly backed up. See save man page (Command Reference Guide) for more information.

E:: File index could not be obtained due to <Unable to do Index lookup of path ‘E:’. The Index session is invalid.

>. Contents of this directory may not be properly backed up. See save man page (Command Reference Guide) for more information.

90096:save: save of ‘E:’ to ‘<NetWorker_server_FQDN>’ failed: Can’t encode arguments

99123:save: Handling an abort while processing Windows backup.

90097:save: ASR Backup: aborting VSS volume save because Quit flag is set.

<NetWorker_client_FQDN>: C: level=incr, 11 GB 00:00:32 18730576 files

Completed savetime=1501793780

90014:save: The backup of VSS emit save set ‘C:’ failed.

100129:save: Unable to update job with id ‘0’ with name value ‘C:’: Invalid or NULL session channel

<NetWorker_client_FQDN>: E: level=incr, 11 GB 00:00:43 18927024 files

Completed savetime=1501793781

90014:save: The backup of VSS emit save set ‘E:’ failed.

100129:save: Unable to update job with id ‘0’ with name value ‘E:’: Invalid or NULL session channel

<NetWorker_client_FQDN>: \?VOLUME{36F43974-F22F-11E5-9606-806E6F6E6963} level=incr, 14 MB 00:00:58 65 files

Completed savetime=1501793779

90015:save: The backup of VSS emit save set ‘\?VOLUME{36F43974-F22F-11E5-9606-806E6F6E6963}’ succeeded.

94694:save: The backup of save set ‘\?VOLUME{36F43974-F22F-11E5-9606-806E6F6E6963}’ succeeded.

99123:save: Handling an abort while processing Windows backup.

90117:save: Unable to perform the ASR backup: cannot obtain the VSS MBS status.

86024:save: Error occured while saving disaster recovery save sets.


The passages are from
NMC ->

Monitoring ->

the Workflow’s Show details … ->

Workflow runs click the failed occurrence ->

Workflow actions click the failed occurrence ->

“Show Details” ->

Failed: backups at the bottom of the “Details” pane.

The NetWorker client’s nor the NetWorker server’s short names are resolvable

Add entries for the respective hosts into their etc hosts files.

Related:

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:

OCR don’t work (15.1)

I need a solution

Guys,i need help.

I installed the OCR server on a separate stand.
I used these instructions here:

https://help.symantec.com/cs/DLP15.0/DLP/v12276019…
https://help.symantec.com/cs/DLP15.0/DLP/v12276019…
https://support.symantec.com/en_US/article.doc1061…

Server OCR – windows server 2008 r2 (4 Vcore, 8Gb ram)
Enforce –
windows server 2008 r2
Endpoint -windows server 2008 r2

Problem –
There are no incidents on the OCR server. But other servers (Endpoint and Discover) create incidents.
Images created by me are not scanned
I installed OCR on a separate server and installed an env along with Endpoint and Discover.
As if there is no connection between Enforce and OCR. But ping and telnet “on”.

What could be the problem?
What did I do wrong?

0

Related:

How to run an on-demand backup of the VM residing under the “containerclients” domain using CLI.

I want to run an on-demand backup of the VM under the domain “containerclients” using CLI. It keeps on giving me error client is not a member of the group.

admin@Backupserver:~/>: mccli client backup-group-dataset –name=”/VCenter/ContainerClients/VMClient” –group-name= “/VCenter/VMwareBackupGroup”

1,22241,Client is not a member of group.

admin@Backupserver:~/>:



Where as i can run it from GUI by selecting the VM seperately and while starting the backup it asks for Groupname in which the Container folder is added. So it seems it can collect the information from GUI but not from CLI.

I do not want to run it by adding the client into some temporary group. I want to know how to run it directly as we run on-demand backup for an agent based client, as it is possible from GUI

Related:

LiveUpdate Administrator with SEPM

I need a solution

Hi all,

I’m working on a new implemenation of SEPM (14.0.1) along with SEP 14.0 (14.0.3897.1101).

I am unable to allow the SEPM server to connect to Symantec LiveUpdate due to network restrictions so I’ve implemented an LAU server with the hop i could use it to download the required updatees and then use SEPM to distribute them to the clients.

I thought we had this working in that the LAU server is able to download the content and I seem to be able to configure SEPM to download them from LAU by configuring the site LiveUpdate settings to Use a specified internal LiveUpdate server and (after some experimentation) using the URL http://IP OF LAU:7070/clu-prod. I have LAU setup to not require and testing and once I run distibution the downloaedd content ends up in that folder… all good…

However when I run Download LiveUpdate Content I get a screen full of No updates found for…. messages, in the last few days of working on this issue (the system is currently in our Test/Dev enviroment not live) I have had the system download a few files but it isnt consistent and if I alter the settigns I get Error-4 so I’m fairly certain I am accessing the folder.

I’d hoped this wa just an issue with the the products I had LUA setup for but I’m now not sure thats the issue, my clients are all running a 32Bit version of the above on Windows 7, these are locked down devices so there is little variation, I  have tried a couple of products:-

Symantec Endpoint Protection 14.0 (english only)

Symantec Endpoint Protection 14.0 RU1 (english only) although I noted that this version is later described as Advanced Endpoint protection ?

I’m also a little concerned that in all the efforts to get this working i have soemthing out of synch as on the home screen the Latest on Manager is showing 17/09/2018 despite me having cleared out the downloaded files a number of times, is theer a way to intitalise the system without tearing it down and deleting the SQL DB ?

Any help or suggestiuons greatly appreciatyed 🙂

0

Related:

Re: Problems with EMC Networker 9.2 and Hyper-V

Hello,

I am running EMC Networker 9.2 and am constantly having trouble when running Hyper-V backups.

My topology is as follows:

– storage node FC attached to DD, using DD Boost

– Hyper-V standalone cluster that I wish to back up to the SN above

Although the DD is accessible only over FC, all other Standalone Hyper-V servers have client direct and block based backups enabled.

When I try enabling Client Direct and block based backups for the my new Hyper-V server, I get the error below

Unable to perform backup for save-set ID ” with DIRECT_ACCESS=Yes, check device and pool configuration to enable Client direct



Filesystem backups run just fine with Client Direct disabled, but I am not able to make Hyper-V backups complete successfully with Client Direct enabled or disabled.

I am also certain that the policy is correctly configured and that there is end to end connectivity between client, SN and server.

Please advise.

Thanks,

Bogdan

Related:

Data Protection Advisor (DPA) authentication for the web published scheduled reports is disabled[1]

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



Data Protection Advisor,Data Protection Advisor Family

Data Protection Advisor (DPA) authentication for the web published scheduled reports has been disabled.

Some customers have a need to access DPA reports via a Web style interface. In DPA 5 a Web Server, acting as Report Portal was available,and could be accessed without a password.

This functionally has been removed from DPA 6. The Web Server component is a security vulnerability that requires near constant patching, fixing newly developed exploitation approaches. In addition, the strategic role of DPA is not to be the Report Portal, rather to publish reports to destinations, such as other portals, as required. For these reasons the portal was removed from the DPA.

Reports produced by DPA can continue to be accessed via a web server, if a web server is configured correctly. This would be the customer’s responsibility.

In DPA 6 functionality was added to publish to Microsoft Sharepoint 2013. This purpose of this was to eliminate the need for a web server. This would be a better option to consider. Details on publishing to MS Sharepoint can be found in the DPA internal help and DPA Installation and Administration Guide. Please contact EMC Technical Support for further details or information.

Please contact Dell EMC Technical Support for further details or information.

Related:

Avamar: ‘max-streams’ parameter is being exceeded during the backup Window

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



Avamar Client,Avamar Server,Avamar Server 7.4.0-242,Avamar Server 7.3.1-125,Avamar Server 7.3.0-233

DDOS VERSION=Data Domain OS 6.0.1.0-556307

The Configurable ‘max-streams’ setting in the Avamar Admin GUI is currently set to ’80’, however just about on a nightly basis we consistently see the number of Backup jobs exceed 120+.

  • All backups jobs have the Data Domain as the ‘Target’.
  • The DDR Stream Management flag in the ‘mcserver.xml’ file is Enabled.
    • <entry key=”ddr_stream_management_enabled” value=”true” />
  • There are multiple streams enabled on SQL and Exchange backups and the ‘Activity Monitor’ tab reports 120+ backups are actually running and when checking the ‘Server Activity’ tab, it shows over 200 parallel streams.

The plugin for Exchange and SQL server has the ability to run multiple streams in parallel. That means there is only one work-order (one backup running), but the backup could run several avtar processes to connect to DataDomain. That is why the streams on ‘Server Activity’ shows double than the backups.

The MC only counts the DD streams by each work-order. It doesn’t know how many streams are running for each individual backup job.

Currently, to control the number of backup’s running and not exceed the ‘max-streams’ parameter – reduce the ‘max-streams’ setting to below your desired value as this will limit the number of jobs.

The permanent fix will be included in Avamar 7.5.1.

Related: