NDMP : Error 636 read from input socket failed
Hi NBU community ! I need your help for the error in the subject. Before the explanation, i present you the context. The environment is the next : Master : VM 2K16 in NBU 9.0.0.1 Media : Physical server 2K16 in NBU 9.0.0.1 NDMP : Nas server Dell EMC Unity My company wants to backup 7 nas server in NDMP with LTO8 drives. 5 nas server are backed up really good without errors, maybe because the volumetry is low. But, we've 2 nas servers that are complicated to back up. Each nas server does 55 To and goes on error 636 the major of time. With some chance, we can have a successful backup of these. I checked articles about tcpkeepalive etc... but i think the problem is somewhere else. You will find in attachment the details of a failed job. Please explain me what is wrong with my nas servers. Thanks.
NDMP restore 'Tape media server is not active'
Hey everyone, been a while since I've had to post here ;) I have a very strange issue which is blocking our ability to restore some data. We have an old NBU 7.5.0.7 system which has been in operation for many years. This system is a VM master server, a few physical media servers, and a number of NetApp filers. All systems aside from the master are plugged into a fiber channel SAN, and NDMP backups are run from the filers to the tape drive directly. The media servers do random standard backups of misc systems. I have NDMP backups from these filers from a few months ago (March) which if we kick off a restore from, we immediately get the message 'Tape media server is not active'. Here is a snip from the job Detailed Status in the NBU Java GUI: 06/03/2021 13:42:51 - begin Restore 06/03/2021 13:42:52 - number of images required: 1 06/03/2021 13:42:52 - media needed: E00128 06/03/2021 13:42:52 - media needed: E00108 06/03/2021 13:42:52 - media needed: E00113 06/03/2021 13:42:52 - media needed: E00120 06/03/2021 13:42:52 - restoring from image pd-dd-07_1615860482 06/03/2021 13:42:52 - Info bpbrm (pid=7975) pd-dd-02 is the host to restore to 06/03/2021 13:42:52 - Info bpbrm (pid=7975) telling media manager to start restore on client 06/03/2021 13:42:52 - Info bpbrm (pid=7975) spawning a brm child process 06/03/2021 13:42:52 - Info bpbrm (pid=7975) child pid: 7980 06/03/2021 13:42:52 - Info bpbrm (pid=7980) start tar on client 06/03/2021 13:42:52 - Info tar (pid=7984) Restore started. 06/03/2021 13:42:53 - requesting resource E00120 06/03/2021 13:42:53 - awaiting resource E00120. Waiting for resources. Reason: Tape media server is not active, Media server: pd-nbumaster, Robot Type(Number): TLD(2), Media ID: N/A, Drive Name: N/A, Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A, Disk Pool: N/A, Disk Volume: N/A this restore forever hangs, never getting beyond this point. I'm not quite sure why it's upset about this. The media server it is showing, pd-nbumaster, is in fact the VM master server, which has no drives or robots physically attached to it. What is even more confusing about this, is that if we try to restore from more recent backups, say in the last month, they restore fine, though those restores all appear to use one of the physical media servers (not filers) as a media server for the restore. The server 'pd-ms2' in this case is one of the physical media servers: 06/03/2021 14:06:13 - begin Restore 06/03/2021 14:06:13 - number of images required: 1 06/03/2021 14:06:13 - media needed: E00561 06/03/2021 14:06:13 - media needed: E00574 06/03/2021 14:06:13 - media needed: E00566 06/03/2021 14:06:14 - restoring from image pd-dd-07_1622280123 06/03/2021 14:06:14 - Info bpbrm (pid=4466) pd-dd-02 is the host to restore to 06/03/2021 14:06:14 - Info bpbrm (pid=4466) telling media manager to start restore on client 06/03/2021 14:06:14 - Info bpbrm (pid=4466) spawning a brm child process 06/03/2021 14:06:14 - Info bpbrm (pid=4466) child pid: 4469 06/03/2021 14:06:15 - Info bpbrm (pid=4469) start tar on client 06/03/2021 14:06:15 - Info tar (pid=4472) Restore started. 06/03/2021 14:06:15 - Info bptm (pid=4468) Waiting for mount of media id E00574 (copy 1) on server pd-ms2. 06/03/2021 14:06:15 - started process bptm (pid=4468) 06/03/2021 14:06:15 - mounting E00574 06/03/2021 14:06:15 - Info bptm (pid=4468) INF - Waiting for mount of media id E00574 on server pd-ms2 for reading. 06/03/2021 14:06:18 - Info ndmpagent (pid=4472) pd-dd-02: Session identifier: 14867 06/03/2021 14:06:15 - requesting resource E00574 06/03/2021 14:06:15 - granted resource E00574 06/03/2021 14:06:15 - granted resource IBM.ULTRIUM-TD8.005 this restore goes on to succeed. I have tried a few things to force the media server as described here: https://www.veritas.com/support/en_US/article.100000701 I've also rebooted all systems involved at least once. However nothing has changed. Any time I try to NDMP restore from these older backups, it always wants to use the master server as the media server. Restores from newish backups seem to run fine, using the physical media servers. Any ideas?
ndmp backup stops in middle of backup job
Hello people, Our ndmp filers can connect to the backup server but backupping the data is not going to complete. The others clients such as Windows file servers and linux machines backup state is perfect.The backup media master server is NB 8.1.2 on Windows Server 2016 fully patched. The backup server can connect to the NDMP host, runs for 10 - 20 minutes while writing data and then stops. Can someone give usefull information?
Manual Duplication is failing with 191 error code
NetBAckup Version: 8.1.1 OS Version: SLES 12 SP 1 My duplication job which is done by SLP fails with the following error after witing a couple of bytes. Apr 9, 2019 12:30:59 PM - mounting 0384L7 Apr 9, 2019 12:30:59 PM - Info bptm (pid=18780) INF - Waiting for mount of media id 0384L7 on server sivls105 for writing. Apr 9, 2019 12:31:32 PM - Info bptm (pid=18780) media id 0384L7 mounted on drive index 21, drivepath /dev/alias/nst/C3EC3D2008, drivename IBM.ULTRIUM-HH7.003, copy 2 Apr 9, 2019 12:31:32 PM - Info bptm (pid=18780) INF - Waiting for positioning of media id 0384L7 on server sivls105 for writing. Apr 9, 2019 12:35:07 PM - Error bptm (pid=13610) cannot read image from NDMP media id @aaaab, drive index -1, error code 20 (NDMP_UNDEFINED_ERR) Apr 9, 2019 12:35:07 PM - Error bptm (pid=13610) NBEMM returned an extended error status: Invalid argument (4000002) Apr 9, 2019 12:35:07 PM - Info bptm (pid=13610) EXITING with status 85 <---------- Apr 9, 2019 12:35:09 PM - Error bptm (pid=18780) media manager terminated by parent process Apr 9, 2019 12:36:31 PM - Error bpduplicate (pid=18763) host sivls106 backup id mp2vmsd058_1524904249 read failed, media read error (85). Apr 9, 2019 12:36:31 PM - Error bpduplicate (pid=18763) host sivls105 backupid mp2vmsd058_1524904249 write failed, media manager killed by signal (82). Apr 9, 2019 12:36:31 PM - Error bpduplicate (pid=18763) Duplicate of backupid mp2vmsd058_1524904249 failed, media manager killed by signal (82). Apr 9, 2019 12:36:31 PM - Error bpduplicate (pid=18763) Status = no images were successfully processed. Apr 9, 2019 12:36:31 PM - end Duplicate; elapsed time 0:05:35 no images were successfully processed (191)
EMC VNX NAS and NetBackup 7.7.x SCSI reserve configuration
Hello, friends. I've reviewed Veritas' and EMC's documentation but not found the answer (yet) to this question, so I'm posting it here. I want to validate that EMC VNX NAS datamover configuration for enabling "scsiReserve" is compatible with my media servers' SPC-2 SCSI reserve option (currently selected.) I'm believing this to be the case, but not finding a lot of concrete information to support that belief. Any suggestions of where to look ?
