cancel
Showing results for 
Search instead for 
Did you mean: 

SQL backup failures

Rick_Brown
Level 4

If this has already been discussed, please forgive - I wasn't able to find it.

 

Have a Win2003 cluster & NBU 6.5.2A (network client) - SQL/Logs & File system working perfect on 02/13/09.

Now only the file system works. All SQL backup fail with a status 2 in ~50 seconds.

No .bch changes have been made.

 

Some of what I got from bpclient:

9:32:22.729 [7924.5256] <2> vnet_check_vxss_client_magic_with_info: ..\libvlibs\vnet_vxss_helper.c.770: Ignoring VxSS authentication: 2 0x0000000209:32:22.729 [7924.5256] <2> vnet_check_vxss_client_magic_with_info: ..\libvlibs\vnet_vxss_helper.c.926: Not using VxSS authentication: 2 0x0000000209:32:22.745 [7924.5256] <2> bprd_get_features: Cannot parse product and feature IDs from EXIT STATUS 2309:32:22.745 [7924.5256] <16> bsa_checkFeatureId: unable to check if feature <33> is licensed09:32:22.745 [7924.5256] <16> bsa_checkFeatureId: Server exit status = 43: unexpected message received09:32:22.745 [7924.5256] <16> VxBSAInit: ERR - The license for the requested feature is not available.09:32:22.745 [7924.5256] <4> VxBSAGetEnv: INF - entering GetEnv - NBBSA_DEBUGFD

09:32:22.745 [7924.5256] <4> VxBSAGetEnv: INF - returning

 

bpdbm on the master says this:

07:00:36.981 [2017] <2> list_client_images: /usr/openv/netbackup/db/images/pcadcd01v1 is empty or not accessible07:00:36.992 [2017] <2> list_client_images: /usr/openv/netbackup/db/images/pcadcd02v2 is empty or not accessible07:02:14.905 [3561] <2> list_client_images: /usr/openv/netbackup/db/images/pcadcd01 is empty or not accessible07:02:14.906 [3561] <2> list_client_images: /usr/openv/netbackup/db/images/pcadcd01v1 is empty or not accessible07:02:14.906 [3561] <2> list_client_images: /usr/openv/netbackup/db/images/pcadcd02 is empty or not accessible07:02:14.906 [3561] <2> list_client_images: /usr/openv/netbackup/db/images/pcadcd02v2 is empty or not accessible07:54:52.784 [24672] <2> clean_stream: pcadcd0107:54:52.801 [24672] <2> clean_stream: pcadcd01v107:54:52.817 [24672] <2> clean_stream: pcadcd0207:54:52.842 [24672] <2> clean_stream: pcadcd02v208:01:46.817 [29040] <2> list_client_images: /usr/openv/netbackup/db/images/pcadcd01v1 is empty or not accessible08:01:46.821 [29040] <2> list_client_images: /usr/openv/netbackup/db/images/pcadcd02v2 is empty or not accessible08:38:36.943 [14671] <2> client_db: client_db sendNotification(client=[pcadcd01], action=[add]) returns 008:39:07.000 [15108] <2> client_db: client_db sendNotification(client=[pcadcd01], action=[update]) returns 008:40:18.510 [15360] <2> client_db: client pcadcd01v1 does not exist09:04:00.271 [21670] <2> clean_stream: pcadcd0109:04:00.336 [21670] <2> db_get_image_info: Job in progress, found image file /usr/openv/netbackup/db/images/pcadcd01v1/1235000000/tmp/pcadcd01v1-sql-logs_1235137216_FULL09:04:00.368 [21670] <2> clean_stream: pcadcd01v109:04:00.387 [21670] <2> clean_stream: pcadcd0209:04:00.413 [21670] <2> clean_stream: pcadcd02v209:04:58.432 [25731] <2> client_db: client pcadcd01v1 does not exist09:32:08.872 [6895] <2> client_db: client_db sendNotification(client=[pcadcd01v1], action=[add]) returns 009:48:36.601 [13157] <2> client_db: client_db sendNotification(client=[pcadcd01v1], action=[update]) returns 0

 

I've opend a case with Symantec & am waiting to hear back from them. This one is just silly whatever it is.

 

Thanks,
Rick

1 ACCEPTED SOLUTION

Accepted Solutions

schmaustech
Level 5

If a regular file system backup is working and the SQL backups use to work but do not now, I am guessing one thing you should check is DNS.  Verify that the master and media servers can correctly resolve the forward and reverse DNS records for the MSSQL host.  Also verify that dns name matches the one used in the policy.

 

If this tests good, try initiating a mananual SQL backup from the host using the Netbackup MSSQL Client.

 

Regards,

 

Benjamin Schmaus

View solution in original post

4 REPLIES 4

schmaustech
Level 5

If a regular file system backup is working and the SQL backups use to work but do not now, I am guessing one thing you should check is DNS.  Verify that the master and media servers can correctly resolve the forward and reverse DNS records for the MSSQL host.  Also verify that dns name matches the one used in the policy.

 

If this tests good, try initiating a mananual SQL backup from the host using the Netbackup MSSQL Client.

 

Regards,

 

Benjamin Schmaus

Rick_Brown
Level 4

Yes, this is definately the issue. Multiple NIC's are involved and multiple IP's are used for the physical nodes & the virtual nodes (where sql runs). If I list the IP address of the virtual node in the "preferred NIC" setting, the sql backups work.

The bpclntcmd -pn on the client would not respond correctly, but I could get a good response from the NBU master. DNS has to be jacked up - no surprise there.

 

Symantec is checking to see if we can bind 1 IP address to the virtual client, instead of havin that setting be used on the Physical node client settings.

 

I'll let you know what we find out - thanks for the help.

Rick

schmaustech
Level 5

When I worked there I would often use host entries and if placed in the correct order and associated  (if I remember right, virtual cluster name followed by node names) would also get the resolution you desire.

 

Regards,

 

Benjamin Schmaus

Rick_Brown
Level 4

Reverse name lookups in DNS are not working for the clients. We were able to list the SQL instance IP address as the "preferred NIC" in the clients host properties allowing the client to backup its SQL data.

This is not the preferred fix, but work for an immediate solution. DNS needs to be fixed so the client as lookup the NBU master by name & IP.

 

Thanks again :)