HCL - Pure Storage FlashBlade (SSD)

May 15, 2019, 12:16 pm

≫ Next: HCL - Pure Storage ObjectEngine VM Edition

≪ Previous: HCL - Pure Storage FlashBlade (Object)

Challenge

Product Information:

Company name: Pure Storage
Product Family: FlashBlade
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: Pure Storage FlashBlade
Drive quantity, size, type: 7 Blades / 8TB per blade - SSD
Firmware version: Purity//FB 2.1.0
General product family overview:

FlashBlade is a fast and dense unstructured data platform from Pure Storage that provides on-premise rapid backup and recovery of archival data. Additionally, Pure Storage FlashBlade provides high-performance in a dense-form factor for other unstructured data primary use cases such as machine learning, deep learning, and electronic design automation (EDA), among others.

Veeam testing configuration:

Note: The following settings were used by the vendor to meet Veeam Ready testing requirements and should not be considered best practices. Additional changes or settings may be needed to meet the storage efficiency or performance needs for each environment. For each setting, reference links are provided for further clarification.

Veeam Build Number: 9.5.0.823

Job Settings:

Deduplication:	Enabled (Default)
Compression:	Optimal (Default)
Storage Optimization:	Local Target (Default)

Repository Settings:

Repository Type:	Shared Folder (CIFS)
Align backup file blocks:	Disabled (Default)
Decompress before storing:	Disabled (Default)
Per-VM Backup Files:	Enabled

↧

HCL - Pure Storage ObjectEngine VM Edition

May 15, 2019, 12:17 pm

≫ Next: HCL - Red Hat Ceph Storage 3.1

≪ Previous: HCL - Pure Storage FlashBlade (SSD)

Challenge

Product Information:

Company name: Pure Storage
Product Family: ObjectEngine
Status: Veeam Ready – Object
Classification Description: Verified object storage solutions that has been tested with Veeam Backup & Replication Cloud Tier features.

Solution

Product Details:

Model number: ObjectEngine //A
Storage Category: Appliance
Drive quantity, size, type: ObjectEngine //A270 includes the minimum of 4 nodes. Nodes can be added to the cluster, in increments of 2, to provide additional throughput. ObjectEngine reduces the data inline (via deduplication and compression) as it’s being written to the permanent storage media. FlashBlade provides the underlying object storage and can be configured with a minimum of 7 and up to 15 blades per chassis, and each blade can be 17TB or 52TB of flash storage. Up to 5 FlashBlade chassis can be connected together.
Storage configuration: Tests were performed on 4-Node Pure Storage ObjectEngine //A270, with 15 blade (17TB per blade) FlashBlade using erasure encoding for unstructured data storage.
Firmware version: OES 5.0.0
Connection protocol and speed: 8x 10 GbE
Additional support: All models and configurations of ObjectEngine for S3 compatible storage with specifications equivalent or greater than the above.

General product family overview: ObjectEngine’s cloud-native technology reduces storage and bandwidth costs, enabling flash plus cloud solutions across a variety of use cases, including data protection. The FlashBlade solution provides an all-flash storage for this unstructured data platform.

Veeam testing configuration:

Veeam Build Number: 9.5.4.2753

Vendor recommended configuration:

Vendor Settings:

Array deduplication used during testing
Aray compression used during testing
Default S3 connection settings

↧

HCL - Red Hat Ceph Storage 3.1

May 15, 2019, 12:19 pm

≫ Next: HCL - Scality RING (Object Storage)

≪ Previous: HCL - Pure Storage ObjectEngine VM Edition

Challenge

Product Information:

Company name: Red Hat, Inc.
Product Family: Red Hat Ceph Storage
Status: Veeam Ready – Object
Classification Description: Verified object storage solutions that has been tested with Veeam Backup & Replication Cloud Tier features.

Solution

Product Details:

Model number: 3.1
Storage Category: Software Defined Storage
Drive quantity, size, type: 7 - 1TB SATA hard drives per cluster node, for a total of 21 drives across the cluster.
Storage configuration: Hard drives were all used in single, standalone mode. No hardware or software RAID used.
Firmware version: ceph version 12.2.5-59.el7cp
Connection protocol and speed: 1GbE
Additional support: All models and configurations of Red Hat Ceph 3.1 or higher for S3 compatible storage with specifications equivalent or greater than the above.

General product family overview:
Red Hat Ceph Storage 3.1 running on a 3-node cluster, with all nodes running the Object Storage Daemons (OSDs), and one node dedicated for the Monitor daemon (MON), Manager daemon (MGR), and Object Gateway daemon (RGW).

Veeam testing configuration:

Veeam Build Number: 9.5.4.2282

Vendor recommended configuration:

Vendor Settings:

No hardware deduplication used in testing
No hardware compression used in testing

↧

HCL - Scality RING (Object Storage)

May 15, 2019, 12:20 pm

≫ Next: HCL - SwiftStack Storage

≪ Previous: HCL - Red Hat Ceph Storage 3.1

Challenge

Product Information:

Company name: Scality
Product Family: Scality RING
Status: Veeam Ready – Object
Classification Description: Verified object storage solutions that has been tested with Veeam Backup & Replication Cloud Tier features.

Solution

Product Details:

Model number: Scality RING
Storage Category: Web-scale Software Defined Storage
Drive quantity, size, type: 156x 6TB NL-SAS, 12x 400GB SSD
Storage configuration: ARC 9+3
Firmware version: 7.4.2
Connection protocol and speed: 40GbE
Additional support: All models and configurations of Scality RING for S3 compatible storage with specifications equivalent or greater than the above.

General product family overview:
The Scality RING is software that turns any standard x86 servers into web-scale storage. With the RING, you can store any amount of data, of any type, with incredible efficiency and 100% reliability, guaranteed—all while reducing costs by as much as 90% over legacy systems.

Veeam testing configuration:

Veeam Build Number: 9.5.4.2753

Vendor recommended configuration:

Vendor Settings:

Jumbo frames used during testing
Storage Servers used in testing:6x Cisco UCS S3260 M4 Dual Node, 2x Intel(R) Xeon(R) CPU E5-2650 v4@ 2.20GHz, 128GB RAM

↧

HCL - SwiftStack Storage

May 15, 2019, 12:22 pm

≫ Next: How to decrease the OpsMgr Health Service load caused by datastore monitoring process.

≪ Previous: HCL - Scality RING (Object Storage)

Challenge

Product Information:

Company name: SwiftStack
Product Family: SwiftStack Storage
Status: Veeam Ready – Object
Classification Description: Verified object storage solutions that has been tested with Veeam Backup & Replication Cloud Tier features.

Solution

Product Details:

Model number: N/A
Storage Category: On-premise cloud-native storage
Drive quantity, size, type: 27 X 12 TB 10000 RPM hard disk drives (HDDs) are used per node to store objects and 1 X 400 GB SSD is used per node to store account information and metadata only
Storage configuration: 6-node cluster comprising UCS S3260 servers were used to test the solution
Firmware version: v6.24
Connection protocol and speed: 10GbE
Additional support: All models and configurations of SwiftStack Storage with specifications equivalent or greater than the above.

General product family overview:

SwiftStack is a cloud-native storage platform for managing unstructured data in a single namespace that is policy-driven and can scale across both private and public infrastructure. Supports all drive types. Size and quantity of drives per node will vary depending on deployment configuration and use cases. SwiftStack supports scale-out object storage clusters comprised of standard Intel-based servers, starting with 3 nodes or greater.

Veeam testing configuration:

Veeam Build Number: 9.5.4.2753

Vendor recommended configuration:

Vendor Settings:

Triple replicas and Erasure coding storage policy settings to protect data in the storage cluster.

↧

How to decrease the OpsMgr Health Service load caused by datastore monitoring process.

May 16, 2019, 2:32 am

≫ Next: Service plan is not found when adding Office 365 organization

≪ Previous: HCL - SwiftStack Storage

Challenge

Decrease the OpsMgr Health Service load caused by datastore monitoring process.

Cause

Since the datastore monitoring job currently cannot be split among several Veeam VMware Collectors, the amount of processed data may overload the Health Service in large VMware environments.

Tip:

To track the number of workflows running in the OpsMgr Health Service, you can use the Veeam MP for VMware > Veeam Collectors > Performance Views > Workflow Count view in the OpsMgr console. The number of workflows will be also displayed in the description of the Veeam VMware Collector: Health Service recommended workflow load monitor fired as soon as the recommended maximum number of OpsMgr Health Service workflows is exceeded.

Solution

To resolve the issue, configure Veeam MP for VMware discovery rules in OpsMgr in a way that will allow you to split the datastore monitoring job among several Health Services. To do that, deploy an additional Veeam MP for VMware instance (the Veeam Virtualization Extensions Service, Veeam Virtualization Extension UI and Veeam VMware Collectors).

Before you apply the solution, mind the following:

1. The version of the Veeam Virtualization Extensions Service (VE Service), Veeam Virtualization Extension UI (Veeam UI), Veeam VMware Collector (Collector) and Veeam Management Packs must be the same for both the existing and new Veeam MP for VMware deployments.
2. The accounts used to install and use Veeam MP for VMware must be granted the same privileges in both deployments. For more information, see the Veeam MP for VMware Installation Guide, section Accounts and Privileges.
3. The solution described below must not affect any setup or patching procedures.
4. If you want to use some of your existing Collectors for the new Veeam MP for VMware deployment, you must reinstall these Collectors and connect them to the new VE Service during the setup.

Case #1. There are several large vCenter Servers in your VMware environment.

In this case, deploy an additional Veeam MP for VMware instance (the VE Service, Veeam UI and Collectors) and assign a number of vCenter Servers to the new Collectors. This solution will decrease the load on the OpsMgr Health Service.
For more information on how to install Veeam MP for VMware, see the Veeam MP for VMware Installation Guide, section Installing Veeam MP for VMware.

Case #2. There is a large number of datastores on one vCenter Server.

In this case, deploy an additional Veeam MP for VMware instance and manually split datastores processed by the datastore monitoring job between several Health Services.
Note that this solution will decrease only the OpsMgr Health Service load — it does not affect the load on Collectors.

1. Deploy the 2nd instance of Veeam MP for VMware (the VE Service, Collector and Veeam UI components). For more information, see the Veeam MP for VMware Installation Guide, section Installing Veeam MP for VMware.
2. In the Veeam UI, set the EnableVMDiscovery parameter value to False for all Collectors installed in the 2nd deployment. For more information, see the Veeam MP for VMware Operations Guide, section Collector Settings.
3. In the OpsMgr console, create 2 groups for Collectors and 2 groups for Veeam VMware datastore containers. Add members to each group explicitly, or configure rules to enable dynamic membership.

If you decide to add members to groups explicitly, it is highly recommended to set the VE Service LoadBalanceOnCollectorRecovery parameter value to False. For more information, see the Veeam MP for VMware Operations Guide, section Extension Service Settings.

a. [For Collector groups with dynamic membership]
Create 2 groups for the Veeam VMware Collector Service object. Configure a rule that will automatically distribute Collectors between these groups based on the name of the VE Service to which each Collector is connected.
Specify the required VE Service name as the Extension Service property value in the Create Group Wizard – Query Builder. Alternatively, use the following formula to populate membership in each group: ( Object is Veeam VMware Collector Service AND ( Extensions Service Equals {VE Service name} ) AND True ).

Note:

If you later add a new Collector to your infrastructure, no additional actions are required. The new Collector will be automatically included in one of the created groups according to the configured rule.

b. [For Collector groups with explicit members]

Create 2 groups for the Veeam VMware Collector Service object. In the Create Group Wizard – Object Selection, manually add objects to these groups based on the name of the VE Service to which each Collector is connected.

Note:

If you later add a new Collector to your infrastructure, you will have to manually add the new Collector to one of the created groups.

c. [For datastore container groups with dynamic membership]
Create 2 groups for the Veeam VMware Datastore Container object. Configure a rule that will automatically distribute datastore containers between these groups based on the name of the VE Service to which each Collector gathering statistics on the containers is connected.

Specify the Veeam VMware Collector Service object and the required VE Service name as the Extension Service property value in the Create Group Wizard – Query Builder. Alternatively, use the following formula to populate membership in each group: ( Object is VMware Datastore Container AND ( Display Name Contains datastore ) AND True ) AND ( Object is Veeam VMware Collector Service AND ( Extensions Service Equals {VE Service name} ) AND True ) ).

Note:

If the number of datastores managed by the vCenter Server exceeds 100, the Collector that monitors datastores will create a new datastore container, and this container will be automatically included in one of the created groups according to the configured rule.

d. [For datastore container groups with explicit members]
Create 2 groups for Veeam VMware Datastore Container object. In the Create Group Wizard – Object Selection, manually add objects to these groups based on the name of the VE Service to which each Collector gathering statistics on the containers is connected.

Note:

If the number of datastores managed by the vCenter Server exceeds 100, the Collector that monitors datastores will create a new datastore container, and you will have to manually add this container to one of the created groups.

4. In the OpsMgr console, configure the following overrides. For more information on how to work with overrides, see Microsoft Docs.
To specify datastore names explicitly, use a comma-separated list (for example: Datastore01, Datastore02). To exclude a group of datastores, use the asterisk character (for example: ds1*, ds2*).

a. For the datastore container group created for the 1st VE Service, override the ExcludeDatastoreByDatastoreName parameter value for the Veeam Stage 2 - Datastore discovery rule. Provide names of datastores that you want to exclude from monitoring for the 1st deployment.
b. For the Collector group, created for the 1st VE Service, override the ExcludeDSRelByDSName parameter value for the Veeam Stage 2 - Virtual Machine discovery rule. Provide names of datastores that you want to exclude from monitoring for the 1st deployment.
c. For the datastore container group, created for the 2nd VE Service, override the ExcludeDatastoreByDatastoreName parameter value for the Veeam Stage 2 - Datastore discovery rule. Provide names of datastores that you want to exclude from monitoring for the 2nd deployment.
d. For the Collector group, created for the 2nd VE Service:

o Override the ExcludeDSRelByDSName parameter value for the Veeam Stage 2 - Virtual Machine discovery rule. Provide names of datastores that you want to exclude from monitoring for the 2nd deployment.
o Set the Enabled parameter value to False for the Veeam Stage 2 – Host components discovery rule.
o Set the Enabled parameter value to False for the Veeam Stage 2 - Virtual Machine discovery rule.

Important!

The list of datastore names must be the same for both the Veeam Stage 2 - Datastore discovery and Veeam Stage 2 - Virtual Machine discovery rules.

5. To verify whether you configured the overrides correctly, open Veeam Stage 2 – Host components discovery properties, switch to the Overrides tab and check that all parameters in the Overrides Summary list are set to False.

Note:

If you later add a new datastore to the vCenter Server, you will have to reconfigure the Veeam Stage 2 - Datastore discovery and Veeam Stage 2 - Virtual Machine discovery rules to exclude this datastore from monitoring for one of the deployments.

6. On the VMware Servers tab of the Veeam UI, for the 1st deployment, clear the check box next to the vCenter Server in the server hierarchy and wait until its objects disappear from the VMware topology in the OpsMgr console. Then select the check box again.
7. On the VMware Servers tab of the Veeam UI, for the 2nd deployment, select the check box next to the vCenter Server.

More Information

After you apply the solution, Veeam MP for VMware analysis and performance reports will have the following issue: each datastore included in both deployments will have a duplicate in the report scope list. This is a known issue that does not affect report functionality.

↧

Service plan is not found when adding Office 365 organization

May 8, 2019, 1:47 am

≫ Next: How to decrease the OpsMgr Health Service load caused by datastore monitoring process

≪ Previous: How to decrease the OpsMgr Health Service load caused by datastore monitoring process.

Challenge

Connecting to Office 365 organization fails with the “Check Exchange plan: No Exchange plan found” or “Check SharePoint plan: No SharePoint plan found” error.

Cause

Some of the Office 365 Exchange or SharePoint service plans assigned to the Office 365 Organization cannot be automatically identified as valid by Veeam Backup for Microsoft Office 365. This happens because assigned Office 365 plans are missing from the list of valid ones.

Solution

To resolve this issue, we need to add missing Plans IDs to the list:

First, get your current service plan ID. For example, you can do it via ‘MSOnline’ AzureAD module and the following PowerShell One-Liners:

To get the list of Exchange Online service plans IDs:

(get-msolaccountsku).servicestatus.serviceplan | where {$_.ServiceType -match "Exchange"} | ft ServiceName,ServicePlanId

To get the list of SharePoint Online service plans IDs:

(get-msolaccountsku).servicestatus.serviceplan | where {$_.ServiceType -match "SharePoint"} | ft ServiceName,ServicePlanId

Ensure that no jobs and restore sessions are running.
Stop the Veeam.Archiver.Service and the Veeam.Archiver.Proxy services.
Navigate to C:\Program Files\Veeam\Backup365 and edit the Config.xml file by adding the following lines between <Archiver> tags:

<Options>

<O365Plans AdditionalExchangePlans="your-Exchange-plans-IDs" />

</Options>

<Options>

<O365Plans AdditionalSharePointPlans="your-SharePoint-plans-IDs" />

</Options>

Start the Veeam.Archiver.Service and the Veeam.Archiver.Proxy services.
Open ‘Add organization’ wizard and re-try the procedure.

More Information

In case the issue persists after these changes, please, contact Veeam Support.

↧

How to decrease the OpsMgr Health Service load caused by datastore monitoring process

May 16, 2019, 3:33 am

≫ Next: Restoring domain controller from an application-aware backup

≪ Previous: Service plan is not found when adding Office 365 organization

Challenge

Decrease the OpsMgr Health Service load caused by datastore monitoring process.

Cause

Since the datastore monitoring job currently cannot be split among several Veeam VMware Collectors, the amount of processed data may overload the Health Service in large VMware environments.

Tip:

Solution

Note:

b. [For Collector groups with explicit members]

Note:

If you later add a new Collector to your infrastructure, you will have to manually add the new Collector to one of the created groups.

Note:

Important!

The list of datastore names must be the same for both the Veeam Stage 2 - Datastore discovery and Veeam Stage 2 - Virtual Machine discovery rules.

Note:

More Information

↧

Restoring domain controller from an application-aware backup

May 16, 2019, 12:26 pm

≫ Next: HCL - IBM Cloud Object Storage

≪ Previous: How to decrease the OpsMgr Health Service load caused by datastore monitoring process

Challenge

Application Aware Image Processing is required to be enabled and working as per Microsoft in order to functionally restore from a DC.

Since Active Directory implements multi-master replication, where multiple domain controllers sync changes with each other, one of the key challenges is the DC recovery process. This article outlines different DC restore scenarios and goes into some specifics of when and why this or that type of restore is required as well as gives instructions on the manual steps to perform proper DC recovery from backup created with Veeam B&R.

Before going into details, it is worth stressing that by default Veeam B&R performs automated non-authoritative restore of domain controller.

Depending on the scenario, different steps (or no steps at all) are required to perform DC restore. All of the scenarios assume application-aware image processing was enabled in the backup job that backed up the DC being restored.

Solution

Restoring single lost DC in a multi-DC environment or in environment with only a single DC

This scenario, actually the most common one, incurs restoring just one of the multiple DC’s when there are still other functional DC’s in the environment that the restored DC can replicate changes from.
DC recovery with Veeam B&R in this case is fully automated and does not require any user interaction. If your backup was done with application-aware image processing enabled in the backup job settings, Veeam B&R performs a non-authoritative restore of the DC, where the restored VM should first boot in Directory Services Restore Mode (DSRM) mode and then reboot automatically immediately to boot up next time normally.
The domain controller itself will understand that it has been recovered from backup and will allow normal replication to update everything that has been changed since the backup took place.
The automatic recovery should also work for environments with only a single DC.

Restoring entire AD infrastructure (AKA “all DC’s are lost”)

As mentioned above, the automatic recovery process performs a non-authoritative restore, where the DC reboots and starts looking for other DC’s to sync up. However, in a scenario where all DC’s are gone, there are no other partners available and replication may take quite long (15-30 minutes) to start. To avoid wasting the time attempting to contact replication partners, it is recommended to restore two of the domain controllers at once, power them on, wait for their reboot and force one of them to become authoritative for SYSVOL, so that they can start replicating. Then restoring other DC’s will be similar to the first scenario, i.e. will be 100% automatic.

Note: During the restore procedure, make sure the restored DC’s DNS records point to available DNS servers (e.g. to itself).

The procedure for designating DC as authoritative for SYSVOL varies based on whether FRS or DFS-R is used for SYSVOL replication. To determine if you are using FRS or DFSR for SYSVOL in the production environment check the value of the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\DFSR\Parameters\SysVols\Migrating Sysvols\LocalState registry subkey. If this registry subkey exists and its value is set to 3 (ELIMINATED), DFS-R is being used. If the subkey does not exist, or if it has a different value, FRS is being used.

If domain level is Windows 2008 or above you could also use the command dfsrmig.exe /getglobalstate to monitor if we are in the ‘ELIMINATED’ state and we are using DFSR.
If you are still using the FRS to replicate SYSVOL you need to perform an authoritative restore of the SYSVOL on first DC restored using burflags
To perform an authoritative restore of the SYSVOL when using FRS, use the following steps:

Start the Registry Editor
Navigate to "HKLM\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup"
Double-click on "BurFlags"
Assign it a value of D4 (hex) or 212 (dec)
Stop the NTFRS Service
Start the NTFRS Service

Or you can use the following commands

REG ADD "HKLM\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup" /v BurFlags /t REG_DWORD /d 212 /f
NET STOP NTFRS
NET START NTFRS

You could monitor the status of the replication by searching for the Event ID 13516
“The File Replication Service is no longer preventing the computer <Computer_name> from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL.”

If you are using DFS-R as the more widely used these days the steps to implement basically consist of setting the following registry values:

Key: HKLM\System\CurrentControlSet\Services\DFSR\Restore
Value: SYSVOL (REG_SZ) = “authoritative”

Key: HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\SystemStateRestore
Value: LastRestoreId (REG_SZ) = any GUID value (e.g. 10000000-0000-0000-0000-000000000000)

If the first restored DC already hosts operations master roles, set the following registry value in order to bypass initial synchronization requirements and not to wait for another partners to replicate the directory partitions:
Key: HKLM\System\CurrentControlSet\Services\NTDS\Parameters
Value: Repl Perform Initial Synchronizations (REG_DWORD) = 0

Note: Don’t forget to reset this value back to 1 after domain recovery is completed, so that domain controller has successful replication with its partners before starting to service client requests.

After setting the values above, restart the domain controller.

Notes:
• If you’re restoring DC without FSMO roles, you might want to transfer them to it manually after the restore, using the ntdsutil seize command.
• This type of restore is similar to what Veeam B&R performs automatically when restoring DC within SureBackup isolated virtual lab.

Restoring from Active Directory corruption

Scenario where no DC’s are actually lost, however, AD itself is damaged in some way (corrupt objects or schema) and you need to restore from the backup created before corruption occurred. In this case you need to restore one of the multiple DC’s when other DC’s are still operating a damaged copy of AD and force all of them to accept replication changes from the restored DC. This is where authoritative restore of the DC is required.

Note: It is recommended to perform restore with network disabled to prevent DC from accepting changes from other controllers after the default non-authoritative restore.
Note: For an easier item-level recovery of Active Directory objects (without the need to restore the domain controller itself), consider using Veeam Explorer for Active Directory.

To perform an authoritative restore:

1. Restore the DC and let it complete the default non-authoritative restore (wait until it reboots second time).
2. During this second boot, press F8 to get to DSRM mode.
3. Log in with DSRM account and password.
4. Open a command prompt and run ntdsutil command.
5. At the "ntdsutil:" prompt, type "authoritative restore" and press Enter.
6. To mark a single object as authoritative, type restore object <distinguished_name>, where <distinguished_name> is the DN of the object as determined in step 1.
To mark a subtree of objects as authoritative, type restore subtree <distinguished_name>, where <distinguished_name> is the DN of the subtree as determined in step 1.
This will mark the container object and everything it contains as authoritative. Note: If the DN contains one or more spaces, enclose the entire DN in quotes.
7. At the Authoritative Restore Confirmation dialog box, click Yes.
8. Upon restore completion, type "quit" and press Enter to exit the ntdsutil utility.
9. Reboot server.
10. Perform an authoritative restore of the SYSVOL, as was already discussed above.

More Information

Veeam recovery of a domain controller
Active Directory backup and recovery with Veeam
Recovering Your Active Directory Forest
Windows Server - How to Perform an Authoritative Restore of Active Directory Object
Restoring The SYSVOL (Non-)Authoritatively When Either Using NTFRS Or DFS-R (Part 1)
Restoring The SYSVOL (Non-)Authoritatively When Either Using NTFRS Or DFS-R (Part 2)
Restoring The SYSVOL (Non-)Authoritatively When Either Using NTFRS Or DFS-R (Part 3)

↧

HCL - IBM Cloud Object Storage

May 16, 2019, 2:02 pm

≫ Next: HCL - Amazon Simple Storage Service (Amazon S3)

≪ Previous: Restoring domain controller from an application-aware backup

Challenge

Product Information:

Company name: IBM
Product Family: IBM Cloud Object Storage
Status: Veeam Ready – Object
Classification Description: Verified object storage solutions that has been tested with Veeam Backup & Replication Cloud Tier features.

Solution

Product Details:

Object Storage Tiers: Standard, Vault, Cold Vault
Object Storage Service Description: IBM Cloud Object storage is an S3-compatible solution available from IBM Cloud or on-premises.

General product family overview:
IBM Cloud™ Object Storage makes it possible to store practically limitless amounts of data, simply and cost effectively. It is commonly used for data archiving and backup, for web and mobile applications, and as scalable, persistent storage for analytics. Flexible storage class tiers with a policy-based archive let you effectively manage costs while meeting data access needs.

Veeam testing configuration:

Veeam Build Number: 9.5.4.2753

↧

HCL - Amazon Simple Storage Service (Amazon S3)

May 16, 2019, 2:17 pm

≫ Next: Service plan is not found when adding Office 365 organization

≪ Previous: HCL - IBM Cloud Object Storage

Challenge

Product Information:

Company name: Amazon Web Services
Product Family: Amazon Simple Storage Service (Amazon S3)
Status: Veeam Ready – Object
Classification Description: Verified object storage solutions that has been tested with Veeam Backup & Replication Cloud Tier features.

Solution

Product Details:

Object Storage Tiers:

Amazon S3 Standard
Amazon S3 Standard-Infrequent Access
Amazon S3 One Zone-Infrequent Access

Object Storage Service Description: Amazon S3 One Zone-Infrequent Access

General product family overview:
Amazon Simple Storage Service (Amazon S3) is an object storage service that offers industry-leading scalability, data availability, security, and performance. This means customers of all sizes and industries can use it to store and protect any amount of data for a range of use cases, such as websites, mobile applications, backup and restore, archive, enterprise applications, IoT devices, and big data analytics. Amazon S3 provides easy-to-use management features so you can organize your data and configure finely-tuned access controls to meet your specific business, organizational, and compliance requirements.

Veeam testing configuration:

Veeam Build Number: 9.5.4.2753

↧

Service plan is not found when adding Office 365 organization

May 17, 2019, 5:46 am

≫ Next: Migrating VAO 1.0 Deployment to Version 2.0

≪ Previous: HCL - Amazon Simple Storage Service (Amazon S3)

Challenge

Connecting to Office 365 organization fails with the “Check Exchange plan: No Exchange plan found” or “Check SharePoint plan: No SharePoint plan found” error.

Cause

Solution

To resolve this issue, we need to add missing Plans IDs to the list:

First, get your current service plan ID. For example, you can do it via ‘MSOnline’ AzureAD module and the following PowerShell One-Liners:

To get the list of Exchange Online service plans IDs:

(get-msolaccountsku).servicestatus.serviceplan | where {$_.ServiceType -match "Exchange"} | ft ServiceName,ServicePlanId

To get the list of SharePoint Online service plans IDs:

(get-msolaccountsku).servicestatus.serviceplan | where {$_.ServiceType -match "SharePoint"} | ft ServiceName,ServicePlanId

Ensure that no jobs and restore sessions are running.
Stop the Veeam.Archiver.Service and the Veeam.Archiver.Proxy services.
Navigate to C:\ProgramData\Veeam\Backup365 and edit the Config.xml file by adding the following lines between <Archiver> tags:

<Options>

<O365Plans AdditionalExchangePlans="your-Exchange-plans-IDs" />

</Options>

<Options>

<O365Plans AdditionalSharePointPlans="your-SharePoint-plans-IDs" />

</Options>

Start the Veeam.Archiver.Service and the Veeam.Archiver.Proxy services.
Open ‘Add organization’ wizard and re-try the procedure.

More Information

In case the issue persists after these changes, please, contact Veeam Support.

↧

Migrating VAO 1.0 Deployment to Version 2.0

May 21, 2019, 8:52 am

≫ Next: HCL - Microsoft Azure Storage

≪ Previous: Service plan is not found when adding Office 365 organization

Challenge

Upgrade of Veeam Availability Orchestrator to version 2.0 is not supported. However, you have an option to migrate your VAO 1.0 configuration to version 2.0 with minimal downtime.

This KB article briefly describes architectural changes introduced in 2.0 version and provides step-by-step instructions on how to perform VAO migration.

Cause

The concept of VAO sites is no longer supported in version 2.0. To provide administrative role-based delegation, VAO now uses scopes. A scope is a logical unit introduced to determine operations that can be performed by VAO users and to define the items available to these users.

If you have a multi-server VAO 1.0 deployment and want to migrate to version 2.0, your main concern now is to configure a list of scopes that will match the preceding Production site configuration.

To learn more about VAO scopes, see the Veeam Availability Orchestrator 2.0 User Guide, section Managing Permissions.

Solution

Planning and Preparation

Make sure the machine on which VAO will be deployed has no other Veeam components installed, and meets the hardware and software requirements listed in the Veeam Availability Orchestrator 2.0 Deployment Guide, section System Requirements.
Make sure the accounts used to install and use the VAO solution have the permissions described in the Veeam Availability Orchestrator 2.0 Deployment Guide, section Required Permissions.
Make sure the ports used to ensure proper communication of VAO components are opened as described in the Veeam Availability Orchestrator 2.0 Deployment Guide, section Ports.
Make sure you have a valid license for VAO 2.0 that covers the required number of licensed VMs. Otherwise, you can obtain the latest license key either by logging in to the Veeam website using your credentials or by contacting our Licensing Department. To contact the Licensing Department, open the Veeam Support Resources webpage, click Submit a ticket, and select Licensing to receive assistance on Veeam licensing.
Make sure all Veeam Backup & Replication servers that you want to connect to VAO 2.0 run Veeam Backup & Replication version 9.5 U4 (build number 9.5.4.2615) or later.

New Installation

This scenario implies that you uninstall VAO 1.0 completely, and then install and configure VAO 2.0 from scratch.

This is the best option for those users who did not have Production sites in v1.0, and for those who can recreate all failover plans, perform initial configuration and recollect infrastructural data fast enough to avoid notable downtime.

Make sure that VAO agents are uninstalled from all connected standalone Veeam Backup & Replication servers in the VAO UI. For more information, see the Veeam Availability Orchestrator 2.0 User Guide, section Uninstalling VAO Agents. Make sure the “Force removal of Agent from VAO even if Veeam Backup & Replication server cannot be contacted” check box is not selected. If VAO is not able to access a Veeam Backup & Replication server, you can manually remove the required components from the server:
- Open Control Panel.
- Navigate to Programs and Features.
- In the list of installed programs, select Veeam Orchestrator Agent and click Uninstall.
To perform installation, follow the instructions provided in the Veeam Availability Orchestrator 2.0 User Guide, section Deployment.

Migration

This scenario implies that you have two side-by-side VAO deployments until the migration process is over, an old one (v1.0) and a new one (v2.0). Only one VAO deployment will be available for failover purposes, and you can expect a switchover period to involve downtime of all VAO services. This guide will help you minimize the switchover period the switchover period.

The migration process includes three phases:

Preparation of VAO 2.0 system — includes installation and initial configuration of VAO 2.0, with no impact on the running 1.0 system.
Switchover from VAO 1.0 to 2.0 — during this phase, neither VAO 1.0 nor VAO 2.0 can execute orchestration plans. This can be considered downtime for the DR system.
Testing of new VAO 2.0 system and decommission of VAO 1.0.

Preparation Phase

1. Install VAO 2.0. For more information, see the Veeam Availability Orchestrator 2.0 Deployment Guide, section Deployment.
Note that installation of VAO components on a machine already running standalone versions of Veeam Backup & Replication and Veeam ONE is not supported.

2. Connect vCenter Servers to VAO 2.0. For more information, see the Veeam Availability Orchestrator 2.0 User Guide, section Connecting VMware vSphere Servers.
Wait until VM Groups become visible in the VAO UI. Note that the VM group collection process may take significant time (up to 4 hours).
If you do not use vSphere tags to categorize VMs, create categorization rules the same way you created rules in VAO 1.0. To learn more about object categorization, see the Veeam Availability Orchestrator Group Management Guide.

3. Create scopes and assign the Plan Author role to users in these scopes the same way you assigned the Plan Author role to users for Production sites in VAO 1.0. For more information, see the Veeam Availability Orchestrator 2.0 User Guide, section Managing Permissions.

4. For each created scope, include the required VM groups the same way you configured Production site groups in VAO 1.0. For more information, see the Veeam Availability Orchestrator 2.0 User Guide, section Including VM Groups.
5. For each created scope, include the required plan steps the same way you configured Production site steps in VAO 1.0. For more information, see the Veeam Availability Orchestrator 2.0 User Guide, section Including Plan Steps.

6. Configure plan steps the same way you configured steps in VAO 1.0. For more information, see the Veeam Availability Orchestrator 2.0 User Guide, section Configuring Parameter Settings.
7. Specify SMTP and email notification settings the same way you configured settings in VAO 1.0. For more information, see the Veeam Availability Orchestrator 2.0 User Guide, section Configuring Notification Settings.

8. Create subscriptions for each scope. For more information, see the Veeam Availability Orchestrator 2.0 User Guide, section Subscribing to Notifications.
9. Configure report templates the same way you configured templates in VAO 1.0. For more information, see the Veeam Availability Orchestrator 2.0 User Guide, section Managing Templates.

In VAO 2.0, clone the Default template. Open the new template in MS Word.
In VAO 1.0, navigate to the template you want to copy Open the template in MS Word.
Copy the text of VAO 1.0 template and paste it into the newly created 2.0 template.
Save the 2.0 template.

Switchover Phase

10. Manually stop all running failover plans and lab tests in VAO 1.0.

●   To learn how to perform the undo failover operation, see the Veeam Availability Orchestrator 1.0 User Guide, section Undoing Failover.
●   To learn how to finalize failover, see the Veeam Availability Orchestrator 1.0 User Guide, section Finalizing Failover.
●   To learn how to reset failover plans, see the Veeam Availability Orchestrator 1.0 User Guide, section Resetting Failover Plans.

11.Disable all scheduled failover plans and lab tests in VAO 1.0 (Manage > Disable).
12. To allow reversion to VAO 1.0 in case of unsuccessful migration, you have to manually uninstall VAO agents from all connected Veeam Backup & Replication servers used in VAO 1.0. For each server, do the following:

Open Control Panel.
Navigate to Programs and Features.
In the list of installed programs, select Veeam Orchestrator Agent and click Uninstall.

13. Connect the standalone Veeam Backup & Replication servers to VAO 2.0. For more information, see the Veeam Availability Orchestrator 2.0 User Guide, section Connecting Veeam Backup & Replication Servers. Make sure all Veeam Backup & Replication servers that you want to connect to VAO 2.0 run Veeam Backup & Replication version 9.5 U4 (build number 9.5.4.2615) or later.
14. Wait until VAO collects the necessary data from the Veeam Backup & Replication servers: all discovered DataLabs and credentials must become available in VAO UI Note that in some cases the data collection process may take significant time (up to 4 hours).
15. For each created scope, include the required credentials the same way you configured Production site credentials in VAO 1.0. For more information, see the Veeam Availability Orchestrator 2.0 User Guide, section Including Credentials.
16. For each created scope, include the required template jobs the same way you configured Production site jobs in VAO 1.0. For more information, see the Veeam Availability Orchestrator 2.0 User Guide, section Including Template Jobs.
17. Assign DataLabs to the created scopes. For more information, see the Veeam Availability Orchestrator 2.0 User Guide, section Assigning DataLabs.
18. Create and configure new failover plans the same way you configured plans in VAO 1.0. For more information, see the Veeam Availability Orchestrator 2.0 User Guide, section Working with Failover Plans.

Testing and decommission of VAO 1.0 phase

Before decommissioning your VAO 1.0 installation, it is recommended that you make sure readiness checks and DataLab tests can complete successfully. If not, you can still revert to 1.0 (as described below).

19. Run readiness checks for the newly created failover plans. For more information, see the Veeam Availability Orchestrator 2.0 User Guide, section Running Plan Readiness Check.
20. Run DataLab tests for the newly created failover plans. For more information, see the Veeam Availability Orchestrator 2.0 User Guide, section Testing Failover Plans.
21. If all readiness checks and DataLab tests complete successfully, you can uninstall VAO 1.0 from the DR server and from all Production servers. For more information, see the Veeam Availability Orchestrator 1. Deployment Guide, section Uninstalling VAO.

Revert to VAO 1.0

If some of the readiness checks or DataLab tests fail to complete successfully, you can revert to the VAO 1.0 deployment by connecting Veeam Backup & Replication Servers back to VAO 1.0:

a) Manually stop all running failover plans and lab tests in VAO 2.0.

●   To learn how to perform the undo failover operation, see the Veeam Availability Orchestrator 2.0 User Guide, section Undoing Failover.
●   To learn how to finalize failover, see the Veeam Availability Orchestrator 2.0 User Guide, section Finalizing Failover.
●   To learn how to reset failover plans, see the Veeam Availability Orchestrator 2.0 User Guide, section Resetting Failover Plans.

b)   Disable all scheduled failover plans and lab tests in VAO 2.0 (Manage > Disable).

c)   Uninstall VAO agents from all connected standalone Veeam Backup & Replication servers in VAO UI. For more information, see the Veeam Availability Orchestrator 2.0 User Guide, section Uninstalling VAO Agents. Make sure the "Force removal of Agent from VAO even if Veeam Backup & Replication server cannot be contacted" check box is selected.

d)   Make sure VAO agents are uninstalled from the Veeam Backup & Replication servers. If not, you can manually remove the required components from the servers:

Open Control Panel.
Navigate to Programs and Features.
In the list of installed programs, select Veeam Orchestrator Agent and click Uninstall.

e) For each Veeam Backup & Replication server connected to VAO 1.0, repair its VAO agent in the VAO UI (Configuration > VAO Agents > Repair).

Wait until VAO collects the necessary data from the Veeam Backup & Replication servers: all discovered DataLabs and credentials must become available in VAO UI.

↧

HCL - Microsoft Azure Storage

May 24, 2019, 11:22 am

≫ Next: HCL - Quest Software, Inc. - QoreStor

≪ Previous: Migrating VAO 1.0 Deployment to Version 2.0

Challenge

Product Information:

Company name: Microsoft
Product Family: Azure Storage
Status: Veeam Ready – Object
Classification Description: Verified object storage solutions that has been tested with Veeam Backup & Replication Cloud Tier features.

Solution

Product Details:

Object Storage Tiers: Cool / Hot
Object Storage Service Description: Azure Storage

General product family overview:
Get scalable, cost-effective cloud storage for all your unstructured data. Choose from among storage tiers, depending on how often you’ll access the data. Store performance-sensitive data in frequently accessed data in Hot or infrequently accessed data in Cool.

Veeam testing configuration:

Veeam Build Number: 9.5.4.2753

↧

HCL - Quest Software, Inc. - QoreStor

May 24, 2019, 11:31 am

≫ Next: HCL-Scality-RING (Archive)

≪ Previous: HCL - Microsoft Azure Storage

Challenge

Product Information:

Company name: Quest Software, Inc.
Product Family: QoreStor
Status: Veeam Ready – Archive
Classification Description: Verified disk archive storage that can be used as a Backup Copy target. Synthetic full backups, granular restores, and vPower features may not provide sufficient performance or be supported.

Solution

Product Details:

Model number: ADISTEC-M
Storage Category: Software Defined Secondary Storage
Drive quantity, size, type: 6 – 3.49TB SAS SSD
Storage configuration: RAID5
Firmware version: V5.1.0 Build 377
Connection protocol and speed: CIFS, 10 GbE x 2 Bonded ALB
Additional support: All models and configurations of QoreStor ADISTEC-M with specifications equivalent or greater than the above

General product family overview:
Software-defined secondary storage platform for backup. ... Your storage will shrink with QoreStor deduplication. Accelerate backups and add replication, variable block deduplication, and direct to storage backup by using QoreStor with Veeam Software.

Veeam testing configuration:

Veeam Build Number: 9.5.4.2753

Job Settings:

Deduplication:	Enabled (Default)
Compression:	Dedupe Friendly
Storage Optimization:	Local Target (Default)

Repository Settings:

Repository Type:	Shared Folder
Align backup file blocks:	Enabled
Decompress before storing:	Disabled (Default)
Per-VM Backup Files:	Enabled

Vendor recommended configuration:

Hardware Settings:

Jumbo frames used on network configuration for testing (MTU=9000)
Array deduplication used during testing – yes
Array compression used during testing – yes

↧

HCL-Scality-RING (Archive)

May 29, 2019, 7:28 am

≫ Next: Release Information for Veeam Availability for Nutanix AHV 1.0 Update 2

≪ Previous: HCL - Quest Software, Inc. - QoreStor

Challenge

Product Information:

Company name: Scality Ring
Product Family:
Status: Veeam Ready – Archive
Classification Description: Verified disk archive storage that can be used as a Backup Copy target. Synthetic full backups, granular restores, and vPower features may not provide sufficient performance or be supported.

Solution

Product Details:

Model number: Scality Ring
Storage Category: Scale-out File and Object Storage
Drive quantity, size, type: 72 – 1TB 7200 RPM HDD, 6 – 500GB SSD
Storage configuration: ARC 9+3
Firmware version: 7.4.0.0
Connection protocol and speed: CIFS - 10GbE
Additional support: All models and configurations of Scality Ring with specifications equivalent or greater than the above.

General product family overview:

The Scality RING is software that turns any standard x86 servers into web-scale storage. With the RING, you can store any amount of data, of any type, with incredible efficiency and 100% reliability, guaranteed—all while reducing costs by as much as 90% over legacy systems.

Veeam testing configuration:

Veeam Build Number: 9.5.0.1536

Job Settings:

Deduplication:	Enabled (Default)
Compression:	Optimal (Default)
Storage Optimization:	Local Target (Default)

Repository Settings:

Repository Type:	Shared Folder
Align backup file blocks:	Disabled (Default)
Decompress before storing:	Disabled (Default)
Per-VM Backup Files:	Enabled

Veeam recommended Backup Copy Job Configuration:

Only full backup copy jobs are recommended to archive data to Scality
"Read the entire restore point from source backup instead of synthesizing it from increments"

Vendor recommended configuration:

Hardware configuration used

Storage Servers : 6x HPE Apollo 4530 Chassis, Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz, 128GB RAM
Connector Server : 1x VM, 8x vCPU Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz, 32GB RAM

↧

Release Information for Veeam Availability for Nutanix AHV 1.0 Update 2

May 30, 2019, 5:47 am

≫ Next: Veeam Backup & Replication - Steps to Compile and Upload Logs

≪ Previous: HCL-Scality-RING (Archive)

Challenge

Release Notes for Veeam Availability for Nutanix AHV 1.0 Update 2.

Solution

Please refer to Release Notes to get detailed information on the new version.

More Information

[[DOWNLOAD|DOWNLOAD UPDATE|https://www.veeam.com/send_license/availability-nutanix-ahv/]]

SHA1: 7e617620dc4d1dccd5ae0c14c7de9be78ea8cafa05160c5bce813b721ece0a1e
MD5: d5ff5a658dae5b1efe08a97c167daf1c

↧

Veeam Backup & Replication - Steps to Compile and Upload Logs

May 30, 2019, 8:48 am

≫ Next: Microsoft Azure Government Cloud support

≪ Previous: Release Information for Veeam Availability for Nutanix AHV 1.0 Update 2

Challenge

If you are a Cloud Provider gathering logs from your infrastructure please see: https://www.veeam.com/kb2096

This article covers how to properly compile your logs in Veeam Backup & Replication v8.x and v9.x, as well as what to include when submitting a Support case for technical assistance.

Solution

The following animation demonstrates how to compile logs in Veeam Backup & Replication.

User-added image

To compile your logs via the log compilation wizard, click the Menu button in the top left-hand corner of the gui and go to Help -> Support Information in the Veeam Backup & Replication console.
This wizard will allow you various methods to compile logging. For Backup, Replication, and other jobs, select “export logs for this job.” If multiple jobs are affected, you can multiple-select. For problems with restore or replica failover, you should select “Export logs for this VM” and choose the production VM that was backed up or replicated. For issues with the GUI or problems that don’t fall into any of the above categories, select “Export all logs for selected components” and choose “This server.”
If possible, compile the logging for each job with issues for at least the last week.
You may save these logs to any location. Ensure that the location referenced has free space for compilation.
When selecting "Next", the wizard will notify of its progress in the compilation process. Please attach these to your case, or in the event that the total attachment size is under 3.5MB, you may attach via email reply. If none of these options for upload are working, please notify Veeam Support and an engineer will provide FTP credentials for the case.

Below is an animation demonstrating how to upload logs to the Veeam Support FTP.

Note: Please use the FTP account provided to you by the engineer for your case. When submitting logging data for analysis by request of an engineer, ensure that the case is replied to when the log submission has completed. In this reply, please include the names of any tasks and associated VMs with issues.

User-added image

Note: SFTP is now supported when uploading to supportftp2, please place files in the \upload\ folder.

More Information

Below are the relative log path lists for Veeam Backup & Replication. If there are difficulties compiling the logging requested via the wizard-based instructions above, please obtain the files from the appropriate directory below and provide Veeam Support a .zip file copy.

Windows 2003, XP – C:\Documents and Settings\All Users\Application Data\Veeam\Backup\
Windows Vista, 7 - C:\Users\All Users\Veeam\Backup\
Windows 2008/2008 R2/2012 - C:\ProgramData\Veeam\Backup\
Linux - /var/log/VeeamBackup/

Typical log files requested for a manual log compilation will be:

The task's folder located in the parent directory, zipped. This will contain all relevant job/task/agent data.
All logs from the parent directory named svc.*.log, util.*.log, as well as the VeeamBackupManager.log and VeeamShell.log

Please note that information provided to Veeam for purposes of customer support may be considered protected under certain data protection regulations and/or internal company policies. A list of potentially sensitive data types is available in the following KB article. Veeam will only utilize this information for the specific purpose of providing customer support to you and will protect the information in accordance with its privacy policy. In any event, the information provided will be securely deleted after 45 inactive days as of the last upload to the FTP. If you would like it deleted sooner, please express this request directly to your support contact once the issue has been resolved. For more information on how we process the collected data, please visit: https://vee.am/processing_of_personal_data

↧

Microsoft Azure Government Cloud support

May 30, 2019, 10:21 am

≫ Next: Red Hat Enterprise Linux kernel 2.6.32-754.6.3 is not supported by Veeam Agent for Linux

≪ Previous: Veeam Backup & Replication - Steps to Compile and Upload Logs

Challenge

Direct Restore to Azure functionality does not support Microsoft Azure Government Cloud.

Cause

Microsoft Azure Government Cloud requires a different Azure environment configuration that Veeam Backup & Replication 9.5 Update 3 does not implement out of the box.

Solution

Please perform upgrade of Veeam Backup & Replication to version 9.5 Update 4.

More Information

[[DOWNLOAD|DOWNLOAD UPDATE|https://www.veeam.com/download_add_packs/vmware-esx-backup/9.5.4.2753.update4a/]]
MD5: 9E7438488FFD10B8F804EE2B8C8C03CF
SHA1: D5F888D81426AC3648E6E0BB0412F63003A26517

↧

Red Hat Enterprise Linux kernel 2.6.32-754.6.3 is not supported by Veeam Agent for Linux

June 5, 2019, 1:27 am

≫ Next: Re-IP issues: Win2008R2 with VMXNET 3 Adapter

≪ Previous: Microsoft Azure Government Cloud support

Challenge

Veeam Agent for Linux may cause an operating system crash on machines running Red Hat Enterprise Linux (RHEL) or its derivatives (CentOS, Oracle Linux) with Linux kernel version 2.6.32-754.6.3.el6 (update RHSA-2018:2846).

Cause

Veeamsnap, Agent for Linux kernel module is not compatible with Linux kernel version 2.6.32-754.6.3.el6.

Solution

The issue is specific to kernel version 2.6.32-754.6.3.el6. For details please refer to the following article: https://access.redhat.com/solutions/3658111
This issue is addressed in the following kernel updates: Red Hat Enterprise Linux 6.10.z - kernel-2.6.32-754.9.1.el6 via RHBA-2018:3763.
Workaround: boot the system from kernels earlier than kernel-2.6.32-754.6.3.el6.

↧