i need yours help urgently
our few sql db policies are failing with below error.
none of the requested files were backed up
even though netbackup id have full permission i restarted service multiple times and reconfigure script still same issue
it is under cluster in some policies active node is failing passive node backup sucessfull please help me to resolve this issue
thanks for yours reply
could you please provide the steps it will be very helpfull for me
just to note recently we replaced netbackup appliacne ( media server) in some policy passsive node backup working fine,
In cluster terms, we refer to 'physical' names as the cluster node names.
Virtual names refer to the virtual hostname that is associated with the clustered instance.
Please do yourself a favour - download the NBU for SQL manual (click on the Acrobat reader icon in below link):
NetBackup for Microsoft SQL Server Administrator's Guide
Read all cluster-related topics, e.g.
- Reviewing the auto-discovered mappings in Host Management
- Configuring mappings for restores of a distributed application, cluster, or virtual machine
- Configuring backups of clustered SQL Server instances (SQL Server Intelligent Policy)
- Configuring backups of clustered SQL Server instances (legacy SQL Server policies)
@intradmin you are confusing yourself between hypervisor host (aka VMware) which typically runs as a cluster of ESXi hosts - versus, guest VMs which can themselves be clustered at the guest level.
In such a guest cluster, each VM will have a primary NIC primary IP and primary host name.
guestA 10.0.10.1 - and has private disk C: and D:
guestB 10.0.10.2 - and has private disk C: and D:
...but we want to "layer" a cluster above these guest OS. We want to be able to "fail-over" a set of resources from one guestA to guestB and vice versa.
So, we create a Cluster Resource Group, which typically contains:
guestC 10.0.10.3 - and has shared disk E:
...and so what appears to be a third IP, a "cluster virtual IP" (aka "cluster VIP") can failover across two guest OS - and so all three resources:
resource name: guestC
resource IP: 10.0.10.3
resource volume: E:
...all failover across guestA and guestB - because all three resource types live in the same "resource group".
you should send us a new version of Host Management printscreen, where "Mapped Host Names" column is visible with all values.
Error 7643 still persists in error logs, so I guess that hqdb-sp* nodes dont have proper mapping to SQL vistual cluster name.
Hint - I see from your printscreen that your Master Server is also clustered (DCNBMASTCLU/MAST01/MAST02). So follow the same mapping steps for SQL server physical/virtual nodes.
Also, to better isolate the problem, run simple filesystem backups first - with physical nodes as clients, and with virtual cluster node as client, if it works.