I’ve been working very closely with a client recently that utilized EMC Networker 8.2.2 for their backup needs. Personally, I am a Veeam fan and try to do everything I can for clients to use Veeam backup software – as Apple would say, “It just works”.
This client was required by a software vendor to utilize a legacy SQL cluster configuration using Windows Server Failover Clustering (WSFC). This configuration required Physical RDM’s from their XtremIO system – therefore, I could not utilize the VM Image backup I am using for the rest of their environment.. Welcome to EMC Networker SQL Backups..
This information isn’t the easiest to find and like most EMC documentation, there is 1,000 pages of different ways to complete the task.
- EMC Networker
- EMC Networker Client
- EMC Networker Module for Microsoft Applications (NMM)
- Install the latest Networker Client software on each SQL Server in the cluster. In my case, this was 8.2.2
- If required, add the trusted Networker to the install. This will ensure ONLY this Networker server can backup this server
- Install the latest Networker Module for Microsoft Applications. This is the same software you would use to backup other Microsoft applications (Exchange is the big one) – IMPORTANT: A restart is required after the software is installed.
- Ensure Windows UAC is disabled – OR ensure the account that you are backing up the server with is in the “Local Administrator Group” and add that user as the “LogOn” account for the “Networker Remote Exec Service”
- Make sure the account you are using to backup the DB has DB access.
1. Under the configuration tab, add the clients needed (under New Client Properties)- this would be the SQL servers that make up the cluster. Ensure under the “Globals 1 of 2) tab, that under aliases, that the hostname is listed by FQDN and its shorn name. If you didnt start the service with the AD account you created, you can add the account used to backup the databases under the “Apps & Modules” tab.
2. Again, under the configuration tab, create another client for the SQL Cluster FQDN. I find it easier to do it this way, so that the other client machines are listed correctly. Once the cluster client is created, right click and go into the “Modify Client Wizard”. Add the databases you want to backup and finish.
3. Add the cluster client to the backup group that you want the databases to be backed up with.
Backup time will obviously vary with the amount of databases and the size – as expected.
Hope this helps!