Unable to find backed up files when I trying to recover them

Hello https://dell.to/3zwVX6D,

I'm not very familiar with Networker, but I will try to assist.

Take a look at this document, it may have what you are looking for:

Administration Guide, Chapter 9 : Recovery section page 481

Performing a browsable recover with NetWorker User Page 506

https://dell.to/3zA8qGF

Please let me know if it helped.

Hello,

Thank you for your response. 

My problem is not with recovering files. The problem is that .mdf and .ldf files (MSSQL log files) could not be backed up when using filesystem backup  type. So, I could not find them in savesets when I trying to recover them despite that I have selected the hole partition.

Did you have any explanation or solution for that please?

Thank you in advance.

Hi @Imen.Am,

Would need some time to discuss this issue with some of the colleagues. They might not be available at this point of time, might need some time to gather information. Meanwhile, what is the OS that it is running on? What is NetWorker build version? From the backup logs, is there any failure backup of files, eg: the .mdf files?

Just wondering if this can help on the savesets: https://dell.to/3Oas1Bx

Hi @DELL-Joey C ,

Networker Client is running on Windows  server 2019. The Networker server is installed on Linux server with 18.2.0.2 version.

 From the backup logs,  there is no failure backup of files. Backup is successful but when I'm trying to recover .mdf or .ldf files I could not find them when browsing backed up files.

I want to use filesystem backups type because these files are already under a partition and not SQL server type using NMM (Networker Module for Microsoft).

Hello @Dell -Charles R ,

Thanks a lot for your response.

I'm using filesystem to backup database files because I have already tried to use NMM SQL module

but I have a problem when backing up databases under Availability group AG.

Databases under AG are excluded. I have found that we need AG listener in order to have acces to these databases.

I have an MSSQL databases configured with three nodes each one in a network range. Two nodes in the production site and one in the DR site. We have many databases each one is under an AG.

As the AG listener is not configured, did you have an idea about how the listener sould be configured in order to have acces and backup all databases?

Hello https://dell.to/3O52KZJ,

I wanted to touch base. I am looking into this and will need some time. I will update you when I have more information.

Hello https://dell.to/3tL4Ndn,

The environment detailed here looks like an Always on Availability Group ( AOAG ) on a Failover cluster.

NMM supports scheduled and manual federated backups of SQL availability groups through the availability group listener.

Availability group listeners are virtual networks that provide access to an Always On Availability Group and all of its databases.

You can use NMM to backup and recovery an availability group using the listener name instead of the cluster name.

Unlike a cluster, when you use the listener name as the backup client name, NMM backs up only the availability group that the

listener is configured for.

If this is a ClusterLess AOAG , we can use the Physical nodes ( where the AOAG 2ndary copy resides ) to configure federated backups using the process below:

                1. Assign the IP address of the primary node to the clusterless availability group listener.

If there is a failover, assign the IP address of the new primary node to the listener.

2. In DNS, create a A record for the SQL nodes in the AlwaysOn Availability Group.

3. In DNS, create a A record for the listener.

The IP address of the listener is the same as the IP address of the primary node. DNS has two A records with the same IP

address. One record is for the primary node and the other for the listener. You do not need to reverse lookup.

4. On the NetWorker server, by using the Client Properties dialog box of the NetWorker Administration window:

a. Create client resources for the two nodes in the AlwaysOn Availability Group, and the listener.

b. Specify the save set, and the backup command of the listener.

From the NMM SQL VDI Admin guide - Configuring client resources for clusterless availability group listener and physical nodes of an AlwaysOn Availability Group section provides more details on manual client configuration.

Also, if you need assistance with setting this AOAG backup up, we recommend to call in and set up a SR with the Networker Support team and have an engineer walk through or help  with any challenges.

If your initial Restore issue for these files ( .mdf and .ldf ) are addressed and we need help with NMM – SQL AOAG backup setup, that may be the best way forward.

Hello Dell -Charles R,

Knowing that our failover cluster is a little bit complicated ( more that one AG and more than one database and  different subnets), is there any  solution in Networker other than the use of a listener is order to backup these databases under the AG?

Thank you in advance.