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
Backup Exec 2012, SQL Server 2012 Database drive & Log drive of SAN storage are not visible.
I have below environment, of the running system Application: Microsoft Dynamic CRM 2011 SQL Server: Cluster Database 2012 on SAN storage O/System: Windows Server 2012 R2 standard 2 node cluster Backup Exec: 2012 with SP4 (Only one server) Problem: Backup Exec 2012, SQL Server 2012 Database drive & Log drive of SAN storage are not visible. So I am not able to take backup. Action: Create new “srvbackup” account equal to domain admin, Login backup exec server with srvbackup. In backup exec create login account with srvbackup push the agent to sql database servers In backup exec Setting -> Network and Security -> Enable TCP dynamic port 10001 – 10050 Login to both servers open backup agent utility give ip in publish tab and add srvbackup account and password SQL Management Utility assign role to srvbackup user (1) dbcreator (2) securityadmin (3) serveradmin (4) sysadmin Note: All this above exercise SQL database drive & Log drive of SAN storage is not visible.
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
SSR 2013 und GRO SharePoint 2010 Foundation
Hallo, warum unterstützt die SSR 2013 GRO die SharePoint 2010 Foundation Option nicht mehr? bei der ver.BESR 8.5 war noch alles in Ordnung, man konnte jede kleinste Datei wiederherstellen und was ist jetzt ab SSR 2011 ist nicht mehr vorhanden das finde ich nicht in Ordnung und schlimmste ist dass man keine Antwort bekommt Ich habe mit Support kontakt aufgenommen (das hat 14 Tage hin und her gedauert) die Techniker aus Indien und USA wussten überhaupt nicht was dieser Fehler bedeuten. Nach 4 Wochen habe Antwort bekommen dass das überhaupt nicht funktioniert, weil die Funktion für SharePoint 2010 Foundation wird nicht mehr unterstützt. Hilfe bei Lösung dieses Problemshabeich keine bekommen. Vieleicht hat jemandeine Idee wie ich das lösen kann. DANKE im Voraus
