Challenge

Cause

Solution

• Dell EMC Data Domain OS 6.0 support, including synthetic full backup performances optimizations, backup retention and health check reliability improvements.
• HPE 3PAR 3.2.2 MU3 support, including multiple API interaction improvements for added reliability and performance.
• HPE StoreOnce 3.15.1 support, bringning Instant VM Recovery to Catalyst-based backup repositories.
• Veeam Agent for Linux 1.0 support.
• Veeam Agent for Microsoft Windows 2.0 Public Beta (build 2.0.0.594) support.
• VMware vSphere 6.5 support (see the next section for details).

• Encrypted VMs support. vSphere 6.5 introduces VMs with encrypted disks. Such VMs can be backed up in hot add and network (NBD) transport modes only, with hot add mode requiring that the backup proxy itself is an encrypted VM. There are no limitations around restores, because backups contain unencrypted VM data (remember to enable backup encryption if that is a concern).
• VMFS6 support. vSphere 6.5 introduces the new VMFS version, and this update allows you to leverage advanced functionality such as Backup from Storage Snapshots and Veeam Explorer for Storage Snapshots for VMs with virtual disks residing on VMFS 6 datastores.
• Virtual hardware version 13 support. vSphere 6.5 introduces the new VM hardware version which increases some configuration maximums and adds ability to add NVMe controllers to a VM. This update adds ability to process such VMs.
• NBD compression. VDDK 6.5 adds ability to enable native NBD traffic compression. To control the compression level, create VMwareNBDCompressionLevel (DWORD) registry value under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key on the backup server with value from 0 (no compression) to 3 (best compression). Please expect significant performance impact from enabling NBD compression unless you’re backing up over slow or busy management network.
• New guest interaction API support. vSphere 6.5 discontinued VIX API that previous Veeam versions leveraged for network-less guest interaction for functionality such as application-aware processing. As part of vSphere 6.5 support effort, we have switched the corresponding functionality to the new vSphere API for guest interaction, so that you can continue using the existing product functionality with vSphere 6.5.
• New VM tag API support. vSphere 6.5 introduces new APIs for programmatic access and management of vSphere tags. With its support by Veeam, you can continue using advanced backup policies based on tags even after you upgrade to vSphere 6.5

• Double-byte support. Double-byte characters are now supported in the virtual infrastructure object names (such as VM name) and Veeam object names (such as job name).
• Export performance improvements. Disk content export from agent-based backups now processes multiple disks in parallel, as opposed to sequentially.

• Performance improvements. Performance of Backup Copy jobs with large number of VMs (hundreds/thousands) was improved in a few times.
• Reliability improvements. Added transfer resume functionality for transparent handling of short network connection outages in certain backup copy process phases where they were not previously used.

• Reliability improvements. Added transfer resume functionality for transparent handling of short network connection outages between a source backup repository and a tape server.

• OES 2015 SP1 support. Open Enterprise Server 2015 SP1 support for file-level recovery from NSS volumes with Trustee Index enabled.

• Side by side restore. Tenants are now able to restore VMs and vApps without overwriting the original object by selecting Keep restore option, in which case the restored object will be created with the _restored suffix as opposed to overwriting the original object (which is still possible by selecting Overwrite restore option).
• Job mapping. Added Set-VBRvCloudOrganizationJobMapping PowerShell cmdlet that allows to map a vCloud backup job and associated guest processing credentials to the existing self-service org record to enable tenants to start using self-service portal functionality for the existing jobs and backups.

• Direct SAN transport improvements. Improved direct SAN transport selection on backup proxies with disabled MPIO, added support for parallel restore through multiple Direct SAN backup proxies.
• Restore without storage profile. The newly added Default policy container in the Select Datastore dialog allows restoring, replicating or migrating virtual machines without their virtual disks inheriting an existing storage profile assigned to the target datastore.
• Restore logic improvements. Full VM restore and Instant VM Recovery operations will now preserve workingDir parameter of the original VM.
• Broker service enhancements. Added experimental Broker Service behavior when it does not try to keep the vSphere infrastructure cache up-to-date continuously. Instead, it will query vSphere infrastructure hierarchy changes only when hierarchy data is requested, but no less often than the specified timeout. Using this mode significantly reduces vCenter Server traffic in large environments while only slightly delaying tasks requiring vSphere hierarchy data. To enable this mode, create VmwareForcedHierarchyUpdatePeriod (DWORD) registry value under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key on the backup server with the value in seconds (900 is the recommended value).

• Asian OS locales support. Veeam Backup & Replication console now supports installation on operating systems with Asian locales, where it was previously unusable due to misplaced UI controls. Update 1 has been tested on all most common Asian locales and validated by local Veeam sales teams of the corresponding regions.
• Experimental high DPI monitors support. We've made the first step towards high resolution monitors support - and while there's still work to be done, the UI is now more usable on DPI settings above 100%. This did require changing the UI font, resizing all dialogs and adjusting placement for some UI controls - so you will notice slightly different UI look after installing the update.

• Fixed an issue which caused monthly Active Full backup schedule to reset to the default one (First Monday of the month) after upgrading to version 9.5.
• Improved reliability of establishing connections to Linux servers by addressing a number of Linux version-specific issues and updating SSH client.
• Improved Direct Restore to Microsoft Azure proxy appliance deployment and management functionality.
• Improved backup placement logic improvements for reversed-incremental backup jobs targeting scale-out backup repository with per-VM backup file chains disabled.
• Addressed an issue with enabling CBT on a VMware VM when backup server is running on certain non-English locales, for example Turkish.
• Addressed a number of minor issues with Veeam Cloud Connect.

More Information

Challenge

Cause

Solution

──────────────────────────────────────────────────────────
Datastore Cleanup
──────────────────────────────────────────────────────────
1. Using datastore browser go to the folder of the replica.
2. Most likely there will be many files, keep in mind that the only files that are required are:
 •VMX
 •VMXF
 •NVRAM
 •VMDK for each disk.
So for example here is a folder precleanup post repair.



We can remove the following files:



Leaving the VMX, VMXF, NVRAM, and the VMDK for each disk. Removing the associated snapshot files that are no longer needed.
 
──────────────────────────────────────────────────────────
Test the replica
──────────────────────────────────────────────────────────
1. Create a snapshot on the replica.
2. Remove the snapshot.
3. If no error occurs, map to the replica in a replication job and see if the job runs successfully.

Challenge

Cause

Solution

1. Start the Netlogon service
2. Change the "Startup type" to "Automatic"
3. Reboot the server

Challenge

Cause

Solution

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

Challenge

Solution

• Validate the VMs named "W2008", "W2008R2_DC" and "W2K" in the most recent restore point for the backup "Backup Job 1_imported".
  
  Veeam.Backup.Validator.exe /backup:"Backup Job 1_imported" /vmname:W2008 /vmname:W2008R2_DC /vmname:W2K
   
• Validate all virtual machines in the last restore point with ID 3942788C-B309-4FA4-A111-A4C87B3EC63D.
  
  Veeam.Backup.Validator.exe /backup:3942788C-B309-4FA4-A111-A4C87B3EC63D
   
• Validate a VM with the name "Windows 8" in the restore point created on December 5 2012 for a job named “Backup Job 1".
   
  Veeam.Backup.Validator.exe /backup:"Backup Job 1" /vmname:"Windows 8" /date:05.12.2012
   
• Validate a VM with the name "VM1" in the restore point created around 16:00 on December 5 2012 for a job named "Backup Job 2".

• Validate a VM with the name "VM2" contained in the VBM file located at C:\Backup\VM2_Backup.vbm
  
  Veeam.Backup.Validator.exe /file:"C:\Backup\VM2_Backup.vbm" /vmname:"VM2"
   
• Validate all VMs in VBK-file (backup file).
  
  Veeam.Backup.Validator.exe /file:"C:\Backup\VM2_Backup.vbk"
   
• Validate a VM with the name "VM3" in the most recent restore point of "Backup Job 1" and create an HTML-report.
  
  Veeam.Backup.Validator.exe /backup:"Backup Job 1" /vmname:"VM3" /report:"D:\Reports\Backup_Job_1_Validate_30_09_2014.html"
   
• Validate a VM with the name "VM3" in the most recent restore point of "Backup Job 1" and create XML-report.
  
  Veeam.Backup.Validator.exe /backup:"Backup Job 1" /vmname:"VM3" /report:"D:\Reports\Backup_Job_1_Validate_30_09_2014.xml" /format:xml

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

Challenge

Solution

 

For Replica seeding in Veeam Backup & Replication 8 please review:
 
VMware
http://helpcenter.veeam.com/backup/80/vsphere/index.html?replica_seeding_vm.html
 
Hyper-V
http://helpcenter.veeam.com/backup/80/hyperv/index.html?replica_seeding_hv.html
 
For replica seeding in Veeam Backup & Replication 7 or older please review the following.

To manually seed a Replica:
 
Part 1: Restoring the VM to the Destination


1.  Go to Backups and select the job in your target repository(Check the Repository column). Expand the backup set via the chevron to the left of the backup set name. Right click the VM you want to make into a replica and select 'Restore Entire VM'.




2.  On the Restore Mode tab select ‘Restore to a new location or with different settings’.



3.  On the same tab click ‘Pick Proxy to Use’.



4.  Pick the appropriate proxy to process this restore job. Pick the proxy on the TARGET side.



5.  On the ‘Host’ tab, select the target host you want the replica to reside on.



6.  On the ‘Resource Pool’ tab, select whichever resource pool, if any, you want the replica to use.

7.  On the ‘Datastore’ tab, by default, original datastore and disktype are selected for each VM. You can change them by selecting desired VM file, and clicking Datastore or Disk Type (at the bottom).

8.  On the ‘Folder’ tab, by default, the original VM folder is selected as restore destination for each VM. You can change folder by selecting the desired VM and clicking Folder (at the bottom). You can also change the VM name by highlighting the VM and then clicking “Name…” at the bottom. It is suggested to add the suffix “_replica”.

9.  On the ‘Network’  tab, if you are restoring to a different location, specify how the original location’s network maps to the new location’s network.

10.  From here you can click through to finish, make sure NOT to check "Power on VM after restoring", and hit [Finish].


Part 2: Mapping to the restored VM


1.  When the restore completes edit the replication job.

2.  Mark the ‘Enable Low Connection Bandwidth’ (fig. 1) in the Name tab.

3.  On the Destination tab make sure the settings match the present location of the restored VM that will become the replica.

4.  On the ‘Seeding’ (fig.2) tab check ‘Map replicas to existing VMs’.

5.  Then highlight your production VM, hit ‘Edit’, and map it to the VM you restored on the TARGET side in Part 1 of this KB. Once you have mapped the restored VM (now replica) to the original VM, next through until you have completed the rest of the job settings and select Finish.

6.  Be sure to run the job and test it.

Challenge

Solution

• A new server to install VBO on it should be ready and should be at least the same version of Windows or higher
• The following data should be available:
  • Everything under C:\ProgramData\Veeam\Backup365 from the old server (Config data)
  • Your data in the VeeamRepository that holds the O365 backupped data (Repository data). Note: The source and target repository paths should be the same.
  • If the repository is a network share, then the target server should have access to that share
  • If the repository is an iSCSI drive then it is important to disconnect it from the source first to avoid 2 iSCSI initiators issue. Then connect it to the target server.
• These files could come from the original server or restored from a VM-backup through Veeam Backup and Replication.
• Your license file

Additional information:

If you forget to retype your password, you will get the following error when a job tries to run.



Error: [Timestamp] :: Connecting to remote server outlook.office365.com failed with the following error message : [ClientAccessServer=DB5PR0201CA0031,BackEndServer=db3pr04mb219.eurprd04.prod.outlook.com,Req
uestId=4dc5aabf-7349-4a2e-8036-597c2163768f,TimeStamp=1/5/2017 5:57:30 PM] Access Denied For more information, see the about_Remote_Troubleshooting Help topic.

Challenge

Processing mailbox: mailbox@name.com...
Syncing folder items: name...
Sync time: 0.562066
Changed items: 26, deleted items: 0
Estimated changed items size: 1.77 MB
Error: Object reference not set to an instance of an object.
Stack:
   at Veeam.Archiver.Source.SyncPage.SaveChanges(IFolderRepository repository)
   at Veeam.Archiver.Source.ItemProcessor.ProcessFolder(Byte[] id, ExFolder folder, Byte[] currentState)
   at Veeam.Archiver.Source.ItemProcessor.<>c__DisplayClass6_0.<Process>b__0()
   at Veeam.Archiver.Source.FolderRetry.<>c__DisplayClass14_0`1.<Process>b__0()
   at Veeam.Archiver.Source.FolderRetry.Process(Action action)
   at Veeam.Archiver.Source.FolderRetry.Process[T](Func`1 func)
   at Veeam.Archiver.Source.ItemProcessor.Process(ExFolder folder)
   at Veeam.Archiver.Source.FolderProcessor.DoMailboxWork(CancellationToken cancel)
   at Veeam.Archiver.Source.MailboxAction.DoWork(CancellationToken cancel)
Mailbox processing failed: mailbox@name.com

Solution

Challenge

Cause

Solution

• vSphere 6.5 support. Veeam ONE now allows reporting and monitoring on vSphere 6.5 hosts and vCenter Server.
• Asian locales support. Veeam ONE console now supports installation on operating systems with Asian locales. Update 1 has been tested on all most common Asian locales by Veeam QC and validated by local Veeam teams of the corresponding locations.

• Memory demand for Hyper-V 2016 VMs. Veeam ONE now shows memory demand for VMs configured with static memory.

• Enhanced Backup Custom Infrastructure report. More Veeam backup object properties have been added to the report parameters list. 
• Enhanced VM Backup Status report. This report now allows filtering VMs based on the backup copy jobs.

• Veeam ONE Monitor Client is using wrong data samples to show performance graphs in the advanced scalability mode.
• Under certain conditions Veeam ONE service may crash when resolving all triggered alarms at the same time.
• Email notifications are sent only to first user email address specified in the alarms notifications section.
• Aggregation option cannot be switched to another value in the Veeam ONE Monitor Client.

• Backup copy jobs are treated as regular backup jobs for the “Suppress Veeam backup activity” option which leads to activating alarms suppression engine for production VMs.

• Datastore latency performance counter is showing wrong measurement units.
• Guest OS disk usage alarm is triggered for powered-off virtual machines.

• Hyper-V VMs guest OS disk monitoring alarm stops working when default settings are changed.
• Reads/sec, Writes/sec, IOPS performance counters from the Virtual Storage Device sub-system are not collected in the advanced scalability mode.
• "Local volume free space" alarm is falsely triggered during Veeam ONE service restart.
• Under certain conditions Veeam ONE falsely alarms on the age of existing VM snapshots.
• Under certain conditions Veeam ONE falsely alarms on VM snapshots that do not exist.

• Chargeback report pack is missing for users with limited access (tenants) to the virtual infrastructure.
• Alarms overview report cannot be generated after upgrading to Veeam ONE 9.5

• EMC DataDomain repositories are missing from all Veeam backup reports.
• "VMs Backed Up by Multiple Jobs" shows 01.01.0001 00:00 date as the latest job run for some VMs.
• Change Rate Estimation Rate report cannot be generated directly from Veeam ONE Monitor Client.

• Host Resource Usage Chargeback report for Hyper-V infrastructures treats Failover Cluster quorum disk as local. This disk should be ignored when reviewing the report.

• Veeam ONE Business View service attempts to collect virtual infrastructure data under user account which is used during web site login operation.

• Dashboard scheduling doesn’t work in distributed Veeam ONE installation when security certificates are missing from the server with Veeam ONE Web UI. To resolve this problem, import security certificates that are installed to Veeam ONE server to the server where Veeam ONE Web UI is deployed.
• Guest OS disk usage alarm is reset to its default thresholds after installing Update 1.

More Information

Challenge

Cause

• As an update over version 1.0.0.860 (You can check this, selecting About from the main menu in the Veeam Backup for Microsoft Office 365 interface.)
• As a new installation without a previous version

Solution

• Added a warning when a mailbox is selected which has an invalid Office 365 license.
• The backup fails with the error JET_errTempPathInUse.
• After a restore job, the iSCSI connection to a repository fails with JET_errInstanceUnavailable. The repository now reopens the database correctly.
• After the first of January, 2017, some mailboxes fail to backup with Object reference not set to an instance of an object error. The update also corrects the content of the existing repository databases.
• The configuration database consumes a lot of disk space: Circular logging is now used by default. The Veeam Backup for Microsoft Office 365 service will clear the old non-circular logs on the first start after the update.
• The support ID is now visible in the license information.
• The options dialog is shown incorrectly when a contrast theme is used.
• The System Menu appears at a random place when a non-default DPI is used.
• The headers on dialogs and wizards are too big because you use high DPI.

• When you want to restore items with Veeam Explorer for Microsoft Exchange, the Conversation History folder isn’t visible for restore.

More Information

Challenge

Starting in Mar. 2017, only case administrators and license administrators will be able to submit support cases. Please make sure to define valid case administrators for your Veeam licenses.

Customers are now able to list people who can manage support tickets on behalf of their company – case administrators. By adding a case administrator, you invite an employee of your company, a reseller or a third-party contractor to join you in managing your cases with the Veeam^® Support Team. Please note that case administrators can open cases, but they cannot manage your existing licenses.

Please also note Veeam Support is not able to change the case administrator for an account. This action can only be performed by license administrators (primary or secondary) for a given account.
 
If you are a primary or a secondary license administrator, you already have access to case administrators management on My Account. Here you can manage case administrators for all your licenses (Support IDs).

If you have lost access to the license administrator account or would like it to be changed, please create a licensing case.

Solution

How do you assign case administrators to a license? 

Click Create case administrator to invite someone to manage your support cases. A case administrator can be an employee of your company, a reseller or a third-party contractor. On the next page you will need to provide their e-mail address.

If the person to whom you would like to give case administrator rights does not have a profile on veeam.com, you may be asked to specify their name and company. If your case administrator's company is not yet registered on veeam.com some additional info may be requested. 

Once all the necessary details are provided you will need to select Support ID(s) to which the newly created case administrator will be associated. By doing so you give them the right to use the Support ID(s) when opening cases on behalf of your company. 

When the changes are saved, the new case administrator will be created and associated with the selected Support ID(s). Please note that if the specified user is not yet registered on veeam.com, they will have to complete the registration by following the corresponding link that they will receive by email. Should this be the case, the newly added case administrator will be able to access My Account and open cases only after confirming the registration.

If you would like to share a Support ID with one or several existing case administrators at the same time, please use the button Add administrator in the License view. Then, select administrators for this Support ID. Please note that the number of case administrators is limited – there can be no more than 20 case administrators per Support ID.  

You can also assign several Support IDs at a time to one of your case administrators. For this please click Add Support ID in the Case administrator view.

How do you remove case administrators from licenses? 

A case administrator can be removed from a license. Once this is done they will no longer be able to manage support cases for this Support ID (pic.1). Please note that you cannot remove other license administrators marked with a lock sign (pic.2).

You can also remove a case administrator from all your licenses at once by following the link Delete administrator in the Case administrator view. Please note that you will not see this link if the user is a license administrator. 

What rights do case administrators have? 

• Case administrators can open, update and close support cases for the licenses assigned to them
• Case administrators can also manage cases created by other case and license administrators 
• Case administrators can view your licenses but cannot manage them 
• Case administrators cannot view and manage other case administrators

More Information

Challenge

Cause

Solution

More Information

More information on HyTrust can be found here:

https://www.hytrust.com/
 

Challenge

Storage space is a concern for backup copy jobs in Veeam. If the repository is insufficiently provisioned, retention can fail, leading to the repository filling up and the job failing. If this happens, the job must often be restarted from scratch.

Cause

First and most important to note is that backup copy job retention happens differently from local backups. As a copy job is optimized for off-site storage, we assume there may be connection issues over a WAN that aren’t present on a LAN. Merges, as a result, are done via temp file, instead of writing the VIB incremental data directly into the VBK full.
 
This temp file is going to be as big as (if not slightly larger than, due to changing data) the VBK. Once the merge is complete, the VIB and the old VBK are deleted and the temp file takes their place.
 
For GFS retention, every Weekly, Monthly, Quarterly, and Yearly backup is itself a VBK, and of similar size.

Solution

To estimate the space requirements for a backup copy job:
 

• Add the sizes of a full backup of all local jobs that will be included in the copy job. You may end up with a slightly smaller copy job due to compression and deduplication of similar blocks, but it’s preferable to plan for more.

• Determine how many full backups you’ll have:

  • One full for the regular retention

  • One full for every Weekly, Monthly, Quarterly, and Yearly GFS archival point

• Add one more point to the total for the temp file used in the merge process

• Multiply that total by the size estimate for the full backup. Ensure your repository will have space for at least this much data, and a bit more for incrementals/variance in data.

 
Example:
 
Consider two local backup jobs being written to a single backup copy job. A full backup of the first job is around 750GB and a full backup of the second is 500GB. Add the two together. 1.25TB should be accounted for the combined full of the copy job, and a minimum of another 1.25TB should be allowed for the merge.
 
The same two local backup jobs have a combined daily rate of change of 170GB (Local Backup 1, on a given week, has increments sized 100, 120, 100, 150, 125, and 175GB for an average of 128.334~ and Local Backup 2 has increments of 50, 40, 55, 30, 45, and 30GB for an average of 41.667). If the backup copy job will retain 14 points, allow at minimum 14 * 170GB or 2.38TB for increments. Given that one cannot consistently predict rates of change, it’s best to oversize here rather than to be left wanting.
 
Assuming no GFS retention on this example job, the backup copy repository should have:
 
[1.25TB (full)] + [1.25TB (merge overhead)] + [2.38TB (incremental points)] = 4.88TB
 
If we add GFS retention of 4 monthly points, those four full restore points add 4 * 1.25TB = 5.0TB. In this case we would need:
 
[1.25TB (full)] + [5.0TB (GFS points)] + [1.25TB (merge overhead)] + [2.38TB (incremental points)] = 9.88TB
 
As a general rule, a bit of additional space is recommended for unforeseen issues. Insufficient sizing for a merge can lead to running out of space, and if a copy job repository ends up with insufficient space to perform a merge—and subsequently is filled with more increments than specified by retention—the only recourse in almost every case is to clear the repository and let the copy job start with a new full, or provision more space for the repository if it is scalable.

Challenge

Cause

Solution

Challenge

Product Information: 

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

Solution

Product Details: 

Model number: 4.0.2-80 
Number of Drives: 25 
Drive type: 400 GB SSD 
Firmware version: 4.x 
Additional support: Any hardware configuration with an equal or greater hardware configuration
General product family overview: The XtremIO Storage Array from Dell EMC is an all-flash system that leverages a scale-out architecture. The system is built via building blocks, called X-Bricks, which are SAN appliances that can be clustered together to grow performance and capacity as required. The Dell EMC XIOS operating system balances data across all solid-state arrays and supports features such as deduplication, compression, and snapshots. The all-flash architecture is viable for use cases including virtual desktop infrastructures (VDI), server environments, or database and analytics workloads. 

Veeam Details: 

Veeam Build Number: 9.0.0.902 
Veeam Settings:  
Repository Type: Windows 
Deduplication: No 
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: Dell EMC 
Company overview: As a member of the Dell Technologies family of businesses, Dell EMC serves a key role in providing the essential infrastructure for organizations to build their digital future, transform IT and protect their most important asset, information. Dell EMC enables our enterprise customers’ IT and digital business transformation through trusted hybrid cloud and big data solutions, built upon a modern data center infrastructure that incorporates industry-leading converged infrastructure, servers, storage and cybersecurity technologies. 

Dell EMC brings together Dell’s and EMC’s respective strong capabilities and complementary portfolios, sales teams and R&D. We seek to become the technology industry’s most trusted advisor, providing capabilities spanning strategy development, consultative services and solution deployment and support to help our customers and partners drive the digital transformation of their businesses.

Challenge

Product Information: 

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

Solution

Product Details: 

Model number: CS8000 
Number of Drives: 10 
Drive type: SAS 
Firmware version: V6.1A7120-SP03 
General product family overview: ETERNUS CS8000 is a datacenter solution for backup storage for mainframe and open systems. Its intelligent process automation and pooling of storage capacity reduces the TCO for complex backup environments by 40%. Unique scalability in capacity and performance makes ETERNUS CS8000 a viable solution, delivering ongoing cost savings. 

http://www.fujitsu.com/fts/products/computing/storage/dataprotection/cs8000/  

Veeam Details: 

Veeam Build Number: 9.5 
Veeam Settings:  

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

More Information

Company Information: 

Company name: Fujitsu 
Company overview: Fujitsu is the leading Japanese information and communication technology (ICT) company, offering a full range of technology products, solutions and services. Approximately 156,000 Fujitsu people support customers in more than 100 countries. We use our experience and the power of ICT to shape the future of society with our customers. Fujitsu Limited (TSE: 6702) reported consolidated revenues of 4.7 trillion yen (US$40 billion) for the fiscal year ended March 31, 2016. For more information, please see http://www.fujitsu.com