netbackup unable to resolve hostname, no hostname alias added to pem name manager.
Hi, I see the below error on my problems report: netbackup unable to resolve hostname <hostname>, no hostname alias added to pem name manager. Now there's about 16 of these servers and they have all been decommissioned and they are not associated with any policy and they are not under client's host properties on the GUI. Upon searching under the /usr/openv/netbackup/db/client directory, all 16 of these client folders are still in there. Is it OK to just remove/delete these client folders on this directory? Or is there another way of getting rid of these error? Regards
NBU Appliance IPMI KVM Disabled
I have a 5230 Appliance, I have managed to get the IPMI configured by using IPMITools. When I try to use the KVM portion (Click on the Remote Control tab) I get a pop-up saying "This feature has been disabled by an administrator" I followed the instructions setting up the bios, but there was not mention of doing anything with the redirection settings so I left them alone, have I missed something? All other functionality is there, but the java kvm does not work. (no prompt for plugin download, so something seems to be turned off)
AIR replication is failing
Hi All, I have master server on windows 2008 datacentre x64 and two 5230 Netbackup appliances. Main Site : One windows master server and one Netbackup 5230 appliance as media server DR site : One Netbackup 5230 appliace as media server. I am configuring AIR between main site windows master server and DR site Netbackup Appliance 5230 as master server. I have configured the aAIR as per standard configuration. I am facing an issue during replication. Please see the below replication job detail and help me. Thank you... ========================================================================================================== Logs : 9/10/2014 2:43:31 PM - requesting resource LCM_*Remote*Master*:msdp_sql_dc_to_dr_2_week 9/10/2014 2:43:31 PM - granted resource LCM_*Remote*Master*:msdp_sql_dc_to_dr_2_week 9/10/2014 2:43:31 PM - Info nbreplicate(pid=6296) Suspend window close behavior is not supported for nbreplicate 9/10/2014 2:43:31 PM - Info nbreplicate(pid=6296) window close behavior: Continue processing the current image 9/10/2014 2:43:31 PM - started process RUNCMD (6296) 9/10/2014 2:43:32 PM - requesting resource @aaaae 9/10/2014 2:43:32 PM - reserving resource @aaaae 9/10/2014 2:43:32 PM - reserved resource @aaaae 9/10/2014 2:43:32 PM - granted resource MediaID=@aaaae;DiskVolume=PureDiskVolume;DiskPool=dp_disk_dc-nbmedia01;Path=PureDiskVolume;StorageServer=dc-nbmedia01;MediaServer=dc-nbmedia01 9/10/2014 2:47:39 PM - Error nbreplicate(pid=6296) ReplicationJob::Replicate: Replication failed for backup id sqlf02_1410349007: media write error (84) 9/10/2014 2:47:39 PMReplicate failed for backup id sqlf02_1410349007 with status 84 9/10/2014 2:47:39 PM - end operation 9/10/2014 2:48:31 PM - Info bpdm(pid=206039) started 9/10/2014 2:48:31 PM - started process bpdm (206039) 9/10/2014 2:48:34 PM - Info dc-nbmedia01(pid=206039) StorageServer=PureDisk:dc-nbmedia01; Report=PDDO Stats for (dc-nbmedia01): scanned: 4 KB, CR sent: 1 KB, CR sent over FC: 0 KB, dedup: 75.0%, cache disabled 9/10/2014 2:48:35 PM - Info dc-nbmedia01(pid=206039) Using OpenStorage to replicate backup id sqlf02_1410349007, media id @aaaae, storage server dc-nbmedia01, disk volume PureDiskVolume 9/10/2014 2:48:35 PM - Info dc-nbmedia01(pid=206039) Replicating images to target storage server dr-nbmaster, disk volume PureDiskVolume 9/10/2014 2:52:35 PM - Critical bpdm(pid=206039) Storage Server Error: (Storage server: PureDisk:dc-nbmedia01) async_get_job_status: Replication started but failed to complete successfully: Error occured during replication. Look at the replication logs on the source storage server for more information. V-454-105 9/10/2014 2:52:35 PM - Error bpdm(pid=206039) wait failed: error 150 9/10/2014 2:52:35 PM - Error bpdm(pid=206039) <async> cancel failed: error 2060001: one or more invalid arguments 9/10/2014 2:52:35 PM - Error bpdm(pid=206039) copy cancel failed: error 174 9/10/2014 2:52:35 PM - Info dc-nbmedia01(pid=206039) StorageServer=PureDisk:dc-nbmedia01; Report=PDDO Stats for (dc-nbmedia01): scanned: 4 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache disabled no images were successfully processed(191)
Status 2060019 and status 87 Killing same job
Got following errors in our details on a solaris backup. Im on an appliance, 5220. We are running 7.6.1.1. Link to 2060019 in error message is a cyclical redirect. I saw in other posts that this was a problem in the pre 7.5.0.4 world, but was supposed to be fixed in 7.5.0.5. Which is not our experience. Is there are work around for this? Anyone else seen it in the post 7.6.1.1 version? ​05/10/2015 00:56:17 - Critical bptm (pid=4960) Storage Server Error: (Storage server: PureDisk:servername) mtstrm_close_write_channel: Fatal error occured in Multi-Threaded Agent: Close Write Channel command failed: Cr_ErrnoException: Timed out after waiting 180s for the read threads to complete (cnt=1) V-454-96 05/10/2015 00:56:17 - Critical bptm (pid=4960) sts_close_handle failed: 2060019 error occurred on network socket 05/10/2015 00:56:17 - Critical bptm (pid=4960) sts_close_handle failed: 2060019 error occurred on network socket 05/10/2015 00:56:17 - Error bptm (pid=4960) cannot write image to disk, media close failed with status 2060019 05/10/2015 00:56:17 - Info bptm (pid=4960) EXITING with status 87 <---------- Thanks in advance.