While trying to restore a backup to a different server. Verify configuration failed when NBU Client Name and NBU Restore Client Name are not the same
Leo Configure :-
Verify Configuration (y/n)? [n]: y
Creating temporary file... OK
Opening file... OK
Setting file size to 1MB... OK
Closing file... OK
Compressing file... OK
Verifying target... OK
Deleting original file... OK
Uncompressing file... EXIT STATUS 2800: invalid error number
Tested the below bpbackup and bprestore command of NetBackup with a small file
On Source Server :-
1. bpbackup -w -p <Netbackup policy name> -S <Netbackup server name> -h <Netbackup client node name> <filename>
bpbackup -w -p policyname -S netbackupserver -h sourceserver small_file_for_testing.log
On Target Server :-
2. bprestore -w -p <Netbackup policy name> -S <Netbackup server name> -C <Netbackup alternate client> -D <Netbackup client node name> <filename>
bprestore -w -p policyname -S netbackupserver -C sourceserver -D targetserver small_file_for_testing.log
Above commands worked fine.
Though LEO verify configuration step gave the above error, the restore succeeded nonetheless. The NetBackup client log does not report any error.
The purpose of "verify configuration" is simply to confirm that the connection to the Netbackup server is working from the client that is running the verification. No other clients can be involved in the verification.
When running verify configuration, the NBU Client Name and NBU Restore Client Name have to be the same. That's because the code running the verify procedure is all being run on the same machine – the test backup is done from machine X, and then the restore is also to machine X. It is probably incorrect to have the verification try to test backup and restore with different Client name and Restore Client Name, when in fact both backup and restore operations are being done on the same client. The reason it worked with bpbackup and bprestore is because the bpbackup really was done on the "alternate client", so when the bprestore is run, Netbackup finds the backup file it needs associated with the "alternate client" on the server. If the experiment was repeated this way (but with a different file this time), it would also fail:
On Source Server :-
1. bpbackup -w -p <Netbackup policy name> -S <Netbackup server name> -h <Netbackup client node name> <filename>
bpbackup -w -p policyname -S netbackupserver -h sourceserver small_file_for_testing2.log
Also on the Source Server :-
2. bprestore -w -p <Netbackup policy name> -S <Netbackup server name> -C <Netbackup alternate client> -D <Netbackup client node name> <filename>
bprestore -w -p policyname -S netbackupserver -C targetserver -D sourceserver small_file_for_testing2.log
That bprestore would fail because the "Netbackup alternate client" is not where the backup was done. This invalid "bprestore" is what LEO's verification routine is doing when the NBU Client Name and NBU Restore Client Name do not match. LEO is properly using the node names that were given, but when it runs the bprestore, it gets an error because the backup was not performed on the "alternate client".
To verify the LEO configuration, i.e. to verify that the netbackup server connection is working properly, the NBU Client Name and NBU Restore Client Name should be set to be the same, and select "Y" to verify at the end of the configuration routine. But to configure it the way it is required for the actual database restore from a backup made elsewhere, LEO should be configured properly to reference the alternate client, but select "N" when "leo configure" asks to verify the configuration.
