RecoverPoint for virtual machines (RP4VM) is one of the DELL EMC data protection solutions to provide the VM level protection locally or remotely.
Comparing with the hardware RecoverPoint Appliance, RP4VM utilized virtual RecoverPoint Appliance and provide VM level protection with the data splitters installed on each of the ESXi servers.
RP4VM relies the vCenter to function properly. This post is to provide a quick guide about how to check and update the vCenter registration information in RP4VM.
When operating DELL EMC Networker environment, in some scenarios, it is required to clone a few selected saveset to target devices. In general, there are two ways to perform this:
- Create a clone group with some filters, this is normally for scheduled clone; and
- Use nsrclone command line.
This post provides an example to perform the Networker saveset clone by SSID through commands.
This post is to provide the general trouble shooting steps for one DELL EMC Networker Common Error, the Error Message is:
No matching devices; check storage nodes, devices or pools
This error message usually appears in both Networker client and server daemon.raw logs. The good side to see this error is the client can communicate with server.
The error is related with the backup client could not find a matching backup device to write the backup data. Let’s use an example as below to explain the trouble shooting steps:
DELL EMC Networker provides a solution to backup NDMP NAS storage to Non-NDMP devices. This post is to outline the key steps of the Networker NDMP-DSA Backup configuration.
It is known that DELL EMC Networker performs Exchange database (DAG or Standalone) restoration through Networker Module for Microsoft (NMM) GUI on the client itself.
However, in some scenarios, directed database restoration is required with urgency. For example, the exchange server is crashed and it is required to restore the database and logs files to another standalone or DAG server.
This is a short post about one of the common failures in Networker Host Inventory.
I am recently working on an environment need to back up a 10TB SQL server by Networker and Data Domain. By utilizing DDBoost ans saveset “MSSQL:”, the backup job could be done in 13 hours for the daily full backup. This is not the worst result to backup a SQL server in 10TB, but we still can optimize it with some settings in Networker.
Recently I got a task to run a command or script to delete files in a given folder after a success backup. In general, there are two major ways, one way is to use PowerShell script and include Networker backup command, and the other way is to use EMC Networker customized backup command. I chose to use the second way because it is more closely integrated with Networker and easier to manage and monitor.
I follow the steps as below:
- Step 1: In the client host, create a file save001.bat under c:\Program Files\EMC NetWorker\nsr\bin.
- Step 2: Use txt editor to edit the Save001.bat with the script listed in the following post.
- Step 3: Login to NMC, in the Backup Command attribute of the Client resource, type the name of the backup script, save001.bat in our case.
I recently worked on a performance turning for the backup solution with below components:
- EMC Avamar as the backup server at DC1 and DC2;
- Data Domain as the backup target storages at DC1 and DC2; and
- Backup datasets are replicated between DC1 and DC2.
The backup client is Avamar NDMP node at both sites. The 50TB ISILON CIFS shares can be backed up in 2 hours by Avamar through NDMP. However, the replication of the daily backup to peer DC can take more than 24 hours.
From EMC Networker Module for Microsoft (NMM) version 9.1, EMC introduces the new feature “SQL Flat File Recovery”, no exciting, but really a helpful feature for the DBA and Backup admin.
Before EMC Networker NMM version 9.1, the MS SQL database only can be recovered to the SQL database, either to the original database or a different database. Since SQL database and Networker are usually managed by different teams, restoring directly to the database increases the internal communication between different teams to get the task done correctly. By introducing “SQL Flat File Recovery”, Networker admin can recover the database flat file to the desired location and DBA can recover the flat file to SQL database after that at any time.
NMM 9.1 can be used with Networker server version 8.2.3 or later with some limitations stated in the administrator guide.