Search This Blog

Saturday, December 9, 2017

Webinar: Office365 Monitoring and Dashboards in SCOM



With organizations transitioning to Office365 and moving their resources in the Cloud, IT Professionals started looking more and more into the possibility of having better visibility on their Office365 environment in SCOM.
NiCE-IT Management Solutions has recently released the new O365 Management pack, a highly anticipated software necessary for transitioning from Exchange and other on-premise services into Azure O365.
Join the webinar hosted with Nice-IT and learn how to:  
  • Live Maps, our powerful dashboarding solution that integrates with SCOM and OMS
    Deploy Nice-IT Management Pack for O365
    Monitor your O365 subscription and display in Live Maps dashboards
Our hosts Justin Boerrigter (Savision) and Christian Heitkamp (NiCE-IT Management Solutions) will walk you through a use case demo for specific scenarios as well.

Sign up now and mark your calendar for:
13 December
Europe 16:00 CET
North America 10:00 EST

Friday, November 17, 2017

Verify Backup Data to Avoid Silent Data Corruption in Backup Chain

How to avoid data corruption due to unavoidance circumstance due to hardware failure which use to keep your backup data?

You backup data may corrupt in the middle of the backup chain. Example:-

  • Full copy - Sunday
  • Incremental - Monday
  • Incremental - Tuesday
  • Incremental - Wednesday
  • Incremental - Thursday
  • Incremental - Friday
  • Incremental - Saturday
Corruption on Wednesday! :(

Accident due happen and you may not realize that your backup chain consists of corruption. It can be
Mechanical wear for tape or hard drives.

If you're using Veeam Backup & Replication, there are few things that you should do to avoid silent data corruption.

1. Modify Backup Job to "perform files health check (detects and auto heal corruption) based on schedule basic. [Under Maintenance Tab | Storage Level Corruption Guard]

 2. Create Surebackup Job to perform verification of your backup. You can enable "Validate entire virtual disk content (detect silent data corruption) [ Under Settings]


3. Use Veeam Validator to check your existing backup chain. Please refer to KB 2086:- https://www.veeam.com/kb2086

It is essential best practice to implement the 3-2-1 rule and always make 3 copies of data, store it on 2 different media and keep 1 copy on the disaster recovery site to avoid situations similar to the current one.

Hope this help.

Friday, October 27, 2017

Error 41106: Failed to Join the Availability Group for SQL Always On

If you encountered the following error when add replica to Availability Group

Error 41106


Try to turn off Windows firewall on both nodes. Open "Windows Firewall with Advanced Security".
Turn off Domain Profile
Turn off Private Profile
Turn off Public Profile


Retry to add again. Now you should be successful.

To open windows firewall traffic, create a new inbound rule | Add Port | 5022 | TCP | Apply to specific local ports: 5022

That should do the trick! 

Hope this work

Setup SQL Always On

Let build a SQL Always On...

Just follow the following steps to configure a high availability SQL Always On.

  • Node running Windows Server 2016
  • SQL Server 2012

Steps

1. Create a Windows Failover Cluster. Example 2 nodes

  • Node1
  • Node2

2. Install default standalone SQL instance on both nodes
3. Open SQL Server Configuration Manager, edit the Properties of SQL Server (MSSQLServer). On AlwaysOn High Availability tab, tick "Enable AlwaysOn Availability Groups and restart sql services



4. Open SQL Server Management Studio and Connect to SQL Server Instance
5. Create a new database first. Make sure that have performed a full database backup
5. Create a new availability group. Go to AlwaysOn High Availability | Availability Group | New Availability Group Wizard.



To create an availability group, you will need to:

  • specify an availability group name

  • select one or more user database

  • specify one or more instance of SQL Server to host secondary availability replicas

-Add Replica ->Select Node2
-Configure automatic failover
-set the synchronous commit
-set readable secondary




  • specify your availability group listener preference

  • select your initial data synchronization preference


-shared a folder.Make sure both nodes has Write permission Example:-
\\Node1\Shared


  • check the validation result of availability group creation

This will create and configure the SQL Always On Availability Group and join the database.

End result:-

Force Cluster Node from Quarantine to Normal State

By default, cluster node running on Windows Server 2016 enter to quarantine state when the node connectivity has an issue. The lock period is 7200 sec. (that will be 120 minutes).



To force the node to normal state, on quarantine node open Windows powershell to execute cmd
Start-ClusterNode - ClearQuarantine


Quarantine node will back to normal ("UP") status


If problem persist, please check on event viewer to identify the potential issue.

Wednesday, October 25, 2017

Uninstall Veeam Agent for Linux

The following is the command to remove Veeam Agent for Linux that install on Centos/RHEL/Oracle Linux/Fedora workload

Type:-
yum remove veeam veeamsnap



Thursday, October 19, 2017

Sneak Peak Project Honolulu-Web Based Management Solution

Project Honolulu is a new web-based management solution from Microsoft, build to modernize and simplify administration of your Windows datacenter. Currently under technical preview, to download click here:- https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-honolulu

After installation, you can start to Add Server that you would like to manage.



Added 3 servers: two running Windows Server 2016 and one running Windows Server 2016 Build 1709.


Based on our testing, we can manage the server, monitor performance utilization & basic administration.
Example:- Join to domain, restart server, shutdown, etc

Example:- Initialize new disk
 Example:- Format a volume
 Example:- Install Roles & Features
During our testing, the product is missing on the configuration of roles. Probably the product is still under "technical preview" & we may able to do it when the product is GA.

Give it a try if you're interested about this Project Honolulu.

Saturday, October 14, 2017

Backup Windows Server 2016 Hyper-V Over SMB

In this post, we are going to look on how to perform backup Windows Server 2016 Hyper-V Over SMB by using Veeam product. VM is residing on smb path.

My scenario:-

  • Host running Windows Server 2016 Hyper-V
  • VM on SMB 3.1.1 Files Shares
  • Veeam Backup & Replication v9.5 Update 2

To cut it short, we have documented the step by step on how to "Configure Hyper-V Over SMB" on this link:- http://www.ms4u.info/2012/11/configure-hyper-v-over-smb.html

In below video, you able to see how Veeam use Resilient Change Tracking (RCT), natively on Windows Server 2016 to perform backup.

Checklist:-
VM  run on SMB Path..........Passed
Full backup ..........................Passed
Incremental backup .............Passed