Replicating Volumes Between Servers in Windows Server 2025 with Storage Replica
ฝัง
- เผยแพร่เมื่อ 6 ก.พ. 2025
- In this video I configure storage replication between two Windows Server 2025 servers using Windows Admin Center.
➡️ Free Microsoft Active Directory Domain Services Applied Skill Credential: learn.microsof...
➡️ Windows Server 2025 What's New: learn.microsof...
➡️ Windows Server Hybrid Administrator Associate Certification: learn.microsof...
➡️ Windows Server 2025 Editions Comparison: learn.microsof...
➡️ Windows Server 2025 Locks and Limits: learn.microsof...
➡️ Azure Edition: learn.microsof...
➡️ More Windows Server videos: • Windows Server Videos
➡️ My social links: aka.ms/orin
#WindowsServer #windowsserver2025
Orin voice cloning done with: elevenlabs.io
Orin avatar trained with: heygen.com
VERY well done!
Time - 10.53. Why Data drive was not visible on B server, after you made example folder and file on server A? Drive was hidden on server B, until you make B server as primary? I just did not get idea, how this technology can be used in production.
It's a DR technology - so you can only read/write to one drive at a time. You switch over if you have a storage failure. There are other options such as Azure File Sync and DFS if you want to read/write to multiple file server nodes (say one in Sydney and one in Tokyo).
Could/would/should this replace DFSR for file server replication between two locations?
I'd replace DFSR with Azure File Sync - that way you can have active file shares at each location. This is more of a DR technology because the secondary isn't active until you switch direction or break the partnership.