Loading ...

Category: Network Attached Storage (NAS)

Synology Active Backup Restore to Hyper-V

Prerequisites:

  • Make sure Hyper-V Host has CPUs than the combined total of CPUs for all servers being restored as these static until after the VMs are completely restored. If there is not enough CPU resources then the VMs will not boot.
  • Make sure Hyper-V Host has more than the combined total of RAM for all servers being restored as these settings are static until after the VMs are completely restored. If there is not enough memory then the VMs will not boot. 
  • Create a SET NIC Team on the server (if you have multiple NICs)
    • Open Powershell as administrator
    • User the New-VMSwitch command to setup an external virtual switch to connect to for live connections
      • New-VMSwitch -name “SET team” -NetAdapterName “NIC1″,”NIC2” -AllowManagementOS $True
      • The AllowManagementOS is needed if you are using the same NIC team to access the VM host
  • Setup secondary Internal vSwitch to allow for testing before deploying
  • Setup Synology LUN targets for each VM to be restored. Make sure that they are big enough to hold all the full uncompressed size of the entire thick provisioned hard drives for the entire server. 
  • Connect each LUN to the iSCSI Initiator on the VM Host. Make sure to bring them online, initialize them, and give them a drive letter. Synology needs this because it uses the SMB protocol to transfer the files during restore.
  • Make sure to allow the File and Printer Sharing app through the Windows firewall and open port 5986 to allow HTTP traffic for WinRM to allow Synology to query the Hyper-V settings.
  • Add the Hyper-V Host to the Active Backup for Business app.

Synology Active Backup Restore to Hyper-V

  1. Open the Active Backup for Business app
  2. Click on the Physical Server tab on the left
  3. Select the server and click the Restore button
  4. Select the point in time to restore from Graphical user interface, text, application, chat or text message Description automatically generated
  5. Choose Restore to Microsoft Hyper-V
  6. Choose Full Virtual Machine Restore
  7. Change the Restore Name
  8. Select a folder on the Hyper-V Host to place the configuration files Graphical user interface, text, application, chat or text message Description automatically generated
  9. Select a folder on the Hyper-V Host to place each of the restore VHD files
  10. Select a Virtual Switch on the Hyper-V Host to connect the VM to Graphical user interface, text, application Description automatically generated
  11. Confirm the settings by clicking on the Done button.

After:

  • The VMs will boot with a single NIC and no network settings. Keep them offline and add additional NICs as needed to match the original setup. Then configure the NICs as before upon reboot. Make sure to connect to Internal Test Switch for initial steps. 
  • Check hardware configuration of CPUs and RAM to determine if adjustments can be made. In particular, the RAM settings can be changed to startup, minimum, and maximum to allow for distribution of resources to VMs that have heavier workloads.
  • Boot VM to make sure it is functioning correctly.  (first bootup can take upwards of 15 minutes)
  • Convert the VM from Gen1 to Gen2
    • Download Windows 10 ISO – https://www.microsoft.com/en-us/software-download/windows10
    • Add Windows ISO to IDE controller as CD 
    •  Set boot to CD in VM Settings 
    • Boot VM to repair section of CD 
    • Boot to command prompt
      • diskpart 
      • list disk   (Make boot disk is in 0 spot)
      • exit
      • X:\>mbr2gpt /validate /disk:0 (select proper disk) 
      • X:\>mbr2gpt /convert /disk:0 
    • Create new VM with Gen2 setting
      • Give the VM a name and Store in appropriate iSCSI LUN drive then Click Next 
      • Select Gen 2 and click Next
      • Give the VM as much startup memory as needed and Use Dynamic Memory then Click Next Graphical user interface, text, application, email Description automatically generated
      • Select the Internal Test Switch and click Next
      • Select an existing hard drive and point to boot drive that was converted to Gen 2 then click Next Graphical user interface, text, application, email Description automatically generated
      • Click Finish to create
      • Modify to match old VM
        • Check Dynamic RAM settings to make sure the Max / Min is set properly
        • Check Hard drives and add additional as needed
        • Turn off Secure Boot function
  • Boot new Gen 2 VM and configure static IP address.
  • If booting successfully then delete Gen 1 VM 
  • Turn of old server as needed
  • Change Gen 2 VM to use SET Team vSwitch 
  • Test connectivity to network resources. 

If your company is looking to migrate from physical to virtual servers, then contact us to make the transition easy.

Tier 3 / Co-Managed IT- Macrium Reflect Restore to Synology VM

This was a strange one, but I have done it now more than once for a Tier 3 / Co-Managed IT client. They use the Macrium Reflect software to do image backups of client servers. They are looking to virtualize these servers going forward and wanted to know if it was possible to restore from Macrium Reflect to a Synology VM. Here is the process that we found to make it work:

Assumptions

  1. We assume that you already have a Synology device setup and functioning properly.
  2. We assume that you already installed the Virtual Machine Manager app on the Synology
  3. We assume you already went through the initial setup wizard of the Virtual Machine Manager app
  4. We assume that you have been backing up the server and have a valid image backup file
  5. We assume you know the network path to these backup files
  6. We assume you already know (and possess on the Synology) the required amount of CPU, Memory, and HDD space.

Process

  1. Create Macrium Reflect bootable Rescue media
    1. Open Macrium Reflect
    2. Click on the Restore tab
    3. Open Other Tasks on the left hand side
    4. Choose Create bootable Rescue media
    5. Browse to where the current backups are stored and save it there (this makes finding everything easier later)
    6. Click Build (You may need to install some pre-requisites to make this possible, but Macrium Reflect with prompt you for it)
  2. Create Virtual Machine
    1. Open the Synology Virtual Machine Manager app
    2. Click on Image
    3. Click on the Add button
    4. Find the Macrium Reflect Rescue media and add it to local storage
    5. Click on Virtual Machine on the left
    6. Click the Create button
    7. Choose the Microsoft Windows option (if appropriate)
    8. Select the proper storage amount
    9. Give it a name, CPU, Memory (as needed)
    10. Give it the needed storage amount(s)
    11. Leave it connected to the default network
    12. Download the Synology Guest Tools if needed.
    13. Select Macrium Reflect Rescue media for the ISO file for bootup
    14. Do not start the automatically
    15. Edit the VM and change it to start from the CD ROM
    16. Power it on
  3. Restore from backup
    1. Connect to the VM
    2. Wait for Macrium Reflect Rescue media to boot (this can take awhile)
    3. Click on the blue computer icon at the bottom
    4. Click on the Map Network Drive icon
    5. Type in need information and click OK
    6. Go back to the Macrium Reflect window
    7. Click on Browse for an image or backup file to restore
    8. Find the appropriate file in the newly mapped network drive
    9. Click on Restore Image
    10. Select the target drive(s)
    11. Click Next, Finished
    12. Wait for restore to complete (this will take a long time)
  4. Prepare restored image
    1. Once completed, click on the ReDeploy restored image to new hardware
    2. Add drivers if needed
    3. Accept any drivers it finds
    4. Accept the default options
    5. Finish the wizard by closing
    6. Power off the VM
    7. Edit the VM Storage to make the disk a SATA controller instead
    8. Edit the VM Others to make the BIOS UEFI
    9. Edit the VM Network to Not Connected
    10. Power on the VM
    11. Login and install the Synology Guest Tools from the attached CD-ROM drive
    12. Power off the VM
    13. Edit the VM Network to use the default connection
  5. Power on the VM if you are ready to deploy

If your company is looking to virtualize your servers or take them to the cloud, then contact us to setup migration evaluation.

Tier 3 / Co-Managed IT- Synology DNS Server loses Domain Name Resolution

Got a email from one of our co-managed IT / Tier3 / managed RMM clients that was having issues with DNS resolution. The network consists of a Synology NAS acting as Domain Controller / DNS Server and a VM on the Synology that runs the clients main application. Several of the workstations were having an issue where they could not browse to the IP address (\\192.168.0.11\sharename)of the application server at one time and could not browse to the UNC path (\\servername\sharename) of the same server on another day. First tried setting the external forwarders to Google DNS and the Forward Policy to Forward First, but the problem resurfaced. So we dug deeper into the DNS settings and found the following:

If you look closely the IP address of the server is 192.168.0.11 and the records for DNS servers associated with the domain above and below it point to servers outside the subnet of the application server (10.0.0.2). Upon further investigation this DNS server address was blocked by the firewall because it was an old IP address scheme that was no longer in use. The current good DNS server IP addresses are 192.168.40.10 and 192.168.0.10.

Turns out the stale DNS records were the problem. Made the needed changes to the DNS records and things are working great.

If your company needs a little extra help running the IT department, then contact us to setup a co-managed IT evaluation.

Synology Active Directory Server

Synology Active Directory Server - Grants Pass, OR

Recently provided some assistance to a local IT company that exclusively uses Synology devices instead of servers for their clients. They approached us to create Group Policy objects based on this new feature of the Synology. The Synology Active Directory Server app is based on the Samba 4 Protocol, here are some details of available features:

  • Support for Windows RSAT
  • Support for TLS domain controller certification
  • Support for custom NetBIOS domain names
  • DNS auto registration
  • Support for single domain controllers

Account & Privileges

  • Group membership and policies
  • Roaming user profiles
  • Account single sign-on
  • Home folder support

Security & Access Control

  • Kerberos-based authentication
  • Password reset via email
  • Password strength policies
  • Account lockout policies

Domain Clients

  • Microsoft Windows 7 and above
  • Linux

Take Aways

Here are some basic take-aways from our experience creating these Group Policy Objects (GPO) on the Synology Active Directory Server.

  1. Need to install Remote Server Administration Tools (RSAT) on the most up-to-date desktop or server OS version in the organization to allow for best compatibility with all earlier OSs when creating GPOs
  2. Need to modify Synology Active Directory Server control panel Domain Options to allow Domain Admins to have admin access – without this you will get Access Denied every time a GPO is attempted to be added
  3. Windows Servers, Active Directory and domains are not dead, they are just becoming a “Container” which makes them much cheaper for small businesses to adopt.

If your company is utilizing a Synology Network Attached Storage device and would like the functionality of an Active Directory domain, then contact us for assistance.

Missing Western Digital MyCloud Drive

Recently took over an account from another tech and was informed by the client that their Western Digital MyCloud drive was unreachable and they had not been able to access their files shared their with the computers in the office for some time. Since the MyCloud is just a simplified Network Attached Storage (NAS) device for the home / SMB market, I decided to go onsite and find out what was causing the issue.

How to find a missing MyCloud

I first investigated the shortcuts that were sitting on the desktop to figure out what was going wrong with the drive or if there were some bread crumbs as to where it was previously. Found one called Dashboard which pointed to an IP address on their current subnet that went nowhere – this was likely the former IP address of the device. Found a shortcut to the “Public” folder which pointed to an IP address that was on another subnet than theirs – this was likely from a setup before another network change and had not been removed since then. Found another shortcut to the “Public” folder which pointed to the same IP address on their current network  as the Dashboard shortcut, so this confirmed that this was the last known IP address.

Ran a network scan using my personal favorite, SoftPerfect Network Scanner, to discover what was on the current subnet and if the MyCloud was still functional at another IP address. Found that the IP address for the device had changed to another similar address, so figured that it was getting its IP address from DHCP and when the old address lease ran out it just grabbed another one from the router. Checked the router and found that indeed the DHCP table contained the IP address for the device, so added a DHCP reservation to the router for that devices MAC address mapping it to the old IP address to make the broken shortcuts work again. Tested opening the dashboard and “Public” folders successfully which thankfully still had all of their information intact.

The final thing to do was to correctly set permissions within the device for each of the users and corresponding user folders within the device to allow them to connect and “backup” their documents to the device like they were used to. Although I would not recommend using this type of device to any of my clients, it was good to get this company backup up and running successfully. If your company is using Western Digital MyCloud drive for shared file access or are considering adding file shares to your network, then contact us for assistance.

Archives

Categories

Plant a Seed @ 541-761-9549
233 Rogue River Hwy #873 Grants Pass, OR 97527
Mon-Fri: 9:00am-5:00pm
support@farmhousenetworking.com
© 2016-2023- Farmhouse Networking. All rights reserved
Terms and Conditions Privacy Policy

Evaluation Signup

[contact-form-7 id="452" title="Free Network Evaluation"]