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:
There are several ways to perform MSSQL database replication, including log shipping, database mirroring and AlwaysOn Availability Groups. It is highly recommended to adopt AlwaysOn Availability Groups whenever it is possible, however, sometime we still need to use database mirroring due to the environment limitation.
This post is to outline the steps to configure the MSSQL database mirroring. The example topology is as below:
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.