Hello and welcome to Power Protect Data Manager appliance P 0.14 R three release. I'm Sonali Verma from the technical marketing engineering team. Today I'm going to present one of the key features that has been introduced in this release: replication to external Dell Power Protect DD series appliance or Dell Power Protect DD virtual edition.
This is a new functionality provided by DM5500 to replicate backup copies to an external Dell Power Protect DD or DDB. This application is implemented through the manage file application, also known as the MFR. We can replicate backup copies from DM5500 to one or more Power Protect DD or DDBE that can either be on-premise or at a remote site. One can also recover the secondary copy to the asset host directly from the target DD series via the source DM5500 UI. Metadata or replica metadata must be available to perform copy data recovery.
Now let's go over some of the prerequisites required to configure and set up this application. First and foremost, the DD Boost protocol needs to be enabled on the replication target, as well as file replication encryption should be enabled on both DM5500 and external Power Protect DD or DDBE. Just to note on DM5500, the DD Boost and file application encryption are enabled by default, but it's always good to verify that file application encryption is still enabled on the DM5500 while you're configuring the application and enable it on the target side as well.
Now let's go over the design and scope. Prior to R three, we could replicate DM5500 to itself (local replication) or to another DM5500 at a remote site. With R three release and the new proposed design, we loosen the restrictions. DM5500 can now replicate not only to another DM5500 but also allow external DDB or DDBE to be added as a replication target. This external D or DDB does serve as a centralized remote data center with large capacity and can hold data for longer retention.
Now, moving on to the demonstration of how we set up this application and create our secondary copies. First, we will log in as admin to our Power Protect Data Manager appliance UI, which is the DM5500 UI. We need to add the Power Protect Dell DD or DDB as the external replication target.
Before that, we would check our prerequisites. We see that replication encryption is turned on on the DM5500, which is by default. We'll go to our external Power Protect DD system and check regarding the DD Boost protocol as well as file replication encryption. For that, we'll go to protocols DD Boost. We see it was disabled, so we enable that. If we scroll down to the advanced section, we can check if file replication encryption is either enabled or disabled. We see it's disabled currently, which is how it is by default on an external D or DDBE. So we will enable it using the set options from more task and choose file replication DD encryption to enable it.
Once this is enabled, we will go back to our Power Protect Data Manager appliance to add the external Power Protect DD or DDB as the application target. We are going to add it by going to infrastructure storage under the application target tab. We need to provide a fully qualified hostname or the management IP of the external Power Protect DD or DDB and then click on verification, where it will do the certificate handshake and exchange the certificates to verify if everything looks good. If successful, it will proceed to add it as a replication target.
We see that the job has been kicked in for the initial discovery of the inventory source of the external Power Protect DD or DDBE. The job has been completed successfully, and we can check back in our infrastructure storage and replication target tab. It may take a while to reflect, but we will see that our replication target is all seen in green. Now, we see that replication encryption has been turned on on both sides, which is why we see that green check mark. If either side has the application turned off, we would see a red cross mark. So, as we've shown, you need to enable application encryption on both sides.
Next, we are going to set up the protection policy for the application. We will go to an existing protection policy and click on replicate to add and set up our application policy. We see the storage name, and our external DDBE has been added as the storage external storage since that’s the only replication target. Currently, you would see the application target: external Power Protect DD or DDB, as well as the Power Protect Data Manager appliance itself.
As mentioned, it is also possible to do a local application within the Power Protect Data Manager appliance. You will specify new so that it creates on its own automatically. Once we set up the application, it will create a new storage unit. We will set up all the schedules here. If we want to segregate the application traffic to a separate interface, we will select a different interface than that of management.
These are the interfaces from the target replication target Power Protect DD or DDBE. We will choose that from here and segregate our replication data traffic. We will set up the schedules and proceed further, but I’ll keep everything as default. You will see your replication target storage unit is currently seen as new because it will create a new storage unit for you once the application is set up, and we see that the job has been kicked in.
So, it has been completed now. Our application policy is all set up. We will do an ad hoc application to show how it looks like for the primary and secondary copies. You will see your storage name, your external Power Protect DD or DDB will be seen here. The new storage unit that it has created is seen here, and we will proceed further.
We see that the job has been kicked in to replicate our primary copies to the secondary external storage. It has started replicating, validating quest and storage system connections. It then tried to connect to the source and destination and started creating a list of copies before starting the replication process.
We will wait for it to complete. Our ad hoc application has been completed. If we go to the infrastructure asset and choose the asset we included in the replication policy, we will be able to see the primary copies. These are the primary copies, and if we see the other, these are the secondary copies here. We can see the hostname of the storage where the copies are residing.
So, this is our external Power Protect DDVE hostname and this is the Power Protect Data Manager appliance hostname. Here are the secondary and primary copies. This is how we are going to configure and set up our application. Thank you all for joining.
