Hi Zlatko,

this issue is usually caused by either a misconfiguration or a name resolution issue:

As far as I understand:

some.host.com= Physical host

someother.host.com= Virtual host

So in this case NMM complains that there are no devices configured for the physical and virtual hosts.

Do you have a client entry created for the physical hosts?

Here I guess you are backing up the virtual node, are you backing up file system or application?

If application, which application are you backing up?

If File system, why are you backing upi the virtual host?

Thank you.

Carlos.

CarlosRojas wrote: As far as I understand: some.host.com= Physical host someother.host.com= Virtual host

I believe he said the other way around.

I am backing up virtual host, because I want to backup shared filesystem across two physical nodes.

I configured everything, both physical nodes and virtual host in client configuration. Device on NW server is labeled and mounted.

Here is the configuration:

Group configuration:

Snapshot:  YES

Snapshot Policy:  Serverless Backup (Once a day)

Snapshot Pool:  Some_backup_pool

Client configuration:

Name:  some.host.com (virtual hostname)

Save set:  R:\  (this is shared partition)

Pool entry is empty

Schedule:  Default

Apps&Modules:

     Backup command:  nsrsnap_vss_save.exe

     Application information:  NSR_SNAP_TYPE=vss

     Avamar: Yes

Globals (2of2):

     Remote Access:  *@*

I am using NMM because I need to backup MSSQL databases (SQL 2012) also.

Thank you Zlatko,

First let's start for the beginning:

1.- Ensure that pool "Some_backup_pool" has checked the box for the group where that client is included.

2.- Ensure that there is correct Avamar storage node/devices configured for that group.

Do you have client entries created for the physical nodes as well?

Please ensure that there is only the aliases for the virtual node into the alias field of the virtual node client entry, and nothing else (no physical node alias in there)

If this is all as I said then try to add the physical nodes in that group but leave the "Scheduled backup" box unchecked otherwise you can also add the physical nodes in the same group to perform file system backup, in that case add all the physical nodes and select those as well as "scheduled backup".

Ensure the correct name resolution from NW server to the physical and virtual nodes:

nsrlookup somother.host.com

nslookup IP )given from previous nslookup)

Same for physical nodes.

Thank you.

Carlos.

You are right Hrvoje

Zlatko, regardless of my confusion we would need to know if there are client entries created for physical and virtual nodes, what you are backing up and more about the configuration of these clients.

Thank you.

Carlos.

I did everything you said, and no use. The problem is still there.

Let me explain what happened this week.

Backup of those clients were fine until this Tuesday. On Tuesday we did test BMR of the one physical host that is a member of that virtual hostname. And we put that restored server on production LAN with the same hostname as the original but with different IP address, and joined that host to the domain (by mistake!). Naturally, when we did that, we could no longer login to the original host because of the "trust relationship domain error". We rejoined to the domain the original host by issuing "netdom reset" command, and after that domain accounts were back online.

I don't know if it is related, but after this "trust relationship domain error" I can't backup only that client. Looking at that cluster environment:

first.physical.com - cannot be backed up

second.physical.com - can be backed up

some.virtual.com - cannot be backed up (because it actually points to first.physical.com)

Carlos, can you please take over SR #52968692 so you could WebEX join to my station and see what is wrong?

Hi Zlatko

Can you please let me know how you are backing up your filesystem backups using NMM i am New to NW and trying to do POC with NW

Cluster servers and non cluster SQL 2012 DB servers

I am trying to backup file systems and DB from read only side of DB for 2012 and both are failing

File systems on read only side of DB server  i am using

Saveset-All

backup command-nsrsnap_vss_save.exe

Application inofrmation -

NSR_SNAP_TYPE=VSS

NSR_IGNORE_MISSING_SYSTEM_FILES=YES

datadomian-Yes

storage node-nsrserverhost

Hi Deepu83,

Did you try configuration as I described in fourth post of this topic?

Hi Zlatko

I tried  the options specified and recommended and i am still geting these errors in File system backups

C:\: NSRSNAPCK::success

C:\: Backup of failed

1 E:\SS2K12$SQL12\DBDATA E:\SS2K12$SQL12\DBTLOG E:\ D:\SS2K12$SQL12\DBTLOG2 D:\SS2K12$SQL12\DBTLOG1 D:\SS2K12$SQL12\DBDATA1 D:\SS2K12$SQL12\DBDATA D:\SS2K12$SQL12\DBTLOG D:\ C:\

[nsrsnap.c 2060] Calling snap_wait..

[nsrsnap.c 2081] Calling parse_fs_logs_and_prefix..

86745:nsrsnap_vss_save:Version information for C:\Program Files\EMC NetWorker\nsr\bin\nsrsnap_vss_save.exe:

    Original file name: nsrsnap_vss_save.exe

    Version: 2.4.1.92

    Comments: NetWorker Module for Microsoft Applications (x64)

50423:nsrsnap_vss_save:nsrsnap_vss_save: Unknown Application Information parameter: DIRECT_ACCESS, may not be supported

50411:nsrsnap_vss_save:nsrsnap_vss_save: Data mover host name not specified. Assuming local host:xxx.com

67770:nsrsnap_vss_save:NMM .. Snapshot rollover policy. Group: "Test-OS" Snapshot Policy: "Test-OS" Rollover: "All".

88430:nsrsnap_vss_save: Checking NetWorker Privileges: User  does not have "Operate NetWorker","Backup Local Data" and "Recover Local Data" privileges on xxxx.com

63322:nsrsnap_vss_save:NMM has detected that client does not have enough permissions.

63335:nsrsnap_vss_save:NMM backup failed to complete successfully.

Internal error.

68151 1361667007 2 0 0 8324 6040 0 xxx.com nsrsnap_vss_save NSR warning 39 nsrsnap_vss_save: Exiting with failure. 0

E:\: NSRSNAPCK::success

E:\: Backup of failed

The group and client properties are as follows-

Group-

Snapshots-enabled

snapshot policy-Filesystems

snapshot pool-datadomain

Advanced tab-nothing changed from defaults in options i have manual restart

Client properties-name

backuptype-Filesystem

checpoint disabled

checkpoint granularity-directory

doirective-sql directive

client direct-disabled

group filesystems

pool-Empty

backup renamed directories-yes

apps &modules- dint give user name passowrd

backup command-nsrsnap_vss_save.exe

application informat-

NSR_SNAP_TYPE=VSS

NSR_VSS_FORCE_SYSTEM_PROVIDER=yes

datadomain=yes

storagenodes-nsrserverhost

Please let me know what i have to do to make this work.

I know this is not the really right solution to work with, but, try putting *@* in Remote Access box of Globals (2 of 2) of Client Configuration.

Hi Zlatko

I have NMM 2.4 on cluster SQL 2012 server node a ,node b and node ab(Rean only DB server)and all are physical servers

How do i configure File sytems backups for these servers?

i install NW and NMM client on all local drives of each node  configured node Ab and node B but geting this unable to connect to server on node A with unable to authenticate to server

Authentication error why=server rejected credentials.

I am admin on the server and can login and install NW clients .

Can you please let me know how to configure group and client properties for these File system backups atleast if can to DB it will be greatly appreciated.

As i am new to NW not able to configure it correctly i think. if you can let me know i will re-do them

Thank you.