Create an Arcserve Datastore for Replication on Unity for Immutable Snapshots – Part 1

Hello everyone.

Welcome to another in the series of how to videos with myself. Richard Hornsby, keeping with our special guest, Kevin Green, today we're looking at creating an arcserve data store for replication on Unity to allow immutable snapshots. So this is going to be part one. It's the three part series. We're going to go into a few different topics, but we're going to start here.

And on that, I will hand over to you, Kevin, so I'll stop sharing. And then if you can share your screen...

Noproblem. Yeah, that's come through. We're good to go. Lovely.

Hello everybody, and hope we're all well, right? Today, as Richard said, we're going to basically assign the LUN that we mapped to this server in a previous how to so from down here on ice, because the initiators, we've already got a target assigned, as we can see here from the actual drive assignments, we have our end drive, which is our one terabyte Lunt presented from the Unity so just so that this has already been created, already, from an arcs point of view, very straightforward.

We're going to go into the Ark's unified data protection main console. We're going to go to Resources, then we're going to come down to recovery point servers. Now this data store here is the local one. So this is the primary backup location. And if you notice, we're using 32k blocks, so to create another data store, to replicate the current one to the Unity, we just right click, or we could go actions, add a data store and we give it a name. So this time, I'm going to call it Nexsan. I need to give it a folder location for the actual data store folder, and this is known as the common. So I'm going to do browse, going to go to the end drive. There's nothing there at the moment, so click the yellow icon.

We call this one the common, and map that one.

Change the block size to the one that matches the original. This is not totally required, but it's recommended from best practice to have the block sizes the same. So we go to 32 we are going to put the hash on SSD. So then we go the Data folder, go to the end drive again, click the yellow folder, type data, make sure that's mapped. One last one for the index back to the end drive, click, type index, and finally, down here the hash location.

Now these three folders here are critical that they are on the Unity the reason for that is when you're doing recovery from an immutable snapshot or even just a standard VSS snapshot, these three folders are required to do data recovery. The hash is not and to make sure that the hash performs correctly when you're doing any kind of replication, we're going to place this
on the Y Drive.

Which in this case, is an SSD, which is why we've ticked it, we're going to turn on encryption, best practice. So type in a password that you require. Now, when you create this password, please make sure it's something you know. If you're not sure, copy it into Notepad and copy into here. The reason for that is later in another session, when we start bringing an immutable snapshot online, we are going to need this password, and if you don't know that password, we're not going to be able to import the immutable snapshot. So get that quick check over common block size, SSD, data, index, hash. It's encrypted. I'm going to do save.

Wait for a couple of seconds. As long as all those folders are empty, we have a new data store, and it's just starting. So from that point of view, we've in a previous session, we've mapped an iSchool on we've mapped it to the server, and we've now created a data store. The last thing we can do before we stop for today on this how to is get some data going to that new data store. So we're going to go to a plan. I've already labeled one here, so we're doing a backup, and then it's going to the Unity. So I'm going to edit this plan by just clicking on it, and I'm going to add a task.

So task one is to back something up.

Task Two is to check that data.

Task three, in this case, will be to replicate it to the Unity. And once we get that going, we're all done for this session.

Okay, so select a task, it's the replicate one. There's only going to be one destination, because there's only one free location, Nexsan schedule, the retention. I'm just going to leave it as default, and I'm going to do save. I could have changed the retention to be something more or less than the original. I can. Set up alerts and so on. But that's more to do with Arc serve than the actual Nexsan. Let's wait for it to complete. If I go back to all nodes, it's just deploying those changes to these servers.

Once that's actually finished, I can kick off some replication. I can do one server at a time, or in this case, I'm just going to do all of them at once.

Give that a couple more seconds, there we go. So I am just going to click all of these and do right click, replicate. Now this will start the process so we don't have to wait for a backup to occur. There you go, where to and where from Nexsan. So there we go, start the job. Okay? So once that kicks in, nothing more we could do until we've seeded some data to the Unity, and then we can look at immutable snapshots and then recovering those immutable snapshots in another how to.

That's it for today. Thank youbrilliant.

Thank you Kev Cheers All.