NetWorker NMMA 2.3 Filesystem Backup Error

Question

Hi All, After troubleshooting a while i thought it´s time to ask somebody for help, as i do not find any solution for my issue. We have a mulithomed NIC Environment and we are trying to run a Filesystem Backup with NMMA 2.3 latest release. After the backup runs a while we get the following errormessage: 64037 16.03.2012 10:52:35  1 0 0 3676 2076 0 client.backup.domain nsrsnap_vss_save NMM .. Create NetWorker backup of snapshot using PS backup service. 63929 16.03.2012 10:52:35  1 0 0 3676 2076 0 client.backup.domain nsrsnap_vss_save NMM .. Setting backup level to full for 'C:\' because no NetWorker VSS backup found for last backup time of '1331891301'. 64360 16.03.2012 10:52:35  1 0 0 3676 2076 0 client.backup.domain nsrsnap_vss_save NMM .. Starting Backup. This operation may take a long time depending on the size of the data requested. 82296 16.03.2012 10:53:05  5 0 0 3676 2076 0 client.backup.domain nsrsnap_vss_save NMM .. Operation unit failed with error 'Please make sure you have configured at least one NetWorker Device and client resources are configured for the application host[client.backup.domain] and the proxy client[client.backup.domain] on NetWorker Server [networker.backup.domain]'.Possible cause: 1)Unsupported file system or 2)write-protected disc or 3)No space on disc or 4)Drive not found 63911 16.03.2012 10:53:05  1 0 0 3676 2076 0 client.backup.domain nsrsnap_vss_save NMM .. Error backing up one or more of the file system savesets: NMM .. Operation unit failed with error Please make sure you have configured at least one NetWorker Device and client resources are configured for the application host[client.backup.domain] and the proxy client[client.backup.domain] on NetWorker Server [networker.backup.domain]. 64038 16.03.2012 10:53:05  5 0 0 3676 2076 0 client.backup.domain nsrsnap_vss_save NMM .. Error creating NetWorker backup of snapshot: NMM .. Operation unit failed with error Please make sure you have configured at least one NetWorker Device and client resources are configured for the application host[client.backup.domain] and the proxy client[client.backup.domain] on NetWorker Server [networker.backup.domain]. 63372 16.03.2012 10:53:18  5 0 0 3676 2076 0 client.backup.domain nsrsnap_vss_save NMM .. Registration of snapshot set failed -- NMM .. Operation unit failed with error Please make sure you have configured at least one NetWorker Device and client resources are configured for the application host[client.backup.domain] and the proxy client[client.backup.domain] on NetWorker Server [networker.backup.domain] 77175 16.03.2012 10:53:22  1 0 0 3676 2076 0 client.backup.domain nsrsnap_vss_save NMM ..  completed commit replica with status of false. 63335 16.03.2012 10:53:23  5 0 0 3676 2076 0 client.backup.domain nsrsnap_vss_save NMM backup failed to complete successfully. 50404 16.03.2012 10:53:23  0 0 0 3676 2076 0 client.backup.domain nsrsnap_vss_save nsrsnap_vss_save: createInstanceBackup() failed 0 16.03.2012 10:53:23  2 0 0 3676 2076 0 client.backup.domain nsrsnap_vss_save nsrsnap_vss_save: C:\: failed 63309 16.03.2012 10:53:23  1 0 0 3676 2076 0 client.backup.domain nsrsnap_vss_save NMM .. bye bye. 68151 16.03.2012 10:53:23  2 0 0 3676 2076 0 client.backup.domain nsrsnap_vss_save nsrsnap_vss_save: Exiting with failure. The NetWorker Client entry has been made with FQDN of the backupdomain and the normal Client with shortname and FQDN has been added to the Aliases field. The NIC ordering on the Server is: Production-LAN Test-LAN Backup-LAN Any help would be greatly appreciatet. Thanks and regards, Andreas

Bebo2k · Accepted Answer

Hi Schallean,

These error messages indicates either a problem with name resolution or a wrong configuration of the client entries in NetWorker server.

Please ensure that:

- The client resource in the NMC is created by FQDN.

- Ensure all aliases for the client included in the Alias field in the client configuration, including short name, FQDN (upper case and lower case of both as well).

- Backup server is able to resolve the names properly for the client using ping, nslookup and rpcinfo commands as well as from the client to the backup server. (Ensure that configuration and name resolutions works fine for the backup network Interface Backup-LAN).

- Make sure you selected that group checked in the Selection criteria field in the pool configuration or the pool is correctly configured in the group configurations.

Hope this helps you to resolve this issue.

Thanks,

Ahmed Bahaa

Lucky85 · Answer

Sounds like problem with pools configuration… Regards Lukas

Bebo2k · Answer

Additionally , Make sure that the Backup Server and client System time (Clock) are synced; the difference should not be more than few minutes. Thanks, Ahmed Bahaa

CarlosRojas · Answer

Hi Andreas,

This is a very common issue, and these are the most common causes:

1.- Name resolution issue.

2.- Pool configuration issue.

3.- Firewall blocking connection

4.- Duplicated client ID in NW MDB

So first of all check the names that appear in the error message and ensure the proper name resolution through the correct network interface.

Then ensure the pool configuration is correct.

If that doesn't help there is a big chance that you have a duplicated client ID in the NetWorker server MDB (Media DB). For that I would recommend you to open a case with support.

Thank you.

Carlos.

schallean · Answer

Hi All,

The issues has been solved. We were facing big issues with the name resolution, where the DNS returned wrong ip adresses and sometimes hostnames. After fixing these Issues we are able to run Backups without any issue.

Thanks to all for support.

Regards,

Andreas

NetWorker

Was this post helpful?