↧
Red Hat Enterprise Linux 7.5 is not supported by Veeam Agent for Linux 1.x and 2.0
↧
VMware Cloud on AWS Support. Considerations and Limitations
Challenge
VMware Cloud on AWS needs some specific preparation to allow Veeam Backup & Replication v9.5 Update 3 or newer to work with it.
Some of VMware features and permissions are not granted by default at the start of VMware Cloud on AWS (VMC). Thus, some depending Veeam Backup & Replication features will be limited or not operating. Depending on VMware update releases for VMware Cloud on AWS, the situation may change and the features from the table below may become available. Please contact your VMware administrator for timely update.
Solution
Implementation step 1 - Backup & Replication- Use a new Windows Server and install Veeam Backup & Replication v9.5 Update 3 or newer.
- Add DNS network settings so that this Server can resolve Internet DNS names.
- Check the below information carefully for any know limitations and configuration steps before you proceed.
Implementation step 2 - Backup & Replication
Install the latest VMware Cloud on AWS Veeam patch:
Please download the patch for Veeam Backup & Replication 9.5 Update 3 for VMware Cloud on AWS V1.3 (M3) here (instructions included).
Implementation step 3 - VMware Cloud on AWS
Firewall Configuration for vCenter connection
The Veeam Backup and Replication Server and Veeam proxy server should be connected to the VMware vCenter using HTTPS through TCP port 443. At VMware Cloud on AWS there is no need to open ports to the ESXi hosts itself. As the vCenter Server is by design of VMware Cloud on AWS on another network (Management Network) you need to implement a VPN tunnel to it or configure the following firewall settings:- Open Port TCP 443 from Backup Server and Proxy Server to the predefined vCenter object on the Compute Network.
- Allow the Compute Gateway Public IP to communicate over TCP 443 with the predefined vCenter object on the Management Network.
Implementation step 4 - add vCenter
Add vCenter to the Veeam console as described here: https://helpcenter.veeam.com/docs/backup/vsphere/add_vmware_server.html?ver=95
- Create a vCenter User with required rights (Active Directory linked mode) described here, or use the cloudadmin@vmc.local user.
- When adding a vCenter server, specify the fully qualified domain name (FQDN) that ends with vmwarevmc.com or vmc.vmware.com (depending on the URL shown in the VMC interface for the vCenter).
Implementation step 5 - add Veeam Repository
VMware Cloud on AWS has only one accessible vSAN disk. It would not make sense to use that disk for production workloads and backups. An external Backup device needs to be added. Depending on the use case there are several ways to achieve this with different economic factors. Please find below an example of an Amazon S3 EC2 Linux Server used as a backup target over the VMware Cloud on AWS integrated EDI network bridge:
To connect the EC2 Server(s) used as Veeam Repositories the following Firewall configuration is needed:
- On the Compute Network:
- Open TCP 22 (SSH) port from Veeam Backup server and Veeam proxy server to the Amazon VPC where the EC2 Server was installed. You can as well define the exact IP addresses of the repository server as Destination.
- Open TCP 2500-5000 ports for Veeam Data Transport in both directions for same servers. It is recommended to use the ENI Network Tunnel to avoid any traffic costs.
- Open the same ports on the Inbound Firewall of the Amazon EC2 server used as a repository server.
It is recommended to use the ENI Network Tunnel to avoid any traffic costs
- Open the same ports on the Inbound Firewall of the Amazon EC2 server used as a repository server
More Information
VMware Cloud on AWS specific problems and solutions:
Problem
Impossible to add the VMware Cloud on AWS vCenter server to the managed server, VMs within this vCenter are not visible in the list of VMs or an Error is displayed in the Veeam Jobs “Processing SQL Error: File does not exist or locked. …”Solution
- Create a vCenter User with required rights (Active Directory linked mode) described here, or use the cloudadmin@vmc.local user.
- When adding a vCenter server, specify the fully qualified domain name (FQDN) that ends with vmwarevmc.com or vmc.vmware.com (depending on the URL shown in the VMC interface for the vCenter).
Problem
When working with Restore or VM Replication wizard, users may face some issues accessing VMware Cloud on AWS vCenter server. By design, VMware does not provide customers access to the background infrastructure and used datastores.
Solution
For proper operation, you can select the specific areas marked as “Workload” or “Compute”. Avoid using the non-accessible areas, for example:- vsanDatastore datastore
- Management VMs folder
- Mgmt-ResourcePool resource pool
Problem
Backup & Replication stop working after VMware Cloud on AWS was automatically updated to Version 1.3 (M3).
Solution
UPDATE: New VMware Cloud on AWS V1.3 (M3) requires updated Veeam Backup & Replication components. Please download the patch for Veeam Backup & Replication 9.5 Update 3 here (instructions included).[[DOWNLOAD | DOWNLOAD | https://storage.veeam.com/Fix_125006_a473166fe3.zip]]
Problem
Some of the Backup & Replication Features are not working correctly because of limitations of the VMware Cloud on AWS environment (compared with a standard vSphere environment).
Solution
| Affected Veeam Feature | Limitation | Workaround |
|---|---|---|
|
Instant VM Recovery |
Currently, VMware Cloud on AWS (VMC) does not allow for NFS usage |
Use a combination of a Veeam backup job and replication job for proactive restore capabilities |
|
Other OS File Level Recovery |
Currently, VMC does not allow for NFS |
Start Linux File-Level Recovery from a backup copy on-premises |
|
Quick Migration |
Quick Migration cannot migrate VMs to VMC if they are running |
Use Veeam Replication and permanent failover to achieve similar functionality |
|
SureBackup, Sure Replica, OnDemand Labs, Virtual Lab |
Currently, VMC does not allow NFS and network manipulation |
As for SureReplica, you can perform it if the replication target is a non-VMC vSphere environment (e.g., replicate VM from VMC to on-premises) |
|
VM Guest Interaction and Windows File Restore by VIX or WebService API |
Currently, VMC does not allow usage of VMware Webservice API |
If you want to perform Veeam Guest processing or Windows File-Level Recovery, then connect to a VM over the network from Veeam Backup & Replication |
|
VM Replication ReIP |
ReIP is not available on VMC |
|
|
Windows Dynamic disks are not supported |
Currently, VMC does not allow to process dynamic disks at Hot-Add (Virtual Appliance mode) backup |
VMware will provide a hotfix for this soon |
|
Non-Unicode VM names |
Currently, VMC does not allow non-Unicode characters for VM names within their APIs used ad VMC |
|
|
VM Replication-based File Level Recovery |
|
Use file restore from backups or use a VM replica on a non VMC environment to start the File recovery |
↧
↧
Required modules and permissions for Multi-OS FLR and Repository support for Linux
Challenge
To configure Linux guests and repositories to work with Veeam Backup and Replication and utilize our software’s features.Cause
There are several requirements that must be met, by a Linux OS, in order for us to effectively utilize all of our features and make sure they run consistently. On top of that we require root permissions to launch several modules. If these settings are not in place, then we won’t be able to properly write to and recover the system.Solution
Authentication MethodsLinux servers registered with Veeam Backup & Replication infrastructure must use Password or Certificate-based authentication methods. At this time we do not support any other forms of authentication like biometrics, smart cards, etc.
Bash
We require Bash to be installed as shell on the Linux environment. At the time we do not support any other command shell. This is usually the default shell set in place by most Linux distributions.
"sudo"
Important Note: accounts using "sudo" must be in the "/etc/sudoers" file and have the ‘nopasswd’ setting put into the "/etc/sudoers" file.
In order to launch our script’s we require the "sudo" command to be able to launch from the credentials we are given at the time of setup. "sudo" is a command that allows us to make administrator level (root) changes and executions in the Linux environment.
One of the primary reasons that we use "sudo" is to make sure that we can access the /tmp folder and launch a script from it. There are many other ways you can launch scripts from the "/tmp" folder but "sudo" is the most consistent way across multiple distribution’s to do it. This also allows us to complete the operation without having change user permissions so the user doesn’t have to modify them afterword’s to get them back to their original configuration, as well as we will be able to relinquish root privileges on the fly.
In order to launch our script’s we require the "sudo" command to be able to launch from the credentials we are given at the time of setup. "sudo" is a command that allows us to make administrator level (root) changes and executions in the Linux environment.
One of the primary reasons that we use "sudo" is to make sure that we can access the /tmp folder and launch a script from it. There are many other ways you can launch scripts from the "/tmp" folder but "sudo" is the most consistent way across multiple distribution’s to do it. This also allows us to complete the operation without having change user permissions so the user doesn’t have to modify them afterword’s to get them back to their original configuration, as well as we will be able to relinquish root privileges on the fly.
Perl
Many Linux distributions come with Perl pre-installed but this does not mean that it has all the Perl modules that are required for us to utilize the server in a backup and restore function and once all of the correct modules are install we must be able to launch these modules as needed. Some systems are setup with software called SELinux. This software will make it so that only certain modules can be launched from SSH. The Linux distribution must allow us to launch all of these modules from "SSH" at any amount at a time.
Here is a list of the modules that we require for Veeam to work properly with a Linux install:
Here is a list of the modules that we require for Veeam to work properly with a Linux install:
- Constant
- Carp
- Cwd
- Data::Dumper
- Encode
- Encode::Alias
- Encode::Config
- Encode::Encoding
- Encode::MIME::Name
- Exporter
- Exporter::Heavy
- File::Path
- File::Spec
- File::Spec::Unix
- File::Temp
- List::Util
- Scalar::Util
- SOAP-Lite
- Socket
- Storable
- Threads
You can find out which modules are installed by running:
perldoc -q installed
One of the most widely used Linux distribution’s currently is CentOS 6/7 and in this distribution the "Data::Dumper Perl" module is not installed by default.
SSH
SSH is a program for logging into a remote machine and for executing commands on a remote machine. This is software that we use to log in to a Linux environment. Most systems have this software installed by default but if the Veeam server is having issues logging into a Linux environment you should check if SSH is installed.
The configuration of your SSH install must allow using tunneled clear text passwords. Info on how to do this can be found on this KB: http://www.veeam.com/kb1512
The configuration of your SSH install must allow using tunneled clear text passwords. Info on how to do this can be found on this KB: http://www.veeam.com/kb1512
SCP
SCP copies files between hosts on a network. It uses SSH for data transfer, and uses the same authentication and provides the same security as SSH. We use this software as our file mover on Linux. It is common for Centos core to not include this SCP module in the default install.
"mlocate", "gzip" and "tar"
"mlocate" is a new implementation of locate, a tool to find files anywhere in the file system based on their name, using a fixed pattern or a regular expression. We utilize "mlocate" to locate files on a Linux system.
"gzip" and "tar" are archive tools very much like WinZip. We use these to compress and decompress files going to and from the server.
All of these files and there required configurations must be installed on the Linux environment prior to its usage with Veeam Backup and Replication to fully use all of our features.
"gzip" and "tar" are archive tools very much like WinZip. We use these to compress and decompress files going to and from the server.
All of these files and there required configurations must be installed on the Linux environment prior to its usage with Veeam Backup and Replication to fully use all of our features.
More Information
http://www.veeam.com/kb2007 merged↧
Veeam Backup & Replication - SureBackup Step-by-Step Configuration Guide
Challenge
SureBackup is designed to speed up and simplify the test restores — one of the most crucial parts of any data protection strategy. SureBackup lets you verify recoverability of your backups in a fully automated manner, without having to first extract backups to your production storage - which can take prohibitively long time, thus limiting the number of test restores you can perform. This is achieved by running the tested VMs directly from backup files in an automatically provisioned isolated environment, preventing any impact on the production environment. Such approach dramatically accelerates the entire restore testing process, allowing you to potentially verify every created restore point of every protected VM, ensuring that your production restores will function as expected in case a disaster strikes.Solution
The following step-by-step instruction will help you to configure an Application Group, a Virtual Lab and a SureBackup job.{iframe src="http://api.veeamuniversity.com/apps/stepbystep.php?did=1818" width="1086" height="786"} {/iframe}
More Information
For more info on Surebackup you may want to check out our helpcenter.veeam.com↧
Veeam ONE - Steps to Compile Logs
Challenge
In some cases, logs are requested by Veeam Support to help diagnose issues.Cause
Follow the steps below to collect and upload the log files for further analysis.Solution
Exporting the log files
In Veeam One Monitor console navigate to Options > Server Settings > Other Settings > Launch Support Utility. In the lower left corner click Export Logs
or
Browse to or run C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe
In Veeam One Monitor console navigate to Options > Server Settings > Other Settings > Launch Support Utility. In the lower left corner click Export Logs
or
Browse to or run C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe
Exporting logs may take a while. When it is finished, you will be asked to choose the location for the logs to be saved to.
Uploading the log files
If the total attachment size is under 3.5MB, you will be able to attach it to your e-mail reply.
If none of these options are working, please notify Veeam Support and an engineer will provide FTP credentials for the case. Once you receive the FTP link, follow the below instructions to upload the logs via FTP. You can start by copying and pasting the URL with credentials, as it has the credentials built into the link. Once you have copied the URL, you can use a Windows\File Explorer browser (Windows key + e) and paste the link into that browser, or your preferred FTP client.
NOTE: Internet Explorer, Firefox, or any other browser will not work for the FTP upload.
1. Open Windows\File Explorer.
2. Paste URL with credentials.
3. Drag and Drop the Zipped folder or individual logs into the browser.
4. Once completed, update your existing support case to inform us that the logs have been successfully uploaded to ensure the quickest review and response.
More Information
Below are the relative log path lists for Veeam ONE. If there are difficulties compiling the logs via the Veeam ONE support tool, you can gather the files from the appropriate directories below and provide Veeam Support a .zip file copy.For versions: 7.x, 8.x, 9.x:
Veeam ONE Monitor - C:\Users\<USER>\AppData\Local\Veeam\Veeam ONE Monitor\
Veeam Reporter\Business View Service logs - C:\Users\<USER>\AppData\Local\Veeam\Veeam ONE\
Veeam Reporter Web logs - %ProgramFiles%\Veeam\Veeam ONE\Veeam ONE Reporter Web\Veeam\Veeam ONE Reporter\
Veeam Business View Web logs - %ProgramFiles%\Veeam\Veeam ONE\Veeam ONE Business View Web\Generated\
VeeamOneSettings - C:\Users\<USER>\AppData\Local\Veeam\VeeamOneSettings\
For version 9.5 and later:
Veeam ONE Monitor – %ProgramData%\Veeam\Veeam ONE Monitor\Logs\
Veeam Reporter\Business View Service logs – %ProgramData%\Veeam\Veeam ONE\
Veeam Reporter Web logs – %ProgramFiles%\Veeam\Veeam ONE\Veeam ONE Reporter Web\Veeam\Veeam ONE Reporter\
Veeam Business View Web logs – %ProgramFiles% \Veeam\Veeam ONE\Veeam ONE Business View Web\Generated\
VeeamOneSettings - %ProgramData%\Veeam\VeeamOneSettings\
If you have any questions, contact Veeam Support.
↧
↧
HCL - Infortrend - EonStor DS
Challenge
Product Information:
Product Family: Infortrend – EonStor DS
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.
Solution
Product Details:
Model number: DS 1016R2
Number of Drives: 16
Drive type: 6TB NL-SAS
Firmware version: 6.61F.10
Connection protocol and speed: 8Gb FC
Additional support: All models and configurations of Infortrend EonStor DS-Series with specifications equivalent or greater than the above
General product family overview: EonStor DS is a high availability SAN storage solution designed for enterprises. It’s hardware design features multiple form factors, flexible host boards to choose from, and stable, reliable modular design with high expandability; as for software, it comes with complete data services and easy-to-use management interfaces. It is ideal for all SAN environments and enterprise applications (such as backup). The whole product line is fast, flexible, and reliable, so that you can find the perfect storage device according to your performance or budget needs.
Vendor Veeam testing configuration:
Veeam Build Number: 9.5.0.1536
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: Infortrend
Company overview: Infortrend Technology is a leading provider of high performance networked storage solutions focusing on quality, choice and value, and is one of the few fully integrated technology companies to be completely dedicated to storage systems as well as related software and services.
↧
HCL - Hedvig Distributed Storage Platform
Challenge
Product Information:
Product Family: Hedvig Distributed Storage Platform
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.
Solution
Product Details:
Model number: Hedvig Distributed Storage Platform
Number of Drives: 1, 15 (x3 nodes)
Drive type: 300GB SSD, 1TB HDD (x3 nodes)
Firmware version: 3.7.2
Connection protocol and speed: 10Gb
Additional support: All configurations of Hedvig Distributed Storage Platform with specifications equivalent or greater than the above
General product family overview: Hedvig provides multi-site software-defined storage for primary and secondary applications for private-, multi-, and hybrid-cloud deployments. Unique capabilities like replication policy, deduplication, compression, and encryption can be enabled per application. This programmable platform can scale from 10’s of TB to multi-PB with no practical limit.
Vendor Veeam testing configuration:
Veeam Build Number: 9.5.0.711
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: No
More Information
Company Information:
Company name: Hedvig Inc.
Company overview: Our mission at Hedvig is to improve the economics of storing and managing the world's data. Built by software engineers of the world's largest and most successful distributed systems, Hedvig delivers modern storage for any enterprise compute environment running at any scale. The Hedvig platform is the only software-defined storage solution with true distributed systems DNA, unconstrained by traditional thinking and existing architectures that can't keep pace with scale-out applications and the velocity of change in today's business.
↧
Veeam Backup & Replication support for VMware vSphere
Challenge
This article describes Veeam Backup & Replication support for different VMware vSphere versions.Cause
The earlier versions of Backup & Replication may not support the latest vSphere releases. It is recommended to use the latest Veeam version to ensure modern platforms support and security compliance.Solution
| ESXi version | Minimum Veeam B&R starting version | Build number | Veeam GA date |
|---|---|---|---|
| 5.0 | v5.0.2.230(*) | 5.0.2.230 | 2011-10-21 |
| 5.1 | v6.5 | 6.5.0.106 | 2012-10-9 |
| 5.5 | v7 R2 | 7.0.0.771 | 2013-11-14 |
| 6.0 | v8 Update 2 | 8.0.0.2030 | 2015-04-28 |
| 6.5 | v9.5 Update 1 | 9.5.0.823 | 2017-01-20 |
| 6.5 Update 1 | v9.5 Update 2 (to support vSAN 6.6.1) | 9.5.0.1038 | 2017-05-12 |
| 6.7 | Not supported. Full support is due in the next Veeam update | - | - |
More Information
End of Support for Veeam Products: https://www.veeam.com/kb1530VMware Lifecycle Product Matrix: https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/support/product-lifecycle-matrix.pdf
The latest Veeam 9.5 Update 3: https://www.veeam.com/kb2353
↧
Veeam Backup for Office 365 Timeout Errors
Challenge
A Veeam Backup for Office 365 job fails with a timeout error.These commonly are reported as one of the the following errors:
- Unexpected End of File
- Exchange Web Services error code: ErrorExceededConnectionCount
- Error: Failed to get folder properties
- Error: You have exceeded the available concurrent connections for your account. Try again once your other requests have completed.
- Error: Unexpected end of file has occurred. The following elements are not closed: m:Data, m:ExportItemsResponseMessage, m:ResponseMessages, m:ExportItemsResponse, s:Body, s:Envelope. Line 1, position 21397505.
Cause
There are multiple causes for these timeout errors. The most common being a bad connection to the Exchange Web Service (EWS) from the Veeam Backup for Office 365 server or proxy. This can be caused by a flooding of open worker threads to the Exchange Web Services server, network traffic saturating the throughput of the connection, a slow internet connection to the Office 365 EWS server amongst other issues.Solution
In 1.5, performance settings to help with timeout errors can be adjusted through the proxy performance settings (Concurrent Threads, and limit network bandwidth). If you are still unable to get a Veeam Backup for Office 365 due to these timeout errors after adjusting the Proxy Settings, you can contact Veeam Support to further fine tune the settings.↧
↧
Veeam Backup & Replication support for VMware vSphere
Challenge
This article describes Veeam Backup & Replication support for different VMware vSphere versions.Cause
The earlier versions of Backup & Replication may not support the latest vSphere releases. It is recommended to use the latest Veeam version to ensure modern platforms support and security compliance.Solution
| ESXi version | Minimum Veeam B&R starting version | Build number | Veeam GA date |
|---|---|---|---|
| 5.0 | v5.0.2.230(*) | 5.0.2.230 | 2011-10-21 |
| 5.1 | v6.5 | 6.5.0.106 | 2012-10-9 |
| 5.5 | v7 R2 | 7.0.0.771 | 2013-11-14 |
| 6.0 | v8 Update 2 | 8.0.0.2030 | 2015-04-28 |
| 6.5 | v9.5 Update 1 | 9.5.0.823 | 2017-01-20 |
| 6.5 Update 1 | v9.5 Update 2 (to support vSAN 6.6.1) | 9.5.0.1038 | 2017-05-12 |
| 6.7 | Not supported. Full support is due in the next Veeam update | - | - |
More Information
End of Support for Veeam Products: https://www.veeam.com/kb1530VMware Lifecycle Product Matrix: https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/support/product-lifecycle-matrix.pdf
The latest Veeam 9.5 Update 3: https://www.veeam.com/kb2353
↧
HCL - iXsystems M-Series
Challenge
Product Information:
Product Family: iXsystems M-Series
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.
Solution
Product Details:
Model number: M40
Number of Drives: 22
Drive type: 4TB 7200RPM SAS
Firmware version: 11.1
Connection protocol and speed: 10GbE iSCSI
Additional support: All models and configurations of iXsystems M-Series with specifications equivalent or greater than the above
General product family overview: The TrueNAS M40 is a 24 bay enterprise storage platform that uses NVDIMMs for write caching, SSDs for read caching, and can expand to use two external 60-bay expansion shelves.
Vendor Veeam testing configuration:
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: No
More Information
Company Information:
Company name: iXsystems
Company overview: iXsystems believes that Open Source technology has the power to change the world through its process of open and collaborative innovation. This principle fuels all product design at iXsystems. By leveraging decades of expertise in hardware design, its contributions to many Open Source software communities, and corporate stewardship of leading Open Source projects (including FreeNAS® and TrueOS®), iXsystems has become an industry leader in building innovative storage solutions and superior enterprise servers for a global marketplace that relies on open technology.
↧
HCL - Panzura - Freedom NAS
Challenge
Product Information:
Product Family: Freedom NAS
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.
Solution
Product Details:
Model number: 5500
Storage Category: Cloud-out NAS Storage
Number of Drives: 12-800GB SAS SSD
Drive type, size, quantity: 12-800GB SAS SSD
Storage configuration: RAID50 via automatic software configuration
Firmware version: 7.0.2.5
Connection protocol and speed: 2 x 10GbE
Additional support: All models and configurations of Freedom NAS with specifications equivalent or greater than the above
General product family overview: Panzura FreedomTM is an intelligent hybrid cloud storage solution underpinned by Panzura CloudFS. Panzura CloudFS is a scale-out, distributed file system purpose-built for the cloud. Programmatically accessible through REST APIs, it utilizes high performance flash in the data center, and integrates the cloud for economics, scalability, and durability. Unlike NAS, it scales globally across multiple sites and multiple clouds.
Veeam testing configuration:
Veeam Build Number: 9.5.0.1536
Veeam Settings:
- Repository Type: Shared Folder
- Deduplication: Yes
- Compression: Optimal
- Storage Optimization: Local target
- Per-VM Backup Files: Yes
- Decompress before storing: No
- Align backup file blocks: Yes
Vendor recommended configuration:
Vendor Settings: The default configuration enables auto-tuning for all Panzura settings, which work well with the Veeam application. The caching policy should be set to pinned (as opposed to autotune) to ensure the administrator controls which backup sets are available locally. All Veeam backup data must be pinned locally to ensure fast restores and effective data operations within Veeam, without cloud reads.
More Information
Company Information:
Company name: Panzura, Inc.
Company overview: Panzura is the leader in enterprise hybrid cloud NAS and cloud data management. Panzura Freedom, an intelligent hybrid cloud storage platform, represents a breakthrough in managing explosive growth in unstructured data, delivering data center performance with the economics, scalability, and durability of the cloud. Panzura CloudFS underpins Panzura Freedom and incorporates intelligent file services backed by 27 patents. Using Panzura, enterprises shift from legacy storage as they consolidate and simplify their storage into the cloud.
↧
Veeam ONE Manual Database Creation
Challenge
Manual creation of Veeam ONE database may be needed in some scenariosCause
Here is how Veeam ONE database can be created.Solution
1. Open SQL Server Management studio.
2. Create a service account for Veeam ONE and assign the following permissions to it:
2. Create a service account for Veeam ONE and assign the following permissions to it:
- Public role (default permissions)
- CREATE ANY DATABASE permissions
- db_owner role on the Veeam ONE database
- db_datareader permissions on the master database
- public, db_datareader, SQLAgentUserRole permissions on the msdb database
- [For Always-On Availability Groups] VIEW SERVER STATE permissions
NOTE: If the Veeam ONE database runs on a remote Microsoft SQL Server instance, with the Microsoft SQL Server and Veeam ONE components residing in the same workgroup, Microsoft SQL Server authentication will be required.
3. Create a new database using the account specified above.
4. Run the installation SQL script against the new database. The script can be found on the Veeam ONE ISO: Addons\SQLScript\VeeamOne.sql.
5. Install Veeam ONE using the specified Service Account and the database created earlier. If Veeam ONE is already installed, update the existing database name using Veeam ONE Settings utility located in C:\Program Files\Veeam ONE\Veeam One Settings\VeeamOneSettings.exe
6. Install Veeam Reporter packs. See this KB for details.
7. Install the latest Update for Veeam ONE (skip this step in case you completed this requirement during the Reports pack installation).
8. Update websites settings. See this KB article for details.
4. Run the installation SQL script against the new database. The script can be found on the Veeam ONE ISO: Addons\SQLScript\VeeamOne.sql.
5. Install Veeam ONE using the specified Service Account and the database created earlier. If Veeam ONE is already installed, update the existing database name using Veeam ONE Settings utility located in C:\Program Files\Veeam ONE\Veeam One Settings\VeeamOneSettings.exe
6. Install Veeam Reporter packs. See this KB for details.
7. Install the latest Update for Veeam ONE (skip this step in case you completed this requirement during the Reports pack installation).
8. Update websites settings. See this KB article for details.
More Information
NOTE: As Veeam ONE operates with the huge amount of data, the database size and the database transaction log growth could be high.Should you have any questions, contact Veeam Support.
↧
↧
HCL - Supermicro - SuperStorage
Challenge
Product Information:
Product Family: Supermicro - SuperStorage
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.
Solution
Product Details:
Model number: SSG-5049P-E1CR45L
Number of Drives: 9, 15
Drive type: 1.5TB SSD, 6TB SATA
Firmware version: 2.0
Connection protocol and speed: 10GbE
Additional support: All models and configurations of Supermicro SuperStorage server with specifications equivalent or greater than the above
General product family overview: The SSG-5049P-E1CR45L features a 45-Bay Storage and a short depth storage server. Designed with Microsoft Software-Defined Storage in mind, it is perfect in space-constrained environments for Cloud Data Protection.
Veeam testing configuration:
Veeam Build Number: 9.5.0.1536
Veeam Settings:
- Repository Type: Shared Folder
- 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: Supermicro, Inc.
Company overview: Supermicro, a global leader of innovative server and storage technologies, provides high performance, high quality and green products and solutions to deliver forward looking computing for Fortune 1000 companies in Data Centers, Cloud Computing, Software-Defined Storage, Embedded, Big Data, HPC and AI. Featuring “Building Block” business model, Supermicro customers enjoy the latest and the broadest technology in industry. Designed with the highest levels of reliability and quality, SMC help its customers to meet challenges in performance, density, thermal management and power efficiency with data center scale and best TCO. Supermicro is the #1 fastest growing IT company ranked by Fortune Magazine in 2017 and a proud member of the Fortune 1000 US companies.
↧
Veeam Availability Console 2.0 Hotfix_1376
Challenge
Veeam Availability Console 2.0 Hotfix_1376Cause
This update resolves the following issues that can be encountered with Veeam Availability Console (VAC) 2.0:Server
- Veeam Availability Console server starts using 100% of CPU resources when registering a Company (aka tenant) from the Cloud Connect server.
- Unable to delete a company from VAC UI if a tenant has been already deleted in Veeam Cloud Connect.
- Optimized PowerShell queries to Veeam Cloud Connect to decrease Veeam.Backup.Satellite processes count.
UI
- Under certain conditions company owner may view failover plans that belong to a different company.
Management Agent
- Veeam management agents show "Out-of-date" as their version status.
Backup Policy & Veeam Agent
- Veeam Agent for Microsoft Windows disappears from the Veeam Availability Console UI after applying the backup policy.
- Backup policies may fail to apply against computers with Scandinavian locales due to a different datetime delimiter.
- Under certain conditions a backup policy may fail to delete.
Monitoring & Alarms
- Under certain conditions "Cloud Host Memory Quota" and "Company Cloud Host Storage Quota" alarms are not triggered after breaching the configured threshold.
- When defining RPO in hours in the "VM without backup" alarm, values above 24 are converted into days.
- A failed job after a successful retry is still reported as "failed".
- Under certain conditions the "Computer without backup" alarm may not trigger.
Reporting & Billing
- Re-configuring a report may result in the "An item with the same key has already been added" error message.
- Under certain conditions RPO is reported incorrectly in the "Protected VMs" report.
- Total Gross may not be correctly calculated when specifying VAT for managed services.
- Tenant Used Storage may be calculated incorrectly in invoices when VMs are backed up to Cloud Connect repository.
- Compute Time Usage may be calculated incorrectly if the "per month" counter is specified.
- A "Protected Computers" report may fail to generate due to the total files path field for the File-Level Backup mode exceeding the allowed maximum. By default, backup jobs contain folder names along with their location.
- Cloud repository used storage quota may be calculated incorrectly, when backup agent is backed up to the Veeam Cloud Connect repository.
RESTful APIs
- Under certain conditions "UsedStorageQuota" and "UsedTrafficQuota" are reported incorrectly through RestAPI.
Solution
Before you begin, confirm under Windows > Programs and features that the current product version is 2.0.1.1319 or later.Download VAC 2.0.1.1364. > VAC 2.0.1.1376
To install the fix:
1. Back up VAC database.
2. Log off VAC Web UI.
3. To install the server update, on the VAC server execute VAC.ApplicationServer.x64_2.0.1.1376.msp as administrator, or run this cmdlet as administrator:
msiexec /update c:\VAC.ApplicationServer.x64_2.0.1.1376.msp /l*v C:\ProgramData\Veeam\Setup\Temp\VACApplicationServerSetup.txt
4. To install the Web UI update, on the VAC Web UI server execute VAC.WebUI.x64_2.0.1.1376.msp as administrator, or run this cmdlet as administrator:
msiexec /update c:\VAC.WebUI.x64_2.0.1.1376.msp /l*v C:\ProgramData\Veeam\Setup\Temp\VACWebUISetup.txt
5. Log in to VAC Web UI.
More Information
You can check whether the update installed successfully opening Windows > Programs and features.The product version for Veeam Availability Console will be 2.0.1.1376 after applying the update.
Should have any questions, contact Veeam Support.
↧
Nothing to backup warning is received for Veeam Agent backup on some Dell PERC controllers
Challenge
When running a Veeam Agent for Microsoft Windows backups job in “Managed by VBR” mode, volume-level backup jobs finish with a “nothing to backup” warning. The job log will contain the following:[Timestamp] <01> Warning Volume [Apps (D:)] is located on disk [Disk 2] which is in invalid state. [Timestamp] <01> Info [CEndPointRegistryOptionsWatcher] Stop watcher [Timestamp] <01> Error Job has been stopped with failures. Name: [DELL SERVER], JobId: [1903716f-b0fc-47b5-ac8a-f622bb43375c] [Timestamp] <01> Error Nothing to backup (System.Exception)
The PC itself is working fine. Locally installed Veeam Agent also succeeds.
Cause
Some storage controllers (e.g. DELL PERC) return an invalid state for the drives:[Timestamp] Info <1720> Disk 2, capacity: 546.4GB, bus type: SCSI, read-only state: undefined, pack state: 1
By default, there should be either read-write or read only states.
An undefined state is not considered as healthy, therefore there are no guarantees that the data on the disk is consistent.
Veeam Agent in unmanaged mode adds such volumes to the backup disregarding the state values. However, in managed mode VAW skips such drives to make sure that only read-write disks are added to the backup scope.
Solution
Please contact Veeam Technical support in order to get a private fix.↧
Version string portion was too short or too long
Challenge
When trying to configure Veeam ONE Reporter data collection tasks, the following error message pops up:Version string portion was too short or too long
Cause
The issue is due to manual Veeam ONE database deployment that leaves blank fields in the common.serversettings table required for correct product functioning.Solution
Before applying the instructions below, make sure you have a full backup of Veeam ONE SQL database.To find out the Windows version, on Veeam ONE server open CMD and run ver command. Use the x.x.x.x format.
Run the following queries against Veeam ONE database, substituting the fields marked in red with appropriate values:
exec common.SetSetupDataReporterURI 'https://reporterfqdn:1239/'
go
exec common.SetSetupDataBusinessViewURI 'https://businessviewfqdn:1340/'
go
exec common.SetSetupDataWindowsVersion '%WINVERSION%'
go
More Information
If you have any questions, contact Veeam Support.↧
↧
Recovery Media based on Windows 1709 fails to connect to SMB1 shares
Challenge
When booting with Recovery Media which is based on Microsoft Windows 10 Fall Creators Update or Microsoft Windows Server 1709, a connection attempt to CIFS shares fails with:You can't connect to the file share because it's not secure. This share requires the obsolete SMB1 protocol, which is unsafe and could expose your system to attack. Your system requires SMB2 or higher. For more info on resolving this issue, see: https://go.microsoft.com/fwlink/?linkid=852747
Cause
In Windows 10 Fall Creators Update and Windows Server, version 1709 (RS3), the Server Message Block version 1 (SMBv1) network protocol is no longer installed by default. It was superseded by SMBv2 and later protocols starting in 2007. Microsoft publicly deprecated the SMBv1 protocol in 2014.Solution
Enable SMBv2 or SMBv3 feature on your NAS device.More Information
https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-installed-windows-10-and-windows-server-version-1709↧
How to change SQL log backup location for Veeam Agent for Microsoft Windows backup
Challenge
Veeam Agent for Microsoft Windows copies transaction log files from the log archive destination (set by the Microsoft SQL Server administrator) to a temporary folder on the Veeam Agent computer file system. By default the path is: C:\ProgramData\Veeam\Endpoint\SqlLogBackup. In case if the default destanation should be changed, you can specify it in SqlTempLogPath(STRING) registry key.Solution
Important: the key should be created on the Veeam Agent for Windows machine!SqlTempLogPath
KEY: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
TYPE: REG_SZ
VALUE: path to desired location (should be without \ in the end)
↧
Veeam Agent for Microsoft Windows deployment fails with “Failed to call RPC function 'PckgCheckSignature'
Challenge
When a computer is being added to protection group, Veeam Agent for Microsoft Windows deployment starts and fails with the following:Info [UploadManager] Checking windows package 'C:\ProgramData\Veeam\Agents\VAW\Veeam_B&R_Endpoint_x64.msi' signature on host 'HOSTNAME' Error Failed to call RPC function 'PckgCheckSignature': Signature of module 'C:\ProgramData\Veeam\Agents\VAW\Veeam_B&R_Endpoint_x64.msi' is invalid.. Error Signature of module 'C:\ProgramData\Veeam\Agents\VAW\Veeam_B&R_Endpoint_x64.msi' is invalid Error --tr:Failed to call DoRpc. CmdName: [PckgCheckSignature].
Cause
The certificate which is used to sign the Veeam Agent installation package is not installed in the Trusted Root Certification Authority store on the client computer.Solution
- Download DigiCert Assured ID Root CA here (right click on Download button - save as)
- Double click the downloaded .srt file
- Click Install Certificate
- Choose Local Machine and click on Next
- Place the certificate into Trusted Root Certification Authorities by clicking the Browse button.
↧