Skip to main content

Windows Server Essentials Training Part 5 - Storage Solutions

The course is in 6 sections, so I'll separate them by parts. I do have Windows Server experience, and 2019 is new to me, though the general idea is the same.

But first, a short refresher on volumes:

Partition table
 - Master Boot Record read by BIOS (Old, but still out there. If it works, it works!)
 - GUID Partition Table is read by UEFI (New!)

Disk Type
Basic Disks are divided into partitions (Which you can put different OSes on and boot them - Boot Partitions).

Dynamic Disks have volumes (Which can probably do the same thing. These have more flexibility). Has RAID arrays.



πŸ“₯ File Systems

NTFS - Huge maximum volume/file size. Has auditing.
FAT - Compatible with everything, but file/volume sizes leave a lot to be desired.
ReFS (From Server 2012) - Much the same as NTFS, with less overhead, and find file corruption while remaining online.

If you shrink volume size, you're changing the layout to the hard drive.

πŸ“₯Data Deduplication (Dedup)  - Save space as you store and access files without the performance hit from compression. Replace redundant bits of data on your drives. Pointers point you to the original product. In server roles, under file and storage services > File and iScSi services > Data Deduplication.

REMINDS ME OF..shortcuts on the desktop.

(NTFS and ReFS)


πŸ“₯ Storage Spaces Direct (S2D) -  Cluster servers for storage. Add it to Hyper-V to make a hyperconverged infrastructure. A number of servers that act as 1.

REMINDS ME (vaguely) OF... Hot Standby Routing Protocol but no server has to die for another to be used, and I feel that there is something else in Networking that it relates to more closely.


πŸ“₯ Storage Replica copies (replicates) volumes to other servers in the domain. The volume sizes should match.  You need a log volume that's still the same size, but not used for anything else.


Storage Migration Services
πŸ“₯  Orchestrator should be Server 2019 or newer, have the SMS proxy, and manages the migration.


πŸ“₯ Destination will accepts migration with configurations, and should be 2019/semi-annual Windows Server, with proxy role.


πŸ“₯ Source server should be at least Windows 2003. Wow, if you're still opening

Should be in same Active Directory, and admin rights on all machines. Configure firewall to allow tools.

Comments

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

 If you're seeing this post, I'm helping you, and you probably have LI presence: React and share this post to help me in return.   In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory