Quantcast
Channel: Veeam Support Knowledge Base
Viewing all 4470 articles
Browse latest View live

Collecting Diagnostic Information for Veeam Agent for Microsoft Windows

$
0
0

Challenge

This KB article shows how to collect the diagnostic information that may be needed if you create a Veeam Agent for Microsoft Windows support case.
 

Cause

Once you have gathered all the logs required for troubleshooting, you will need to attach them to the case through the customer portal or to the ftp site using the ftp information provided to you by the engineer assigned to your case. Please, notify the engineer once the logs are uploaded. 

If you need to use a secure FTP, this article contains secure FTP instructions.

Solution

How to gather the Veeam Agent for Microsoft Windows product logs

The Veeam Agent for Microsoft Windows logs can be located in the path below on the machine where the product is installed.
 
C:\%programdata%\veeam\endpoint
 
You will need to zip up the entire Endpoint folder.
 

How to gather Microsoft VSS information

You will need to run the commands below from an Administrative command prompt on the system that is having issues:
 
vssadmin list writers > C:\vss_writers.log
vssadmin list providers > C:\vss_providers.log
vssadmin list shadows > C:\vss_shadows.log
vssadmin list shadowstorage > C:\vss_shadow_storage.log

They will create four log files named vss_writers.logvss_providers.logvss_shadows.log and vss_shadow_storage.log in C:\. Once submitted to Veeam Support, these logs can be deleted.
 

How to gather Microsoft Event logs

You will need to export the logs in .evtx format. An .evtx file alone does not contain the text of most events, so uploading an .evtx file without the associated Display Information can delay the resolution of your support case. You will need to export the System and Application logs as follows:
 
1. Open Event Viewer (eventvwr.msc).
2. Locate the log to be exported in the left-hand column.
3. Right-click the name of the log and select Save All Events As.
4. Enter a file name that includes the log type and the server it was exported from.
For example, when exporting the Application event log from a server named HV01, enter Application_HV01.
5. In Save as type, select Event Files.
6. Include the display information.

User-added image

7. Be sure to include the LocaleMetaData folder when packaging the logs for upload.

User-added image


How to gather File System Minifilter information

You will need to run the command below from an administrative command prompt on the system that is having issues:
 
fltmc instances > C:\filter.log

A log named filters.log will be created in C:\. Once submitted to Veeam Support, this log can be deleted.

HCL - Quest DR4300

$
0
0

Challenge

Product Information

Product Family: DR Series Disk Backup Appliances 
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: DR4300 
Number of Drives: 12 
Drive type: 4TB 
Firmware version: 4.0.0.3 
Connection protocol and speed: 10 GbE 
Additional support: CIFS Shared Folder with RD Accelerator Driver Installed Version = 4.0.543.3 
General product family overview: The DR Series system is a high-performance, disk-based backup and recovery appliance that is simple to deploy and manage and offers unsurpassed Total Cost of Ownership benefits. Features such as innovative firmware and an all-inclusive licensing model ensure optimal functionality and provide the assurance of no hidden costs for valuable future features. DR Series Appliances are 2U, rack-based, system backup storage repositories that include deduplication and compression technology in their operating systems featuring exclusive client-side CIFS and NFS acceleration technology that enables client-side deduplication, iSCSI, encryption at rest, and seamless expandability. 

 

Veeam Details

Veeam Build Number: 9.5.0.1038 
Veeam Settings:  

  • Repository Type: CIFS 
  • Deduplication: No 
  • Compression: None 
  • Storage Optimization: Local target – 16TB+ 
  • Per-VM Backup Files: Yes 
  • Decompress before storing: Yes 
  • Align backup file blocks: Yes 

More Information

Company Information

Company name: Quest 
Company overview: At Quest, our purpose is to solve complex problems with simple solutions. We accomplish this with a philosophy focused on great products, great service and an overall goal of being simple to do business with. Our vision is to deliver technology that eliminates the need to choose between efficiency and effectiveness which means you and your organization can spend less time on IT administration and more time on business innovation. 

HCL - Dell EMC Isilon

$
0
0

Challenge

Product Information

Product Family: Dell EMC Isilon 
Status: Veeam Ready Repository 
Classification Description: Verified backup storage that supports all Veeam backup and restore features. 

Solution

Product Details

Model number: All 
Number of Drives: Any 
Drive type: Any 
Firmware version: OneFS 8.0 and newer. By design, Isilon has a 4TB max file size limitation in this firmware. We suggest using a software load balancer with it as referenced in KB2221.
Additional support: Any EMC Isilon configuration with supported firmware. 
General product family overviewDell EMC Isilon scale-out NAS is the ideal platform to store, manage and protect unstructured data efficiently while supporting a wide range of applications and workloads.  

 

Veeam Details

Veeam Build Number: 9.5.0.823 
Veeam Settings:  

  • Repository Type: Shared folder (or Linux Repository when used with General Storage dsmISI load balancer software - see KB2221)
  • Deduplication: ON
  • Compression: Optimal 
  • Storage Optimization: LAN Target 
  • Per-VM Backup Files: ON (Required)
  • Decompress before storing: OFF 
  • Align backup file blocks: OFF

More Information

Company Information

Company name: Dell EMC 
Company overview: Dell EMC, a part of Dell Technologies, enables organizations to modernize, automate and transform their data center using industry-leading converged infrastructure, servers, storage and data protection technologies. This provides a trusted foundation for businesses to transform IT, through the creation of a hybrid cloud, and transform their business through the creation of cloud-native applications and big data solutions. Dell EMC services customers across 180 countries – including 98 percent of the Fortune 500 – with the industry’s most comprehensive and innovative portfolio from edge to core to cloud. 

HCL - NexentaStor

$
0
0

Challenge

Product Information

Product Family: NexentaStor 
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details

Model number: NexentaStor 
Number of Drives: 24 SAS
Firmware version: 5.1
Additional support: Any NexentaStor with the listed firmware, including an equal or greater quantity of disk drives 
General product family overview: NexentaStor delivers unified file (NFS and SMB) and block (FC and iSCSI) storage services, runs on industry standard hardware supporting all-flash, hybrid, and all-disk scaling from tens of terabytes to petabyte configurations, and includes all data management functionality by default through an easy to deploy and use graphical user interface.  More information about NexentaStor can be found at https://nexenta.com/products/nexentastor 

 

Veeam Details

Veeam Build Number: 9.5
Veeam Settings:  

  • Repository Type: Shared Folder 
  • Deduplication: OFF
  • Compression: Optimal 
  • Storage Optimization: Local target
  • Per-VM Backup Files: ON 
  • Decompress before storing: OFF 
  • Align backup file blocks: OFF

More Information

Company Information

Company name: Nexenta 
Company overview: Nexenta is the global leader in Open Source-driven Software-Defined Storage (OpenSDS) with 6,000+ customers, 400+ partners, 42 patents, and more than 1,500 petabytes of storage under management. Nexenta uniquely integrates deep software-only “Open Source” collaboration with one of the largest and most vibrant Open Source communities (46,000 members) and a comprehensive vision around a commodity hardware-centric “Software-Defined Storage” innovation enabling ANY app, cloud platform and protocol. Nexenta is 100% Software-based; and 100% hardware-, protocol-, cloud platform-, and app-agnostic providing organizations with Total Freedom protecting them against punitive “vendor-lock-in”, “vendor-bait-n-switch”, and “vendor-rip-n-replace” gimmicks. Nexenta provides enterprises with the "true" benefits of “true” Software-Defined Everything-centric Cloud Computing.

HCL - SUSE Enterprise Storage v5 SDS

$
0
0

Challenge

Product Information

Product Family: SUSE Enterprise Storage 
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: SUSE Enterprise Storage 5 
Number of Drives: 15 
Drive type: 2TB SATA 
Firmware version: SDS GA 
General product family overview: For most enterprise-level businesses, the demand for data storage is growing much faster than the average price for storage is shrinking. That means you'll be forced to increase your budget dramatically to keep up with your data demands. However, there is another answer—SUSE Enterprise Storage. This intelligent software-defined storage solution, powered by Ceph technology, enables you to transform your enterprise storage infrastructure to reduce costs while providing unlimited scalability. 

 

Veeam Details

Veeam Build Number: 9.5.0.1038
Veeam Settings:  

  • Repository Type: Windows 
  • Deduplication: Yes 
  • Compression: Optimal 
  • Storage Optimization: Local target 
  • Per-VM Backup Files: No 
  • Decompress before storing: No 
  • Align backup file blocks: No 

More Information

Company Information

Company name: SUSE 
Company overview: We adapt.  You succeed. 

HCL - QSAN XCubeSAN XS3200

$
0
0

Challenge

Product Information

Product Family: XCubeSAN 
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: XS3200 
Number of Drives: 8 
Drive type: SSD 
Firmware version: 1.2.1 
Connection protocol and speed: iSCSI 10 GbE 
General product family overview: QSAN XCubeSAN XS3200 series is the high performance, simple, secure, scalable, and affordable SAN storage systems for enterprise and SMB. It is an ideal solution to the applications of mission critical data center, virtualization integration, media and entertainment, or large scale surveillance; and also backup and disaster recovery in enterprise, SMB or ROBO (Remote Office/Branch Office) deployments. 

 

Veeam Details

Veeam Build Number: 9.5.0.1038 
Veeam Settings:  

  • Repository Type: Windows 
  • Deduplication: Yes 
  • Compression: Optimal 
  • Storage Optimization: Local target 
  • Per-VM Backup Files: No 
  • Decompress before storing: No 
  • Align backup file blocks: No 

More Information

Company Information

Company name: QSAN 
Company overview: QSAN Technology, leading storage technology designer and manufacturer, was founded in July 2004. Building on our vast experience in the industry, QSAN strives to build enterprise class storage systems that pride ourselves with outstanding performance, secure data protection and comprehensive data management. QSAN endeavors to provide the industry with high quality data storage systems that are simple, secure, scalable and reliable. For more information, please visit www.QSAN.com 

Restoring GPT Disk to Incompatible Legacy BIOS System

$
0
0

Challenge

After selecting a restore point during the bare metal restore configuration, the following message pops up:
 
OS disk in backup uses GPT disk.  This may cause boot issues on BIOS systems.

User-added image

If this is ignored and the restore process completes, the following may happen when the restored machine boots up:
 
No boot disk found
or
An operating system wasn’t found

Cause

Due to compatibility issues between GPT formatted partitions and legacy BIOS systems, certain systems that can only run in legacy BIOS are unable to recognize the formatted boot partitions. This prevents the system from successfully booting to the underlining operating system.

Solution

To resolve the compatibility issues, it is necessary to format the System partition correctly as outlined in the following steps.

1. Boot the Recovery Media.
2. Go to Tools and start command prompt utility.
3. Run the following commands one by one:
 
diskpart

list disk    

At this step, find the disk you are going to use as a restore destination. In this example, we'll use disk 0.     
select disk 0

NOTE: The 'clean' command erases the selected disk completely.
clean
convert mbr

create partition primary size=100

select part 1

format fs=ntfs label=”System reserved” quick

active

assign letter=S

The '​exit' command will take you out of the diskpart utility.
exit
  

Close the command prompt.

4. Start the restore. While allocating the volumes do not delete the system reserved partition.
5. Do not reboot once restore is completed.
6. Go back to Tools > Command Prompt utility.
7. Run the following commands one by one.
 
diskpart

find the volume with restored operating system. In this example it’s going to be volume C
list vol

exit from disk part utility
exit

8. Once you exit the diskpart context, run the following command in the command prompt: 
 
bcdboot C:\Windows /S S: //volume letter I got from previous list volume in disk part

9. Reboot and start the restored OS.

More Information

If the system does allow for both MBR and GPT partitions, check with your vendor whether this can be changed in the BIOS settings of the system.

Repository Unavailable to Veeam Agent for Microsoft Windows Installed on a Veeam Backup and Replication Server

$
0
0

Challenge

The behavior described here can be observed in the following configuration:

- multiple installations of Veeam Agent for Microsoft Windows (VAW) are targeted at a Veeam Backup and Replication (VBR) repository within the same domain;
- all VAW-processed computers are added to an AD computer group;
- the mentioned group is used to manage Agent Backup Permissions to access the repository.

This configuration works fine for all VAW installation except the one on the VBR server.

Cause

During the authentication on the same machine, Kerberos authentication is not used, thus making the repository unavailable for the local installation of VAW.

Solution

A group which contains NT AUTHORITY\SYSTEM account should be added to the Agents Backup Permissions.

By default, the BUILTIN\Administrators group contains the Local System account.

Changing Default Ports for Veeam Availability Console Websites

$
0
0

Challenge

It may be necessary to change the default ports for Veeam Availability Console Web UI or Veeam Availability Console RESTful API websites.

Cause

Follow the steps below to change the default ports.

Solution

1. On the server hosting the Web UI and RESTful API websites run the IIS Manager by accessing Administrative tools > Internet Information Services (IIS) Manager. Other ways of accessing IIS Manager are shown here.

2. Select a website that requires port change:

User-added image

3. In the pane on the right in the Edit Site section click Bindings.

4. In the pop up window, select a binding and click Edit:

User-added image

5. Set the new port and Save:

User-added image

More Information

If you have any questions, contact Veeam Support.

Disabling collection of historical performance data

$
0
0

Challenge

If the Veeam ONE Monitor Server service was stopped for some time or a new vCenter server has just been added, Veeam ONE attempts to import past performance data for this time interval from vCenter Server.

When a large volume of past performance data is imported or there are gaps in the data staged to be imported, Veeam ONE may sometimes stop responding. In this case (and in some other situations), it may be deemed reasonable to disable collection of past performance data.


 

Solution

To disable automatic import of historical performance data in Veeam ONE, complete the procedure outlined below:
 
1. Log onto the Veeam ONE server, then open the services.msc and stop both the Veeam ONE Monitor Server and Veeam ONE Reporter Server services.
 
2. Open regedit and navigate to the following registry path:
 
HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam ONE Monitor\Service
 
3. Modify (or add if not already present) the following values in this location:
 
Name:  MedPerfQueryPeriod
Type:   DWORD
Value:  0
 
Name:  LowPerfQueryPeriod
Type:   DWORD
Value:  0
 
4. Start both the Veeam ONE Monitor Server and Veeam ONE Reporter Server services.

 
Note: Please be aware that configuring Veeam ONE in this way will result in Veeam ONE not automatically recovering performance data missed during any monitoring outage. Additionally, performance graphs and reports will contain gaps in data for corresponding to any monitoring outages.

More Information

If you have any questions or problems, please contact Veeam Support at http://www.veeam.com/support.html
 

High Veeam ONE Database IOPS Index

$
0
0

Challenge

Starting with version 9, Veeam ONE database server shows high IOPS usage of approximately 700-800 operations per second with regular spikes exceeding 2500 operations every 5 minutes.

Cause

As a real-time monitoring solution, Veeam ONE actively performs input-output operations against its database. Version 9 uses modified monitoring engine. Data collection and database data writing procedures have been overhauled, increasing the list of collected performance counters, the number of operations per second in regards to SQL database and WMI. The data are collected and written to the database using sophisticated algorithms for processing performance data and alarms.

The aforementioned processes cause relatively stable IOPS index with regular 5-minute spiking that references to the frequency with which bulk insert into the database takes place.

Solution

This behavior is by design. Possible solutions to balance the load include:
  • Migrating Veeam One database to a dedicated datastore to minimize the impact on other applications
  • Changing the Scalability mode as per KB2017

More Information

If you have any questions, contact Veeam Support

How to enable storage-specific API logging

$
0
0

Challenge

Need to collect storage-specific API logging by Veeam Customer Support request.

Cause

This extended logging level isn't enabled by default and its control varies from storage system to storage system.

Solution

Storage-specific API logging could be enabled via one of the following registry values. You need to enable only one that is specific to your storage. Please create them on the Veeam machine where Veeam Backup Service is running:
 
HPE 3PAR StoreServ:
Name: LogWsApiFullDetails
Type: REG_DWORD
Value: 1
Path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\
 
NetApp FAS, FlexArray (V-Series), Edge VSA and IBM N Series (NetApp FAS OEM)
Name: NetAppDetailedLogging
Type: REG_DWORD
Value: 1
Path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\
 
Nimble Storage AF-Series and CS-Series
Name: NimbleAPILogDetails
Type: REG_DWORD
Value: 1
Path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\
 
Dell EMC VNX, VNX2, VNXe and Unity
Name: VNXAPILogDetails
Type: REG_DWORD
Value: 1
Path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\
 
Cisco HyperFlex
CiscoHXLogRestAPI
Type: REG_DWORD
Value: 1
Path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\

Failed to send heartbeat to controller

$
0
0

Challenge

Veeam Backup for Microsoft Office 365 Backup jobs fail with the following error:
 
Timestamp 12 (9572) Connecting to organization...
Timestamp 12 (6688) Failed to send heartbeat to controller
Timestamp 12 (6688) Error: Access is denied.

Timestamp 42 (9572) Found: Veeamuser, SMTP: Veeamuser@veeam.com
Timestamp 42 (9572) Trying to obtain license for Veeamuser@veeam.com
Timestamp 42 (9572) Failed to obtain license
Timestamp 42 (9572) Error: Access is denied

Cause

Proxy ID has not been properly reformed during Veeam Backup for Office 365 upgrade from version 1.0 to 1.5

Solution

  1. Stop Veeam Backup for Microsoft Office 365 Service and Veeam Backup Proxy for Microsoft Office 365 Service
  2. Delete С:\Programdata\Veeam\Backup365\ProxyDb\ and C:\Programdata\Veeam\Backup365\Proxy.xml from Proxy Server
  3. Start Veeam Backup Proxy for Microsoft Office 365 Service*
  4. Start Veeam Backup for Microsoft Office 365 Service
  5. Proxy ID should be synchronized - run the backup
*It is vital to have Veeam Backup Proxy for Microsoft Office 365 Service started before Veeam Backup for Microsoft Office 365 Service, since Controller has the proper information that should be propagated to newly created Proxy database and not a vice-versa.
 

HCL - DataCore SANSymphony 10.0

$
0
0

Challenge

Product Information

Product Family: DataCore SANSymphony 
Status: Veeam Ready - Repository 
Classification Description: Verified backup storage that supports all Veeam backup and restore features 

Solution

Product Details

Model number: SANSymphony 
Number of Drives: 4 
Drive type: 450GB SSD 
Firmware version: 10.0 
Connection protocol and speed: 10GB iSCSI 
General product family overview

SANsymphony 
https://www.datacore.com/products/datacoresansymphony 
DataCore™ Hyper-converged Virtual SAN 
https://www.datacore.com/products/datacorehyper-converged-virtual-san 
Both products (above) are share a common code base, implementation use case and license keys differentiate products. 

 

Veeam Details

Veeam Build Number: 9.5.0.1038 
Veeam Settings:  

  • Repository Type: Windows 
  • Deduplication: Yes 
  • Compression: Optimal 
  • Storage Optimization: Local Target 
  • Per-VM Backup Files: Yes 
  • Decompress before storing: No 
  • Align backup file blocks: Yes 

More Information

Company Information

Company name: DataCore Software Corporation 
Company overviewhttps://www.datacore.com/company/about 

 

HCL - Huawei OceanStore 9000 NAS

$
0
0

Challenge

Product Information

Product Family: Huawei OceanStor 
Status: Veeam Ready – Repository 
Classification Description: Verified backup storage that supports all Veeam backup and restore features. 

Solution

Product Details

Model number: 9000 Scale-Out NAS Storage System 
Number of Drives: 24 
Drive type: 600GB SAS 
Firmware version: V300R006C00SPC100 
Connection protocol and speed: 10GbE 
General product family overview: Huawei OceanStor 9000 Scale-out NAS Storage is a scale-out NAS storage system specifically designed for massive data storage. Employs a fully symmetric distributed architecture, supports either file or object storage, and delivers superior performance, extensive scale-out capabilities, and super-large single file system for unstructured data storage.  Widely applied in media, satellite mapping, gene sequencing, energy exploration, scientific research, education, backup and archiving. 

 

Veeam Details

Veeam Build Number: 9.5.0.1038
Veeam Settings

  • Repository Type: Shared Folder 
  • Deduplication: Yes 
  • Compression: Optimal 
  • Storage Optimization: LAN Target  
  • Per-VM Backup Files: Yes 
  • Decompress before storing: No 
  • Align backup file blocks: No 

More Information

Company Information

Company name: Huawei Technologies Co., Ltd. 
Company overviewhttp://www.huawei.com/en/ 


An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full

$
0
0

Challenge

After installing Windows April update KB4015553 Veeam jobs and services fail at different operations with:
 
"An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full"

Cause

This particular update (and all consequent rollups that include it) causes the system to run out of free RPC ports when there are failed iSCSI connections.

Solution

Repairing or removing unsuccessful iSCSI connections, followed by the server reboot, was found to fix the issue. Additionally, remove any unused targets from the ‘Favorite Targets’ tab that are associated with these connections as they may be reconnected after reboot.

This issue has been addressed by Microsoft. Apply the appropriate update below to resolve the issue

For 2016:           https://support.microsoft.com/en-us/help/4025334
For 2012 R2:      https://support.microsoft.com/en-us/help/4025335

-------------------------------------------------------------------------------------------------------------------------------------------------

The update that resolved the above Buffer Space iSCSI issue (KB4025335) has caused another iSCSI issue that only affects Backup from Storage Snapshots using an iSCSI connection.
 
After installing Windows Update KB4025335, KB4034681, KB4025333, or KB4025336, Veeam jobs utilizing Backup from Storage Snapshots using an iSCSI connection fail with the following errors:
 
“Error: Cannot retrieve physical extents for connecting iSCSI target IQN iqn.2007-11.com.nimblestorage:lun-nim-oracle-veeam-lun-nim-oracle-v069a713ff86811d1.000000d1.fef260ee.s069a713ff86811d1.000000de.0000b1cb on proxy IQN iqn.1991-05.com.microsoft:mtl-s-fs0005.solotech.local”
 
In the logs, it can be seen with this error:
 
Task Log:
“[25.07.2017 09:44:54] <61> Error Failed to find physical drive for LUN with lun Id 'WwnOrIqn: 'iqn.1992-04.com.emc:cx.apm00140946425.a1', LunId: '10',
 
[25.07.2017 09:44:54] <61> Error Unable to retrieve devices for iSCSI session. number of retry attempts: '20'. Interval: '100'. (Veeam.Backup.Common.CCppComponentException)
[25.07.2017 09:44:54] <61> Error in c++: void __thiscall disklib::vmfs_san::iscsi_api::iscsi_discovery::GetDevicesForSessionWithRetry(struct _ISCSI_UNIQUE_SESSION_ID &,class std::vector<struct ISCSI_DEVICE_ON_SESSIONW,class std::allocator<struct ISCSI_DEVICE_ON_SESSIONW> > &,int,int) failed.
[25.07.2017 09:44:54] <61> Error in c++: void __thiscall disklib::vmfs_san::iscsi_api::iscsi_discovery::LoginTarget(const class std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class std::allocator<wchar_t> > &,class std::vector<struct disklib::vmfs_san::iscsi_api::IscsiDriveInfo,class std::allocator<struct disklib::vmfs_san::iscsi_api::IscsiDriveInfo> > &) failed.”

 
 
Proxy Resources Log:
 “[04.08.2017 13:50:55] < 4016> cli| VMFSSAN.ConnectISCSITarget
[04.08.2017 13:50:55] < 4016> cli| (EString) TargetName = iqn.1992-04.com.emc:cx.apm00140946425.a1
[04.08.2017 13:50:55] < 4016> cli| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[04.08.2017 13:50:55] < 4016> dsk| Retrieving devices for target 'iqn.1992-04.com.emc:cx.apm00140946425.a1'.
[04.08.2017 13:50:55] < 4016> dsk| WARN|The data area passed to a system call is too small.”

 
The above issue is resolved by installing Windows Update KB4034663, which can be found here:
 
https://support.microsoft.com/en-us/help/4034663/windows-8-1-windows-server-2012-r2-update-kb4034663
 

More Information

https://social.technet.microsoft.com/Forums/SharePoint/en-US/492f62ce-aec8-4777-98f0-0c9dbf302954/problem-with-kb4015553?forum=winserverwsus

https://support.microsoft.com/en-us/help/4015550
This security update introduced an issue in which, if an iSCSI target becomes unavailable, attempts to reconnect will cause a leak. Initiating a new connection to an available target will work as expected.

If after performing the steps outlined above the issue still occurs, a support case with Microsoft may be needed.

Failed to import Veeam Cloud Connect certificate after Veeam Availability Console server migration

$
0
0

Challenge

After migrating your Veeam Availability Console (VAC) installation to a new server and adding an existing Veeam Cloud Connect (VCC) server, the following certificate error may be observed:
 
Failed to import certificate from the Veeam Cloud Connect server. See debug logs for more information.

Cause

The behavior may occur after migrating a VAC installation that used to be co-located with Veeam Cloud Connect and adding the existing VCC server to the new VAC installation. In case the old VAC installation is in place, the VCC management agent is unable to pass the certificate to the new VAC server. 

NOTE: the VAC management agent that used to manage the existing VCC installation needs to be removed as per this KB article

Solution

There are 2 workarounds for this behavior:

Remove the old VAC installation from the VCC server.

or

Import the certificate manually following the steps below:

1. Open the Veeam Backup & Replication console on the VCC server and find out what certificate is currently in use:

User-added image

2. Run the certmgr command from the cmd, find the certificate in question and export it with the private key:

User-added image

3. Copy and install the exported certificate on the new VAC server. Make sure Local Machine is selected as a Store Location:

User-added image

User-added image

4. Restart the Veeam Management Portal service:

User-added image
 

More Information

If you have any questions, contact Veeam support.

An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full

$
0
0

Challenge

After installing Windows April update KB4015553 Veeam jobs and services fail at different operations with:
 
"An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full"

Cause

This particular update (and all consequent rollups that include it) causes the system to run out of free RPC ports when there are failed iSCSI connections.

Solution

Repairing or removing unsuccessful iSCSI connections, followed by the server reboot, was found to fix the issue. Additionally, remove any unused targets from the ‘Favorite Targets’ tab that are associated with these connections as they may be reconnected after reboot.

This issue has been addressed by Microsoft. Apply the appropriate update below to resolve the issue

For 2016:           https://support.microsoft.com/en-us/help/4025334
For 2012 R2:      https://support.microsoft.com/en-us/help/4025335

-------------------------------------------------------------------------------------------------------------------------------------------------

The update that resolved the above Buffer Space iSCSI issue (KB4025335) has caused another iSCSI issue that only affects Backup from Storage Snapshots using an iSCSI connection.
 
After installing Windows Update KB4025335, KB4034681, KB4025333, or KB4025336, Veeam jobs utilizing Backup from Storage Snapshots using an iSCSI connection fail with the following errors:
 
“Error: Cannot retrieve physical extents for connecting iSCSI target IQN iqn.2007-11.com.nimblestorage:lun-nim-oracle-veeam-lun-nim-oracle-v069a713ff86811d1.000000d1.fef260ee.s069a713ff86811d1.000000de.0000b1cb on proxy IQN iqn.1991-05.com.microsoft:mtl-s-fs0005.solotech.local”
 
In the logs, it can be seen with this error:
 
Task Log:
“[25.07.2017 09:44:54] <61> Error Failed to find physical drive for LUN with lun Id 'WwnOrIqn: 'iqn.1992-04.com.emc:cx.apm00140946425.a1', LunId: '10',
 
[25.07.2017 09:44:54] <61> Error Unable to retrieve devices for iSCSI session. number of retry attempts: '20'. Interval: '100'. (Veeam.Backup.Common.CCppComponentException)
[25.07.2017 09:44:54] <61> Error in c++: void __thiscall disklib::vmfs_san::iscsi_api::iscsi_discovery::GetDevicesForSessionWithRetry(struct _ISCSI_UNIQUE_SESSION_ID &,class std::vector<struct ISCSI_DEVICE_ON_SESSIONW,class std::allocator<struct ISCSI_DEVICE_ON_SESSIONW> > &,int,int) failed.
[25.07.2017 09:44:54] <61> Error in c++: void __thiscall disklib::vmfs_san::iscsi_api::iscsi_discovery::LoginTarget(const class std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class std::allocator<wchar_t> > &,class std::vector<struct disklib::vmfs_san::iscsi_api::IscsiDriveInfo,class std::allocator<struct disklib::vmfs_san::iscsi_api::IscsiDriveInfo> > &) failed.”

 
 
Proxy Resources Log:
 “[04.08.2017 13:50:55] < 4016> cli| VMFSSAN.ConnectISCSITarget
[04.08.2017 13:50:55] < 4016> cli| (EString) TargetName = iqn.1992-04.com.emc:cx.apm00140946425.a1
[04.08.2017 13:50:55] < 4016> cli| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[04.08.2017 13:50:55] < 4016> dsk| Retrieving devices for target 'iqn.1992-04.com.emc:cx.apm00140946425.a1'.
[04.08.2017 13:50:55] < 4016> dsk| WARN|The data area passed to a system call is too small.”

 
The above issue is resolved by installing Windows Update KB4034663, which can be found here:
 
https://support.microsoft.com/en-us/help/4034663/windows-8-1-windows-server-2012-r2-update-kb4034663
 

More Information

https://social.technet.microsoft.com/Forums/SharePoint/en-US/492f62ce-aec8-4777-98f0-0c9dbf302954/problem-with-kb4015553?forum=winserverwsus

https://support.microsoft.com/en-us/help/4015550
This security update introduced an issue in which, if an iSCSI target becomes unavailable, attempts to reconnect will cause a leak. Initiating a new connection to an available target will work as expected.

If after performing the steps outlined above the issue still occurs, a support case with Microsoft may be needed.

HCL-Scality-RING

$
0
0

Challenge

Product Information

Product Family: Scality RING 
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 
Number of Drives: 48 SATA, 6 SSD per node (6 nodes) 
Drive type: SATA and SSD 
Firmware version: RING Software Version 5.1.7 
Additional support: Configurations with 6 or more nodes with at least 48 SATA drives and 6 SSD’s per node 
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 Details

  • Repository Type: Shared folder
  • Align backup file data blocks: No
  • Decompress backup data blocks before storing: No
  • Use per-VM backup files: Yes (optional)
  • Enable In-Line Data Deduplication: Yes 
  • Compression level: Optimal 
  • Storage Optimization: Local Target (16TB+ backup files)  (Settings for source backups only, it guarantees better performance on this storage due to a bigger block size in backup copy)

More Information

Company Information

Company name: Scality  
Company overview: Scality, the world leader in object and cloud storage, bridges the gap between application vendors and industry standard hardware providers to meet your cost-effective storage scale, durability, cloud and performance requirements.

Cannot browse backups of Office 365 mailboxes that have been made in December

$
0
0

Challenge

Cannot browse backups of Office 365 mailboxes that have been made in December 2017.

Solution

Please note that backups are still valid and the restore of such is possible the following way:
  1. Stop Veeam Backup for Microsoft Office 365 Service and Veeam Backup Proxy for Microsoft Office 365 Service
  2. Open Veeam Explorer for Exchange
  3. Add ADB Mailbox Store to the Scope manually (refer to documentation)
  4. Restore items

More Information

Will be addressed in the next release version.
Viewing all 4470 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>