DB2 backup Failure

If you want anyone to make useful comments, it would be better to actually state what we are dealing with here? As only an error message without any context makes it rather difficult to assess...

Scheduled backup? Initiated from client end? What are the settings used? Was it ever working before or is this a new setup? NW version NW NMDA module version?

The error in and by istelf seems to suggest that the node name is empyt ("")?

https://www.ibm.com/docs/en/db2/11.5?topic=messages-sql1000-sql1249 :

SQL1001N name is not a valid database name.


User response

Resubmit the command with the correct database name.

@bbeckers1​ .

It is new configuration 

Configured manually not thorugh wizard.

NW version:193.

NMDA:19.4

Node name wrong means where it is mentioned wrong

@Brahmaiah E​ so it would help actually telling what and how you have configured the NMDA DB2 backup configuration?

Also does it work when performing the backup manually from client end? This as DB2 redo log backups need to be triggered from client end anyways as they cannot be scheduled from NW server end. So some cleint end configuration is needed anyways. Ideally by having a separate config for the DB2 redo log backups versus the ones for the DB2 backup, for example to be able to use different backup pools (as we always want to have regular DB backups separated from the redo log backups, which is still a leftover from our tape days, to prevent that all data might end up on the same tape).

This however would require needing to know how to setup the configuration on client end? You went through the NW NMDA manual for that?

We tend not to use the wizard ourselves as then the backup team would need to know (and not down in case of needing to change the settings) the credentials for the DB to be input into the wizard, while when setting things up manually, then this is not required.

for example reference KB https://www.dell.com/support/kbdoc/en-us/000021161?lang=en "NetWorker: NMDA DB2 Triage Guide".

https://www.dell.com/support/kbdoc/en-us/000128033?lang=en "NetWorker: Log files to collect for NetWorker Module for DB2 backup issues".

So with scheduled backup approach not using the wizard, using the sample template file nmda_db2.cfg as reference.

https://www.dell.com/support/manuals/en-us/networker-module-for-databases-and-applications/nw_p_nmda_admin/nmda-configuration-file?guid=guid-fa98755e-7ad5-4666-8f16-a540e7d4961c&lang=en-us

Having a config file on client end, also might help to solve scheduled backup issues, as one can test what happends when running the backup from client end. Technically one might not wanna use the same config file as in a scheduled backup certain params, like the NW server to use, are overridden by the scheduled backup and the client config file setting is then ignored...

@bbeckers1​ I have not tested backup from client side ..cannwe run through save command or any other way to run ...

Can you help me to resolve the above post error message .

I had created manually client in gui and using configuration file in backup command

@Brahmaiah E​ as sated before without stating actually WHAT you have configured where... for example in the configuration file, etc, it is problematic to point you into a direction, as first things firts, as at first the backup needs to be configured correctly and then work from there...

Hence the earlier referenced examples that also show how to run a manual backup from client end (which however assumes you have already configured the .cfg file correctly). And on NW end for the scheduled backup, stating the correct save set.

And might have a look at https://www.dell.com/community/en/conversations/networker/networker-db2-backup-configuration-and-log-collection/647f6c56f4ccf8a8de97fa74 . Might however wanna use a different pool than Default. Pretty much all other settings are also up to what is used in your environment?

@bbeckers1 ,I had created client manually and using configuration file and configuration file i and provide all the details 

@Brahmaiah E​ All the details? You have not shown what you have actually configured that might explain why the error states you do not seem to have a node name, as it reports as an empty string ""?

So that would be stated in the save set, but you have not mentioned any of the settings, only the resulting error.