accessing MSDP and dedup pool from mulitple networks
Hello all, First of all i would like to provide my excuse for my poor english writing, i'm french. I come today on this forum to query advices and solutions for the problem i'm going to report here. i just come to deploy a netbackup environnement with these architecture: netbackup version: 7.6.1 - Principal Site: Rôles: backup VMWare virtual machines (hypervisor network) thru media-hyp-princ.domain.fr network interface backup clients for physical servers (backup network) thrumaster-princ.domain.fr of the master andmedia-princ.domain.fr for the media NDMP backup Operating system:Windows 2012R2 for master and media one VM (VMWare): master server/EMM, one network interface on backup network (master-princ.domain.fr) One physical server: MSDP with one dedup pool attached MSDP is multi-homed: one network interface on hypervisor network (bonding SFP+ 10Gb,media-hyp-princ.domain.fr), one network interface on backup network (bonding SFP+ 10Gb, media-princ.domain.fr) MSDP FQDN is configured on hypervisor network hostname (media-hyp-princ.domain.fr) The media gateway is on the backup network, on the network interface media-princ.domain.fr The master gateway is on the backup network, on the network interface master-princ -Secondary site: Rôle: AIR (Auto image Replication) One netbackup appliance 5230: master/media MSDPFQDN is configured on backup network hostname (master-sec.domain.fr) MSDP has just one bonding SFP+ 10Gb on backup network (master-sec.domain.fr) Each backup (VMs and clients) on the principal site are replicated via AIR to the secondary domain (using SLP) i've checked the network client backup flow and all transits thru the backup vlan (media-princ.domain.fr), that we want And the VMWare backup is on the same VLAN (hypervisor vlan) so the backup flow transits thru media-hyp-princ.domain.fr network interface All works great but.... The deduplication pool is attached to the MSDP hostname media-hyp-princ.domain.fr, on the hypervisor VLAN and i try to associate media-princ.domain.fr to the MSDP that it could be recognize as media-princ.domain.fr and media-hyp-princ.domain.fr i've added media-princ.domain.fr as media server and you ca see below the nbemmcmd.exe -listhosts result: <netbackup_install_path\NetBackup\bin\admincmd>nbemmcmd.exe -listhosts NBEMMCMD, Version: 7.6.1 The following hosts were found: server master-princ.domain.fr master master-princ.domain.fr media media-hyp-princ.domain.fr ndmp media-hyp-princ.domain.fr remote_master master-sec virtual_machine vcenter.domain.fr replication_host master-sec media media-princ.domain.fr ndmp vuserhomedata-cl1.domain.fr Command completed successfully. media-princ.domain.fr and media-hyp-princ.domain.fr appear on the media list from the netbackup windows administration console as media server. As you can see, media-princ.domain.fr and media-hyp-princ.domain.fr are the same physical media server but on differents vlans Why i want to do this ? because when i try to backup Active Directory servers with granular recovery, client backed up try to communicate with media-hyp-princ.domain.fr, and this is the only error i encounter. Below the nbfsd logs on the client: 12:25:18.724 [472.2344] <2> logparams: <install_path_netbackup_client>\Veritas\NetBackup\bin\nbfs mount -server media-hyp-princ.domain.fr -port 7394 -retry 11 -cred ABCDEFGHIJKLMNOPQRSTUV (cred volontary replaced for copy on this forum) * 12:25:18.739 [472.2344] <2> rpc_connect: connecting to media-hyp-princ.domain.fr 12:25:39.753 [472.2344] <16> rpc_connect: can't create TCP connection to media-hyp-princ.domain.fr (12 10060), will retry... 12:25:44.760 [472.2344] <2> rpc_connect: connecting to media-hyp-princ.private.univ-tlse3.fr 12:26:05.773 [472.2344] <16> rpc_connect: can't create TCP connection to media-hyp-princ.domain.fr (12 10060), will retry... 12:26:10.781 [472.2344] <2> rpc_connect: connecting to media-hyp-princ.domain.fr 12:26:31.810 [472.2344] <16> rpc_connect: can't create TCP connection to media-hyp-princ.domain.fr (12 10060), giving up I've tried to manually debug using this methode below but replacing media-hyp-princ.domain.fr by media-princ.domain.fr: https://www.veritas.com/support/en_US/article.TECH124810 and it works.... i've tried to create medi-hyp-princ.domain.fr alias with media-princ.domain.fr instead of declaring media server media-princ.domain.fr I've tried to modify hosts file on the client to backed up with the IP adress of media-princ.private.domain.fr for media-hyp-princ.domain.fr i've tried preferred network QUESTIONS: 1) Do i have to re-install everything from scratch using medi-princ.domain.fr as MSDP name ? i found the link below: https://www.veritas.com/support/en_US/article.000072756 Perhaps is it the best solution for me because i have a lot of production backup on the media 2) If i do this, do will i have trouble to backup virtual Machines with a deduplication pool attached on a MSDp on backup VLAN (media-princ.domain.fr) 3) I've tried to associate media-princ.domain.fr to the Storage Unit (PureDisk, dedup-pool) but it doesn't appear (i know that it must be a MSDP and not alonely a media server).Can i configure a second MSDP (with differents credentials and different name)on the same server ? i think no Because MSDP is declared on hypervisor vlan, my responsible wants i re-install everything.... After such a big works, i'm desesperate in the idea to re-install everythings, i did all the research, test, and implementation alone, without help, this represent months of work, but in my test environnement, my media wasn't on multiple network, just on the hypervisor network, so i did the same configuration on my pre-production architecture and i think now this is a mistake to configure my MSDP on the hypervisor network Thanks a lot in advance for your advices and solutions
Vmware View and Netbackup 7.6
Hello, I'm trying to backup a VDI environment w/ Netbackup. I'm able of using the VIP (vmware inteligente policy) that I can backup everyting starting w/ VDESK* using linked clones I was trying to use an option (clicking Advanced at vmware pannel) select "dont backup boot disk" that was supposed to be perfect, the only problem is that Vmware do not understand the Snapshot that Netbackup needs to execute. does anyone have won this challenge? I do not want to install an agente in every virtual desktop so I 'll have some problem W/ DNS and I really don't want to :) I have read something about create the persistant disk in a different datastore, so Vmware dont recomend that. Best Regards Any Idea will be very usefull
netapp backup is failing with error 84 and showing message "FREEZING media id XXXXX, too many data blocks written, check tape/driver block size configuration"
One netapp volume(NDMP) backup is failng with error 84 and in details logs it is showing the message "FREEZING media id XXXXX, too many data blocks written, check tape/driver block size configuration" we are using netbackup 7.0.1.2 (OS-Solaris10).
VxBSACreateObject: Failed with error
Hi all, I need your help, my manager Netbackup on a Windows 2008 operating system and Netbackup 7. We have an integration with RMAN but when I run the backup sguente send us the error. The owner forOracle engine is ORACLE and the NetBackup with another user named NetBackup, and integrate the same group of DBA but still sends me the same error. INF - Begin progress logging for process: (14464.15088) INF - Using policy BMB_SMCHFMPROD4_HFM_Ora_Onl_D to perform a user directed Oracle Stream Based backup. INF - Starting Oracle Recovery Manager. INF - Using: "f:\app\hfm\product\11.2.0\dbhome_1\bin\rman.exe" INF - Connection info: target 'netbackup/*****@HFM' rcvcat 'RMANHFM/*****@rmanbm' INF - Start of Recovery Manager input. INF - # ----------------------------------------------------------------- INF - # RMAN command section INF - # ----------------------------------------------------------------- INF - RUN { INF - ALLOCATE CHANNEL ch00 INF - TYPE 'SBT_TAPE'; INF - SEND 'NB_ORA_CLIENT=SMCHFMPROD4,NB_ORA_SID=HFM,NB_ORA_POLICY=BMB_SMCHFMPROD4_HFM_Ora_Onl_D,NB_ORA_SERV=mxqrsbur,NB_ORA_SCHED=Diario'; INF - BACKUP INF - INCREMENTAL LEVEL=0 INF - FORMAT 'bk_u%u_s%s_p%p_t%t' INF - TAG 'rl_t%t_s%s_p%p' INF - DATABASE; INF - RELEASE CHANNEL ch00; INF - # Backup Archived Logs INF - sql 'alter system archive log current'; INF - ALLOCATE CHANNEL ch00 INF - TYPE 'SBT_TAPE'; INF - SEND 'NB_ORA_CLIENT=SMCHFMPROD4,NB_ORA_SID=HFM,NB_ORA_POLICY=BMB_SMCHFMPROD4_HFM_Ora_Onl_D,NB_ORA_SERV=mxqrsbur,NB_ORA_SCHED=Diario'; INF - BACKUP INF - FORMAT 'arch_u%u_s%s_p%p_t%t' INF - ARCHIVELOG INF - ALL INF - DELETE INPUT; INF - RELEASE CHANNEL ch00; INF - # Control file backup INF - ALLOCATE CHANNEL ch00 INF - TYPE 'SBT_TAPE'; INF - SEND 'NB_ORA_CLIENT=SMCHFMPROD4,NB_ORA_SID=HFM,NB_ORA_POLICY=BMB_SMCHFMPROD4_HFM_Ora_Onl_D,NB_ORA_SERV=mxqrsbur,NB_ORA_SCHED=Diario'; INF - BACKUP INF - FORMAT 'ctrl_u%u_s%s_p%p_t%t' INF - CURRENT CONTROLFILE; INF - RELEASE CHANNEL ch00; INF - } INF - End of Recovery Manager input. INF - Start of Recovery Manager output. INF - Recovery Manager: Release 11.2.0.1.0 - Production on Fri Feb 3 23:27:50 2012 INF - connected to target database: HFM (DBID=1249472717) INF - connected to recovery catalog database INF - allocated channel: ch00 INF - channel ch00: SID=696 device type=SBT_TAPE INF - channel ch00: starting incremental level 0 datafile backup set INF - input datafile file number=00012 name=I:\HFM\DATAFILE\CISFM.DMP INF - input datafile file number=00014 name=H:\HFM\DATAFILE\CISODIWORK.DMP INF - input datafile file number=00015 name=I:\HFM\DATAFILE\CISFM01.DMP INF - input datafile file number=00016 name=I:\HFM\DATAFILE\CISFM02.DMP INF - input datafile file number=00017 name=I:\HFM\DATAFILE\CISFM03.DMP INF - input datafile file number=00019 name=G:\HFM\DATAFILE\CISEA01.ORA INF - input datafile file number=00020 name=G:\HFM\DATAFILE\CISEA02.ORA INF - input datafile file number=00021 name=G:\HFM\DATAFILE\CISEA03.ORA INF - input datafile file number=00022 name=G:\HFM\DATAFILE\CISEA04.ORA INF - Begin progress logging for process: (2436.13472) INF - Start backup of backup piece: (bk_u0vn2e6rs_s31_p1_t774314876) INF - Server status = 241 ERR - Server exited with status 241: the specified schedule is the wrong type for this request INF - input datafile file number=00007 name=H:\HFM\DATAFILE\CISEPMA.DMP INF - input datafile file number=00018 name=H:\HFM\DATAFILE\CISODIWORK2.DMP INF - input datafile file number=00003 name=E:\HFM\DATAFILE\O1_MF_UNDOTBS1_78OBHVV8_.DBF INF - input datafile file number=00013 name=H:\HFM\DATAFILE\CISODI.DMP INF - input datafile file number=00001 name=E:\HFM\DATAFILE\O1_MF_SYSTEM_78OBH3V0_.DBF INF - input datafile file number=00002 name=E:\HFM\DATAFILE\O1_MF_SYSAUX_78OBHK1G_.DBF INF - input datafile file number=00005 name=J:\HFM\DATAFILE\CISHSS.DMP INF - input datafile file number=00008 name=J:\HFM\DATAFILE\CISHBI.DMP INF - input datafile file number=00011 name=E:\HFM\DATAFILE\CISFDM.DMP INF - input datafile file number=00004 name=E:\HFM\DATAFILE\O1_MF_USERS_78OBJ9N7_.DBF INF - released channel: ch00 INF - RMAN-00571: =========================================================== INF - RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== INF - RMAN-00571: =========================================================== INF - RMAN-03009: failure of backup command on ch00 channel at 02/03/2012 23:28:12 INF - ORA-19506: failed to create sequential file, name="bk_u0vn2e6rs_s31_p1_t774314876", parms="" INF - ORA-27028: skgfqcre: sbtbackup returned error INF - ORA-19511: Error received from media manager layer, error text: INF - VxBSACreateObject: Failed with error: INF - Server Status: the specified schedule is the wrong type for this request INF - Recovery Manager complete. INF - End of Recovery Manager output. INF - End Oracle Recovery Manager.
