How to Configure Storage Replica in Windows Server 2019

Video Series on Advance Networking with Windows Server 2019:
Step by step video on How to Install and configure Storage replica feature on Windows Server 2019 to setup Server to server storage replication.
1. Install storage replica feature on both member server.
2. Test Replication partnership.
3. Create a replication partnership.
4. Monitor replication performance.
Follow my blogs:
msftwebcast.com

[@shamilps]

Good and informative, please mention the use cases for the contents too, in this storage replica too u have explained and shown very well how to do it, but beginners still wont understand what is the use of the storage replica

[@MSFTWebCast]

Noted.

[@Oper8or]

Excellent information. You are the only channel I have alerts turned on for. Your work is much appreciated.

[@urke1987]

If the primary server is completely offline, is removing partnership the only way to unlock the secondary data volume? And if removed, can the partnership be rebuilt using the existing group?

[@asimsami9014]

Very Nice Explanation, thanks

[@prajeesh1986]

Windows server 2016
Test-SRTopology i get the following error could you please help
you are logged on to the source computer as a local user, not a domain user.
The destination computer is not running or is not accessible over the network.
You specified an incorrect name for the destination computer.
You specified an IP address for the destination server.
The destination computer firewall is blocking access to PowerShell and/or CIM calls.
The destination computer is not running the WMI service.
You did not use CREDSSP when running the Test-SRTopology cmdlet remotely from a management computer. N

[@sharonpoonen1278]

I have the same error

[@guptaramkumar52]

awesome knowledge, thank you for creating such video. how many drive we can configure in the storage replicate.

[@__SKYNET__]

Can you use this to sync a network drive from any other sever or does the other server have to be windows?

[@sharonpoonen1278]

Hello, unfortunately this did not work for me, after executing : Test-SRTopology -SourceComputerName server2 -SourceVolumeName R: -SourceLogVolumeName L: -DestinationComputerName server3 -DestinationVolumeName R: -DestinationLogVolumeName L: -DurationInMinutes 10 -ResultPath C:\sr-test\, I received an error : You specified ip address for the destination server, Only NetBios name allowed...
The destination computer not running.. I have configured as per your example.

[@__SKYNET__]

Is this a way to do a real-time sync?

[@liveomega3740]

hello Sir, Is there any way to get both the drivers (data driver-replica1 and replica2) to be accessible ?

[@jogiamit1]

Thanks for the nice explanation. Please confirm, whether Storage Replica will replicate corrupted files/folders or it will skip such corrupted data? Thanks.

[@MSFTWebCast]

I am pretty sure it also replicate corrupted data with the replication partner.

[@kirankumarbuddala5082]

Will you please provide this in document manner

[@jonathansartaguda8022]

What’s the prerequisite for dfs storage replica? Do you need to have AD? Does the Server need to be a member of an Active directory

[@MSFTWebCast]

Yes, Active Directory Forest is needed.
1. Windows Server 2019 is also required.
2. Minimum 2 GB RAM.
3. Two cores per Server.
More information: docs.microsoft.com/en-us/windows-server/storage/storage-replica/storage-replica-overview

[@hardick1991]

Why an extra log drive needed, even though i wanted to replicate 1 volume drive ? what's this log drive for ?
is it just to track the changes and updates ?.
If that the case can we use the same log drive to configure multiple disk to replecate on destination server using Storage Replica feature ?

[@GerbenWijnja]

It's good practise in general to have log files on a separate partition. If your operating system partition or data partition becomes 100% full (accidentally/unexpectedly), log files can still be written to, and you can still find out what happened, and what is currently happening. If the log files are on the partition that became 100% full, then log files can no longer be written or (if they are in a binary format) they can even become corrupted. It can also go the other way around, log files can fill up your OS partition. For example the IIS log files are by default in C:\inetpub\logs. I always relocate them to a different drive, to prevent C: from accidentally filling up and the server becoming unresponsive.

[@MrTechdude1]

Do you do freelance work? I have a small business and need AD/AD DS setup.

[@MSFTWebCast]

Not at the moment. But I can help over mail whenever possible...

[@ahmedsaad-lk2og]

thanks

[@marinmarinov1020]

indian accent.....

[@MSFTWebCast]

Cant change that mate.