multi-OS restore fails on Hyper-V 2008R2

June 1, 2016, 6:31 am

≫ Next: Veeam ONE Monitor SNMP MIBs

≪ Previous: No updates from gateway servers

$

0

0

Challenge

To restore individual files and folders from file systems other than Microsoft Windows, you can use the multi-OS File-Level Restore wizard. To restore files from VM guest OS, Veeam Backup & Replication uses a proxy appliance. The proxy appliance is a helper VM running a stripped down Linux kernel that has a minimal set of components. When the appliance is booting up you may open a console and see the following message:
 

Unable to obtain settings by DHCP for interface eth0: ... No such device

Cause

This is a bug in the Linux kernel of the appliance that occurs only in Hyper-V 2008 R2.
 

Solution

This is known issue which will be fixed in the next version of Veeam Backup & Replication.

There are two possible workarounds currently :

1. Update your Hyper-V server to Windows 2012 R2

2. Use Instant Recovery, connect VM to an isolated network and retrieve needed files in any convenient way

More Information

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748609

---

Veeam ONE Monitor SNMP MIBs

June 2, 2016, 3:30 am

≫ Next: Start new backup set

≪ Previous: multi-OS restore fails on Hyper-V 2008R2

$

0

0

Challenge

Need to forward events which are caught by Veeam Monitor to any 3rd party network monitoring product.

Cause

In this case you need an SNMP MIB file for Veeam One Monitor which is provided separately.

Solution

Obtain the SNMP MIB file from here.

More Information

Monitored SNMP traps contained in the MIB file are in SNMP v1 format such as the examples presented below:
 

vmPoweredOn  - "This trap is sent when a virtual machine is powered ON from a suspended or a powered off state.
vmPoweredOff - "This trap is sent when a virtual machine is powered OFF."
vmHBLost - "This trap is sent when a virtual machine detects a loss in guest heartbeat."
vmHBDetected - "This trap is sent when a virtual machine detects or regains the guest heartbeat."
vmSuspended - "This trap is sent when a virtual machine is suspended."

The following are accompanying variables for these traps:
 

vmID - "This is the ID of the affected vm generating the trap. If the vmID is non-existent, (such as for a power-off trap) -1 is returned."
vmConfigFile - "This is the config file of the affected vm generating the trap."

The following traps are sent from VMware vCenter:
 

vpxdTrap - "This trap is sent when entity status changed."
vpxdTrapType - "This is the trap type in the preceding traps."
vpxdHostName - "This is the name of the host in the preceding traps."
vpxdVMName - "This is the name of the VM in the preceding traps."
vpxdOldStatus - "This is the old status in the preceding traps."
vpxdNewStatus - "This is the new status in the preceding traps."
vpxdObjValue - "This is the current object value in the preceding traps."

If you have any questions, contact Veeam Customer Support.

Start new backup set

June 6, 2016, 8:42 am

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

≪ Previous: Veeam ONE Monitor SNMP MIBs

$

0

0

Challenge

The need is presented that requires that a new backup set be created for a job.

Solution

*NOTE: Please ensure that the destination will have the space needed to start a new backup set.
 
1.   Find where the backup files are currently located.



The location of the backup files can be found by finding the backup set entry under:
Backups>Disk
Within the properties of the backupset you will find the location of the backup set on storage.

2.   Remove the current backup set from the backups section.



Right-click on the backup set and choose “Remove from backups”, this will leave the backup set on storage but remove it from the Veeam console and all the jobs to start a new backup set.

3.   Rename the folder where the backup files are located from step 1.
4.   Run the job to start a new backup set.

More Information

Important Notes:

• The files that we removed from the console will no longer be affected by retention policy and will stay where they were left until they are manually removed.

• There may be multiple entries under Backups>Imported for the files that were removed from backups previously then were brought back in after a rescan of the repository.
• For Backup Copy Jobs with Archival fulls enabled - Make sure to check the box to remove archived fulls when removing from configuration. Otherwise a new incremental from the most recent archived restore point will be created. 

Veeam Backup & Replication - Steps to Compile and Upload Logs

June 7, 2016, 6:01 am

≫ Next: vCenter Migration Utility

≪ Previous: Start new backup set

$

0

0

Challenge

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

Note: The images below are for v7, the GUI options are the same in v8.

Solution

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

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

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



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

 

More Information

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

• Windows 2003, XP – C:\Documents and Settings\All Users\Application Data\Veeam\Backup\

• Windows Vista, 7 - C:\Users\All Users\Veeam\Backup\

• Windows 2008/2008 R2/2012 - C:\ProgramData\Veeam\Backup\

• Linux - /var/log/VeeamBackup/

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

• The task's folder located in the parent directory, zipped. This will contain all relevant job/task/agent data.

• All logs from the parent directory named svc.*.log, util.*.log, as well as the VeeamBackupManager.log and VeeamShell.log
   

vCenter Migration Utility

June 9, 2016, 4:47 am

≫ Next: Web plugin troubleshooting guide

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

$

0

0

Challenge

If a Virtual Machines MoRef is changed due to migration to new vCenter / inventory change in vCenter, you would receive the error "Object "vmname" is not found".  Please see KB1299 for more details.

This utility is designed to assist in re-mapping the MoRef ID's of the Virtual Machines you are backing up and/or replicating using Veeam Backup & Replication, so that incremental chains remain intact, after an inventory change in VMware vSphere vCenter. 

Please note that this utility is provided as a courtesy, and is not officially supported by Veeam Technical Support.  Use at your own risk.

Cause

Veeam Backup & Replication tracks Virtual Machines in its jobs by a Managed Object Reference ID (MoRef), which will change when moved to another vCenter, or removed and re-added to inventory.

Solution

Please download this bundle: tool and instructions.  Before using this tool, it is highly recommend to take a configuration backup of your VeeamBackup database. 

Web plugin troubleshooting guide

June 17, 2016, 5:43 am

≫ Next: SP Per-VM Licensing Exceeded

≪ Previous: vCenter Migration Utility

$

0

0

Challenge

Web plugin is a new feature, which has little in common with other features and it may seem to be difficult to troubleshoot. It is suggested to follow this guide rather than trying to analyze error message, as it is not very informative and almost always misleading.

 

Solution

Known issues and solutions

Unable to connect Enterprise Manager
Make sure that Enterprise Manager and RestAPI services are running. Please disable proxy in Internet Explorer on vCenter and EM servers, disable firewalls.
If it doesn't help, then review plugin log on vCenter, if you see something like "Certificate error: Remote servers certificate thumbprint does not match the thumbprint stored in the application settings" then
1. Perform plugin uninstall with cleanup(see section below)
2. Reinstall Enterprise Manager and select required certificate during installation

Invalid SSO Token
Steps to resolve:
1. Make sure, that EM and RestAPI services are running under domain account with local administrator priveleges.
2. Add user(that is used to log on to vSphere web client) in EM Roles explicitly.
If it doesn't help, then analyze SSO token.

Server error: null
Plugin files are not completely installed, corrupted or 2 versions of plugin are installed. If you have vShpere 5.5 then plugin might have old version.
Steps to resolve:
1. Verify plugin version installed in EM(Configuration - vCenter Servers) and EM version(EM - configuration - about - Veeam Backup Enterprise Manager Service). For vSphere 5.5 it should be not lower than 7.0.0.764. If needed, apply the latest patch once again. If Enterprise Manager and Veeam B&R are installed on different servers, make sure that the latest patch is installed on both servers.

2. Perform Plugin uninstall with cleanup
3. Install plugin

Installation fails with message "Check if there is an existing one already installed" but the plugin is not already installed
If Svc.VeeamBES.log contains “NoPermissionFault”: Make sure the user account that is accessing the vCenter is listed in the vCenter permissions at the root level (or is part of a group at that level), and is assigned to a role with Extension privileges.
If Svc.VeeamBES.log contains “null reference exception”: In IIS Manager on the Enterprise Manager server, make sure that an SSL certificate is assigned to the HTTPS binding for the VeeamBackup site.



Generic troubleshooting guide

If the issue is not listed in known issues section or it didn't help, then follow this guide before escalating a ticket.
1. Disable proxy in IE and firewall both on EM and VC
2. Verify that EM version is current (EM - configuration - about - Veeam Backup Enterprise Manager Service) and install latest patch if needed. In case of upgrade, uninstall plugin from EM, restart vSphere web client service and install it again.
3. Add user(used to log on to VC) to EM roles explicitly
4. Make sure that RestAPI and EM services are running under domain account with local admin priveleges

Check if RestAPI service is available and responding:

1. Login to EM server and open in browser https://<em-server>:9398/web. You should receive an XML. Username and password may need to be entered. You can safely ignore untrusted certificate warning.

2. If this page doesn't open, check if RestApi service is started

3. If service is started, run netstat -abn from command line to check if port 9398 is listened by Veeam.Backup.EnterpriseService.exe

4. Try to open "http://<em-server>:9399/web", if this page opens while "https://<em-server>:9398/web" doesn't - you need to re-install SSL certificate for RestAPI (see corresponding chapter below - RestAPI certificate change)

If nothing, listed above helps:
1. Perform plugin uninstall with cleanup(see section below)
2. Reinstall EM
3. Install plugin
If the above steps do not resolve the issue, please contact Veeam Support.


Thoubleshooting steps

Plugin uninstall with cleanup
1. Uninstall plugin from EM
2. Restart vCenter Web Client Service. On windows server from services.msc console, on VC appliance from Vcenter Management web page
3. Remove all pieces of web plugin, that were not removed. Open SSH session to VC appliance and remove all enties that are returned by find / -name '*veeam*'. On windows server remove all files and folders containing veeam in %programdata%\vmware and %programfiles%\VMware

SSO token analyze
1. Open Svc.VeeamRestAPI.log
2. SSO token is Base64 encoded. Copy encoded text between "Failed to authorize user. SSO token: [" and closing "]" into notepad and remove all occurrences of "\n" (replace to empty string)
3. Decode resulting Base64 string. You can use http://www.base64decode.org/ for that.
4. In the resulting xml look for tag "saml2:Issuer". There is a URL to the VC SSO service. Verify if the URL points to the VC. Try opening it from Veeam server. Response file in XML format should be opened or downloaded, depending on browser settings. Certificate not trusted error can be safely ignored. If the URL is wrong, then customer should reconfigure SSO.

RestAPI certificate change

To view all SSL certificates assigned on different ports, run command prompt on EM server "netsh http show sslcert".

Locate 2 records:

0.0.0.0:9443 (stands for Enterprise Manager)

0.0.0.0:9398 (RestAPI service)

1. Copy "Application ID" value from the 0.0.0.0:9398 section

2. Copy "Certificate Hash" value from 0.0.0.0:9443 section

3. Execute "netsh http delete sslcert ipport=0.0.0.0:9398" to delete existing cert

4. Execute "netsh http add sslcert ipport=0.0.0.0:9398 certhash=<hash> appid=<id>"(where <id> and <hash> are values, gathered before) to set new certificate

More Information

Required logs
1. (From EM) Svc.VeeamBES.log
2. (From EM) Svc.VeeamRestAPI.log
3. (From VC) VMWare web client log(logs location on VC - http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2004090
4. (From VC) For vSphere 5.1 or older, web plugin logs from VC. Should be located in the same folder, where VMWare Web Client logs are. For vSphere 5.5 there is no dedicated Veeam Plugin log, info is written in Web Client log instead
5. (From VC) For vSphere 6 please see - https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2110014


 

SP Per-VM Licensing Exceeded

June 20, 2016, 12:09 pm

≫ Next: How-To: Manually Repair a VMware Replica created by Veeam

≪ Previous: Web plugin troubleshooting guide

$

0

0

Challenge

SP Tenants receive error messages that state ‘Service Provider has exceeded the licensed VM count’
 
Error that appears in SP report:
--------------------------------
 
Licensed Cloud Connect Backup VM count has been exceeded. We will stop accepting data for all VMs above licensed quota at <date>. To ensure uninterrupted service, please acquire and install a license file with larger number of VMs, or decrease the number of protected VMs by disabling or deleting some tenants.





Error(s) that occurs on Client Side job:
---------------------------------------
 
Error: Cannot backup this VM because your service provider has reached licensed VM limit.



 

Cause

The Veeam Cloud Connect service provider license is consumed only by active VMs. An active VM is a VM that has been successfully backed up, copied or replicated by an active (not disabled) tenant with an active lease period (if lease is set up). The number of restore points created by tenants or the number of jobs that process VMs does not consume the license. For example, if a tenant processes the same VM with several backup jobs, this VM is considered as 1 active VM.
 
The total number of active VMs must not exceed the total number of VMs in the license. Depending on the number of active VMs, the Veeam Cloud Connect service provider license can be in one of the following states:
 
Normal: the total number of active VMs does not exceed the total number of VMs in the license. Tenants can freely process existing and new VMs: back up and copy VMs to the cloud repository and replicate VMs to cloud hosts.
 
Grace: after the total number of active VMs exceeds the total number of VMs in the license, the license is put to the Grace state. Tenants can still process existing and new VMs regardless the number of VMs in the license. VMs that exceed the license limit are tracked separately for future FIFO (First In First Out) processing. If free license slots appear due to older VMs no longer being protected, VMs from the FIFO list occupy free license slots on the FIFO basis.
 
The Grace state is valid for 60 days. After the 60-days period expires, the license is put to the Post grace state.
 
Post grace: the total number of active VMs exceeds the total number of VMs in the license and the grace period has expired. Tenants can back up, copy and replicate only those VMs that have already been backed up, copied and replicated while the license was in Normal and Grace states. VMs that exceed the license limit are no longer processed.
 
The license in the Post grace state can get to the Normal state if the SP obtains and installs a license for a greater number of VMs.
 
Recovery: During the Grace period, the SP may return to the license limits. This can happen if the number of active VMs reduces. In this situation, the license it put to the Recovery state. Tenants can back up and copy VMs to the cloud repository and replicate VMs to cloud.
 
The Recovery state is valid for 1 day. After that, Veeam Backup & Replication changes the license state:
 
If the number of active VMs remains within the license limits during 1 day, the license is put back to the Normal state.
 
If the number of active VMs exceeds the number VMs in the license at any time during 1 day, the license is returned to the Grace state. Veeam Backup & Replication does not start the Grace period anew: it resumes the earlier Grace period. For example, the license was first put to the Grace state on June 10. On June 13 the number of active VMs reduced and the license was put to the Recovery state. On June 14 the number of active VMs was again exceeded and the license is returned to the Grace state. The license will be in the Grace state till August 10. After that, the license will be put to the Post grace state.
 

Solution

The number of active VMs in the Veeam Cloud Connect service provider license can reduce for one of the following reasons:
 
The SP disables or removes a tenant account. As a result, all tenant’s VMs become inactive and the equal number of VMs is revoked for other tenants.
 
The SP resets the VM count for the tenant. As a result, the corresponding number of VMs becomes inactive and the equal number of VMs is revoked for this tenant or other tenants.
 
A tenant removes backups and replicas created for one or several VMs on the cloud repository and cloud host. As a result, the corresponding number of VMs becomes inactive and the equal number of VMs is revoked for this tenant or other tenants. However, when a tenant runs a job that processes a VM for which backup and replica were deleted, such VM becomes active, and the number of active VMs in the SP license increases.
 
To reduce the number of managed VMs in a Hosting license, the SP can do the following
 
Remove backup jobs that were configured on tenant's Veeam backup server and are no longer required (or exclude specific VMs from backup jobs).
Remove VM backups created by these jobs from the Veeam backup repository.

More Information

https://helpcenter.veeam.com/backup/cloud/cloud_connect_sp_license.html
https://helpcenter.veeam.com/backup/cloud/sp_reduce_vms.html
 

How-To: Manually Repair a VMware Replica created by Veeam

June 22, 2016, 6:06 am

≫ Next: Installed Reporter and Access is Denied

≪ Previous: SP Per-VM Licensing Exceeded

$

0

0

Challenge

This article explains how to manually revert a replica to its base disks allow it to be remapped to a replication job and used as a seed in the case that the replicas snapshot files become corrupt.
 
NOTE: The actions take here should never be performed on a production server as a data loss could occur. These actions are only to be taken on a replica as Veeam has the ability to bring the replica up to date.
 
The following are error messages that may prompt the use of this KB article:
• A replication job may fail with a message such as “Unable to repair replica VM.”
• When the replication job attempt to create a snapshot on the replica it fails with “File or folder already exists.” In this case most often there is a loose file that is named like a snapshot but not associated with the replica. E.g. a file named DC01-0000001.VMDK, and when VMware goes to create the first snapshot on the replica it can’t because the file it was going to create already existed.
•Replication job fails with “Invalid Snapshot Configuration,” and you are able to determine that the error is coming from the replica by checking the replicas Tasks & Events.
•Replication job fails “CID mismatch error: The parent virtual disk has been modified since the child was created,” and you are able to determine that the error is coming from the replica by checking the replicas Tasks & Events.

Cause

An old or orphaned Snapshot file is linked to the vmx, and a new Snapshot is trying to use that file name.

Solution

Please be aware that as an alternative to performing the steps below, you may first attempt to clone the faulty replica within VMware, if it succeeds map the Replication job to the clone of the replica.
 
 
Note: Prior to beginning:
•Stop all replication jobs to target location of the replica in question.
•Manually check each target side proxy for stuck replica hotadded disks. (Consider switching the target proxies to use Network transport mode to prevent this if it becomes a problem). See Removing Stuck VMDK’s from the Veeam Proxy for details.
 
──────────────────────────────────────────────────────────
Gather Information
──────────────────────────────────────────────────────────
 
1. Edit the Replica
2. Note what disk files correlate to each SCSI ID.
      Example:
      [Datastore1] DC01_replica\DC01-00000023.vmdk     on SCSI0:0
      [Datastore1] DC01_replica\DC01_1-00000023.vmdk on SCSI0:1
      [Datastore2] DC01_replica\DC01-00000023.vmdk     on SCSI0:2
 
──────────────────────────────────────────────────────────
Prepare the Replica
──────────────────────────────────────────────────────────
1. Open the Snapshot manager and starting with the oldest snapshot delete the snapshots one at a time. The intention here is to get as much new information in to the base disks as possible. At some point there will be a snapshot that will not remove.
2. If there are any snapshots left in the snapshot manager try using the Delete All option in snapshot manager.
3. Use the consolidate function to consolidate any orphaned snapshots.
 
──────────────────────────────────────────────────────────
Preparing Veeam Backup & Replication
──────────────────────────────────────────────────────────
Within the Veeam console under Replicas find the replica that you will be repair and right-click it, from the context menu choose “Remove from replicas…”
 
After you use the “Remove from replicas…” function it will remove the VM from the Replication job.
You will have to manually add the VM back to the replication job.
 
──────────────────────────────────────────────────────────
Detach Snapshot Disks and Attach Base Disks
──────────────────────────────────────────────────────────
1. Edit the replica, and select each of the disks and click remove. It will put a strikethrough the drive and show the word (removing).
2. After selecting all the disks for removal, press OK.
3. Edit the replica again, now reattach the base disks to the replica, choose to add an existing disk and then navigate to the location of the base disks for the replica. Attach them to the same SCSI nodes that were noted earlier.
 
──────────────────────────────────────────────────────────
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.

 

---

Installed Reporter and Access is Denied

June 22, 2016, 11:04 pm

≫ Next: Install fails with “Error occurred during certificate processing.”

≪ Previous: How-To: Manually Repair a VMware Replica created by Veeam

$

0

0

Challenge

When trying to load Reporter for the first time, you receive the message when trying to view http://hostname:1239.

Access is Denied 
  Error message 401.2.: Unauthorized: Logon failed due to server configuration. Verify
that you have permission to view this directory or page based on the credentials you
supplied and the authentication methods enabled on the Web server. Contact the Web
server's administrator for additional assistance. 

Solution

This is a 401.2 error from IIS (no access).  http://support.microsoft.com/kb/253667  
 

Per our user guide we require the following permissions.  

Required Permissions 

- To be able to access SQL backend data, the clients should be members of the Veeam Reporter Administrators or Veeam Reporter Viewers local groups on the Veeam Reporter Server console. To learn more about the user groups, see the Veeam Reporter User Groups section.

 

Per our user guide we require the following software versions.  

Required Software

Microsoft .NET Framework 3.5 or later

Microsoft Internet Information Services (IIS) 5.1 or later

Microsoft Internet Explorer 6.0 or later, or Mozilla Firefox 3.5 or later

Microsoft Office 2007 or later (some reports cannot be viewed with Excel 2003)

Microsoft Visio 2003 or later

PDF viewer

Note: If using IIS 7.0, you will need features: IIS 6.0 Management Compatibility, Windows Authentication support, ASP.NET 
 

Our user guide can be found here: http://www.veeam.com/files/guide/veeam_reporter_4_0_2_user_guide.pdf

 

We also encourage local admin for the installation to make sure we have the correct permissions to install on top of IIS correctly.

Install fails with “Error occurred during certificate processing.”

June 23, 2016, 10:54 am

≫ Next: Starting a SureBackup job in Troubleshooting mode

≪ Previous: Installed Reporter and Access is Denied

$

0

0

Challenge

Install fails with “Error occurred during certificate processing.”



 

Cause

Insufficient rights to the MachineFiles folder on the Veeam server. In the BackupSrvLog.log you will see the following entry:
 
Generating a 2048 bit RSA private key
...........................................+++
........+++
writing new private key to 'C:\Users\<user>\AppData\Local\Temp\openssl\ca.key'
-----
 
***Veeam***  Command line: '"C:\Users\<user>\AppData\Local\Temp\openssl\openssl.exe" pkcs12 -export -inkey "C:\Users\<user>\AppData\Local\Temp\openssl\ca.key" -in "C:\Users\<user>\\AppData\Local\Temp\openssl\ca.crt" -out "C:\Users\<user>\\AppData\Local\Temp\openssl\client.pfx" -name "Veeam Backup Server Certificate" -password pass:*****'.
***Veeam***  WARNING: can't open config file: /usr/local/ssl/openssl.cnf
Loading 'screen' into random state – done
[…]
***Veeam***  Generating certificate...
***Veeam***  Creating key pair for self-signed certificate...
***Veeam***    Result: 0x80090016.Trying to create new key container...
***Veeam***  VmWinError has been occurred. Error: 5.
Error occurred during certificate processing.
 

Solution

1. On the Veeam server navigate to C:\ProgramData\Microsoft\Crypto\RSA\
2. Right click on MachineKeys and select Properties and the select the Security tab
3. Grant Everyone ‘Full Control’
4. Retry the installation

Starting a SureBackup job in Troubleshooting mode

June 23, 2016, 10:58 am

≫ Next: How to configure Veeam for rotated media

≪ Previous: Install fails with “Error occurred during certificate processing.”

$

0

0

Challenge

If some VM fails to be verified automatically, you can start it manually for troubleshooting.
 
For example, if the VM fails to be verified because a particular test fails, you can start it in troubleshooting mode, and then open the VM console to check whether some service does not start, or a software firewall is blocking connections, etcetera.

Solution

To start a SureBackup job in troubleshooting mode, perform the following steps:

1.    Double-Click on the SureBackup job to open the statistics for the previous session.
2.    Right-click on the VM you want to troubleshoot, then click "Start".

If the application group has already been powered off by that time, it will be started again. After that, you can open the VM console and perform verification and testing manually.

How to configure Veeam for rotated media

June 23, 2016, 12:00 pm

≫ Next: How to log in to the Virtual Proxy Appliance

≪ Previous: Starting a SureBackup job in Troubleshooting mode

$

0

0

Challenge

To fulfill the 3-2-1 rule’s requirement for an offsite backup, a repository has been pointed to removable storage media (such as USB hard drives or RDX disks). The action of swapping to a new medium causes Veeam Backup & Replication jobs to fail because the job cannot find a file.

Cause

By default, Veeam Backup & Replication assumes that if recent files are missing, the job should fail. This way, the job provides a notification that something is wrong instead of taking any action.

Solution

For an introduction to Veeam Backup & Replication’s options for rotated media, consult the user guide. The following notes assume the option for rotated media is enabled in the repository advanced settings.
 
Retention Options on Windows-type Repositories
 
There are three options:

1. Default backup job behavior;
2. Default backup copy job behavior;
3. Deleting files when disks are rotated.

 
Backup jobs will always create active full backups immediately after disks are rotated. This option requires that each storage medium has sufficient disk space for at least two full backup files.
 
With backup copy jobs, when a new disk is detected, the job will only create a full backup if there are no valid backups on the disk for that job. If an existing backup set is detected, the backup copy job will create an incremental backup file that contains the difference between the current restore point and the most recent previous restore point on that disk. As a result, if disks are re-used frequently, the incremental backup files will be similar in size to increments on non-rotated media; if a disk contains very old restore points, the first new incremental backup copy may be almost as large as a full backup.
 
With both job types, Veeam Backup & Replication tracks restore points stored on all disks that have been used with the job. If outdated restore points are stored on the current disk, they are only deleted at the end of the current job session.
 
For example, consider a job that creates two restore points per day, with disks swapped once per day, a total of three disks, and retention policy set to 6 restore points.

• A forward incremental backup job creates a full backup file and an increment on each of the three disks over the first three days. On the fourth day, the first disk is re-used. A new full backup file is created. There are now 7 points across all disks, so retention policy is met, but the initial full backup cannot be deleted because an incremental file is dependent on it. After another restore point is created, the older two files on disk 1 are deleted by retention policy.
• A backup copy job also creates a full backup file and an incremental file on each of the three disks over the first three days. On the fourth day, the first disk is re-used. A new incremental backup file is created, and the oldest incremental file is merged into the full backup file.

 
If a disk does not contain enough space for a new backup file, the job will fail instead of deleting old files. This can be avoided by deleting old files as soon as the disks are swapped. This can be done manually, via pre-job script, or with the registry setting described below.
 
 
Retention on All Other Repositories
 
By default, repositories configured for rotated media do not delete any backup files when disks are swapped. If a disk containing a previous backup is to be re-used, but lacks sufficient available space for new backup files, the old files must be deleted manually, or by a pre-job script.
 
Retention policy is enforced, but only on the current backup chain. For example, consider a backup copy job that creates restore points every hour, with disks swapped once per day, and retention policy set to 6 restore points. Once there are 7 restore points on the current disk (a full backup file and 6 incremental backup files), the oldest increment is merged with the full backup file so that there are 6 restore points on disk. The disk is swapped out for a new one, and the process repeats. When the first disk is re-used, the 6 backup files still on the disk are ignored. A new full backup file is created, and a new chain of incremental files. At the end of the day, there are 12 restore points on disk, with only the most recent 6 visible in the Veeam Backup & Replication console.
 
An alternative behavior is available as a registry setting (below).
 
Deleting Files When Disks are Rotated
 
When this registry setting is enabled (set to 3 or 5), jobs using a repository configured for rotated media will maintain retention normally until the job detects that previously-available files are missing.
 
Create this value on the Veeam Backup and Replication server:
 
HKLM\Software\Veeam\Veeam Backup and Replication
ForceDeleteBackupFiles (DWORD)
 
Set to 3 to make the job delete the entire contents of the backup job’s folder only.
Set to 5 to make the job delete the entire contents of the root backup repository folder, potentially deleting any files belonging to other jobs. Note that if the backup repository points at the volumes root folder, the entire volume's contents are erased.
 
The Veeam Backup Service must be restarted after creating this registry value. Make sure no jobs or restores are running before restarting this service.
 

How to log in to the Virtual Proxy Appliance

June 23, 2016, 12:00 pm

≫ Next: Veeam Backup & Replication event set for Kaseya

≪ Previous: How to configure Veeam for rotated media

$

0

0

Challenge

For troubleshooting or advanced configuration, you may need to log in to a Linux appliance deployed by Veeam Backup & Replication.   Linux appliances are used by Veeam Backup & Replication for several purposes: In Surebackup, the Virtual Lab proxy appliance routes network traffic between isolated and production networks. In Multi-OS File Level Restore, the proxy appliance mounts virtual machine disks. In Cloud Connect Replication, the network extension appliances route traffic between tenant networks and service provider networks.

Solution

You must log in to the appliance as root. You can set a password in the credentials manager, or use the default password.   Setting Passwords   To set the password for the particular type of appliance, edit it in the credentials manager.   To set the password for Surebackup (Virtual Lab) and Multi-OS FLR appliances, edit the record with the description “Helper appliance credentials”. To set the password for network extension appliances, edit the record with the appropriate description: “Tenant-side network extension appliance credentials” or “Provider-side network extension appliance credentials”. Only Cloud Connect Service Providers can set the password for provider-side appliances.   For Surebackup and Cloud Connect, you must re-deploy the appliance before you can use the new password. The multi-OS FLR appliance does not persist between restore sessions, so to use the new password you only need to close the file browser and restore again.   The password will be applied to all newly-deployed appliances. It is not possible to specify different passwords for different instances of the same appliance type.     Default Password   You can only use a default password if no password has been set in the credentials manager.   To determine the default password for a particular appliance: 1) Start with the appliance name as it can be seen in the infrastructure view in the hypervisor; 2) Replace any “.” or "_" or space or parenthesis with “-“, but skip a trailing - (if any); 3) Add “_r” to the end.   For example, if your appliance’s vm name is “network.extension_appliance(cloud connect)”, the default password would be “network-extension-appliance-cloud-connect_r”.

Veeam Backup & Replication event set for Kaseya

June 24, 2016, 5:19 am

≫ Next: Unable to View Connection String for Veeam Reporter and Veeam Business View Websites in IIS Manager

≪ Previous: How to log in to the Virtual Proxy Appliance

$

0

0

Challenge

Monitoring Veeam Backup & Replication activity through Kaseya.

Solution

To monitor Veeam Backup & Replication please confirm you are running version 9.0. You can check this under Help | About in Veeam Backup & Replication console.

Kaseya version 6.3 or later is required.

Download the event sets below and import them to Kaseya to monitor backup server activity. Download

Veeam Backup & Replication.xml - all events
Veeam Backup & Replication Alerts.xml - errors and warnings only

Events Descriptions:

Event ID	Name	Description	Severity	Job Type
23010	Job created	The [Job Type] job “[Job Name]” has been created.	Info	Backup, Replication, Backup copy
23050	Job modified	The [Job Type] job “[Job Name]” has been modified.	Info	Backup, Replication, Backup copy
23090	Job deleted	The [Job Type] job “[Job Name]” has been deleted.	Info	Backup, Replication, Backup copy
23110	Job objects added	“[object count]” objects  has been created for "[Job Name]".	Info	Backup, Replication, Backup copy
32120	Job objects deleted	“[object count]” objects  has been deleted for "[Job Name]".	Info	Backup, Replication, Backup copy
23130	Job objects modified	“[object count]” objects has been modified for "[Job Name]".	Info	Backup, Replication, Backup copy
23210	Surebackup job created	The SureBackup job “[Job Name]” has been created.	Info	SureBackup
23220	Sure backup job modified	The SureBackup job “[Job Name]” has been modified.	Info	SureBackup
23230	Sure backup job deleted	The SureBackup job “[Job Name]” has been deleted.	Info	SureBackup
23310	Sure backup objects added	“[object count]” jobs  has been created for "[Job Name]".	Info	SureBackup
23320	Sure backup objects deleted	“[object count]” jobs  has been deleted from "[Job Name]".	Info	SureBackup
23330	Sure backup objects modified	“[object count]” jobs has been modified for "[Job Name]".	Info	SureBackup
110	Backup job started	<Job type> job '<Job name>' has been started.	Info
190	Backup job finished	The <Job type> Job '<Job name>' has finished with <State name> state.	Info,Warning,Error
150	Backup task finished	VM "[TaskName]" task has finished with '[StateName]' state.	Info	Backup, Replication, SureBackup
114	Tape backup job started	<Job type> job '<Job name>' has been started.	Info
194	Tape backup job finished	The <Job type> Job '<Job name>' has finished with <State name> state.	Info,Warning,Error
210	Restore session started	Restore session has been initated by '<User name>'.	Info
250	Restore Vi task finished	Restore for '<Object name>' has finished with <State name> state	Info,Warning,Error
251	Restore Hv task finished	Restore for '<Object name>' has finished with <State name> state	Info,Warning,Error
290	Restore session finished	The restore session has finished with <State name> state.	Info,Warning,Error
310	Sure backup job started	<Job type> job '<Job name>' has been started.	Info
350	Sure backup Vi verification task finished	VM [<Vm name>] verification task has finished with [<State name>] state.	Info,Warning,Error
351	Sure backup Vi validation task finished	VM [<Vm name>] validation task has finished with [<State name>] state.	Info,Warning,Error
360	Sure backup Hv verification task finished	VM [<Vm name>] verification task has finished with [<State name>] state.	Info,Warning,Error
361	Sure backup Hv validation task finished	VM [<Vm name>] validation task has finished with [<State name>] state.	Info,Warning,Error
390	Sure backup job finished	The <Job type> Job '<Job name>' has finished with <State name> state.	Info,Warning,Error
410	Backup copy job started	<Job type> job '<Job name>' has been started.	Info
450	Backup copy task finished	VM <Task name> task has finished with '<State name>' state.	Info,Warning,Error
490	Backup copy job finished	The <Job type> Job '<Job name>' has finished with <State name> state.	Info,Warning,Error
510	File copy job started	<Job type> job '<Job name>' has been started.	Info
590	File copy job finished	The <Job type> Job '<Job name>' has finished with <State name> state.	Info,Warning,Error
512	Vm copy job started	<Job type> job '<Job name>' has been started.	Info
592	Vm copy job finished	The <Job type> Job '<Job name>' has finished with <State name> state.	Info,Warning,Error
10010	Restore point created	VM '<Vm name>' restore point has been created.	Info
10050	Restore point removed	Restore point for VM 'Vm name' has been removed according to the configured retention policy.	Info
10090	Restore point updated	VM '<Vm name>' restore point has been modified.	Info
10014	Tape restore point created	VM '<Task name>' restore point has been offloaded to the tape <barcode>.	Info
20114	Tape updated	Tape <barcode> has been renamed.	Info
21210	Proxy server established connection	Connection to backup proxy '<proxy name>' has been restored.	Info
21214	Proxy server lost connection	Backup server has lost connection to backup proxy '<proxy name>'.	Error
21220	Repository server established connection	Connection to backup repository '<repository name>' has been restored.	Info
21224	Repository server lost connection	Backup server has lost connection to backup repository '<repository name>'.	Error
21230	Wan accelerator established connection	Connection to WAN accelerator '<wan name>' has been restored.	Info
21234	Wan accelerator lost connection	Backup server has lost connection to WAN accelerator '<wan name>'.	Error
24010	License installed	<license type> License key for Veeam Backup & Replication <editioin> has been installed.	Info
24020	License expiring	<license type> License key for Veeam Backup & Replication <edition>  is about to expire in <number of days> of Days.	Warning
24022	License evaluation expiring	<licanse type> Evalution license key for Veeam Backup & Replication <edition>  is about to expire in <nuymber of days> of Days.	Warning
24030	License expired	<license type> License key for Veeam Backup & Replication <edition> has expired.	Error
24040	License support expiring	Support contract for Veeam Backup & Replication is about to expire in <number of days> of Days.	Warning
24050	License support expired	Support contract for Veeam Backup & Replication has expired. Contact Veeam sales representative to renew your support contract.	Error
23410	Second destination job has been assigned	<Job name>' job has been assigned as secondary destination for '<Job count>' jobs	Info	BackupCopy
23420	Second destination job has been removed	<Job name>' job has been removed as secondary destination for '<Job coount>' jobs.	Info	BackupCopy
610	Quick migration job has been finished	QuickMigration job finished with '<0>' state.	Info,Warning,Error

Unable to View Connection String for Veeam Reporter and Veeam Business View Websites in IIS Manager

June 24, 2016, 7:34 am

≫ Next: "JavaScript must be enabled in the web browser to view this page" error while logging to Veeam Reporter Web page

≪ Previous: Veeam Backup & Replication event set for Kaseya

$

0

0

Challenge

When trying to view connection strings for Veeam Reporter and Veeam Business View websites in IIS manager, the following error messages pop up:

Cause

Veeam One encrypts these configuration settings.

Solution

This behavior is the product design.

More Information

If you have any questions, contact Veeam Support.

---

"JavaScript must be enabled in the web browser to view this page" error while logging to Veeam Reporter Web page

July 5, 2016, 6:22 am

≫ Next: Migrating Veeam ONE Server to Another Machine

≪ Previous: Unable to View Connection String for Veeam Reporter and Veeam Business View Websites in IIS Manager

$

0

0

Challenge

The following message displayed on Veeam Reporter web page:

"JavaScript must be enabled in the web browser to view this page's content. If you are using Microsoft Internet Explorer, add this site to the trusted sites".

 

Cause

Security restrictions applied in web-browser prevent from running static content or Veeam Reporter website requires the Static Content feature of IIS be installed in order to function properly.

Solution

At first, try to add Veeam Reporter's web-site into list of Trusted Sites zone via Internet Explorer's configuration options.

Then please check if you have Static Content feature installed for your IIS instance.
This particular error also happens if you do not have Static Content feature installed for IIS7 server where Veeam Reporter server resides.

You should install Static Content feature for IIS to resolve the issue.

Instructions for installing Static Content feature for IIS7:
   1) Open Server Manager console navigate to "Roles -> Web Server (IIS)".
   2) Go to "Role Services" section and press "Add Role Services" link.
   3) On new "Add Role Services" wizard window enable "Static Content" feature in "Web Server -> Common HTTP Features" section.
   4) Go to next step and proceed with installation of the component/feature.
   5) "Static Content" feature now should be available via Server Manager console in Web Server (IIS) Role Services section and should have status "Installed".
   6) Restart IIS7 if required.
   7) Open Veeam Reporter webpage.

Migrating Veeam ONE Server to Another Machine

July 5, 2016, 6:24 am

≫ Next: Moving Veeam ONE database to a different SQL Server

≪ Previous: "JavaScript must be enabled in the web browser to view this page" error while logging to Veeam Reporter Web page

$

0

0

Challenge

Migration of Veeam One server is needed to install (upgrade) the product on a supported OS.

Cause

The previous version of Veeam One was installed on one of the operating systems that is no longer supported by Veeam ONE 7.0

Solution

Before you upgrade, be sure to perform a backup of the corresponding SQL database for Veeam ONE, so that you can easily go back to previous version in case of issues with upgrade.
 

To perform upgrade of Veeam ONE to version 7.0, you must be running version 6.0 or 6.5. Upgrade from earlier versions of Veeam ONE is not supported.
 

If Veeam ONE 6.x is installed on one of the operating systems that is no longer supported by Veeam ONE 7.0, use the upgrade procedure provided below:

 

Deployment with a local SQL Server:
 

1.      Stop all Veeam ONE services. 

2.      If there were any changes made to Veeam registry configuration, export these registry hives manually:

[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam ONE Monitor\Service]  

[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Reporter Enterprise] 

3.      Back up Veeam ONE database using SQL Management Studio. 

4.      Install all system prerequisites on the new Veeam ONE server. This procedure can be performed by running Veeam ONE setup wizard.  

5.      Download and install SQL Server 2008 R2 Express Edition or above on the new Veeam ONE server.

6.      Restore the backed up Veeam ONE database (step 3) to the new server via SQL Management Studio.

7.      Run Veeam ONE installation wizard on a supported OS and point to existing SQL Server instance on the database configuration step. Veeam ONE database will be upgraded automatically. 

8.      Launch Veeam ONE Monitor Client and retype connection account settings to all monitored hosts.

9.      Import Veeam ONE configuration registry keys to the new server. This step is not required, if Veeam ONE installation is running with the default settings.

10.  Restart Veeam ONE services.

 

Deployment with a remote SQL Server:
 

1.      Stop all Veeam ONE services. 

2.      If there were any changes made to Veeam registry configuration, export these registry hives manually:

[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam ONE Monitor\Service]  

[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Reporter Enterprise] 

3.      Back up Veeam ONE database using SQL Management Studio to be able to revert to the previous version of the database in case of issues with upgrade.

4.      Run Veeam ONE installation wizard on a supported OS and point to the remote SQL Server instance on the database configuration step. Veeam ONE database will be upgraded automatically. 

5.      Launch Veeam ONE Monitor Client and retype connection account settings to all monitored hosts.

6.      Import Veeam ONE configuration registry keys to the new server. This step is not required, if Veeam ONE installation is running with the default settings.

7.      Restart Veeam ONE services.

 

Moving Veeam ONE database to a different SQL Server

July 5, 2016, 6:25 am

≫ Next: How to reset VMware Virtual Machine CBT

≪ Previous: Migrating Veeam ONE Server to Another Machine

$

0

0

Challenge

You need to move the Veeam ONE database from the original SQL Server to a different SQL Server and change Veeam ONE Server configuration settings.

Solution

To change SQL Server or database connection settings for Veeam ONE Server, you can use the Veeam ONE Settings utility.

To modify connection settings, follow the instructions below.

Provision a domain account for Veeam ONE Monitor and Veeam ONE Reporter on the new SQL Server. This can be one account or two different accounts. Move the database to the new SQL Server. Grant to the account(s) db_owner permissions on the VeeamOne database.  

Next, modify the accounts that are used by monitoring and reporting components of Veeam ONE.

First, modify connection settings for Veeam ONE Monitor. To accomplish this, perform the following steps:

1. Launch the Veeam ONE Settings utility available under the following path:
   
   C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe

2. In the menu on the left, select General, open the Database tab and make the necessary changes in the SQL Server section.
   

3. Make sure this account has sufficient privileges on the Veeam ONE database on the SQL Server side, as it will be used for performance data collection.

4. Click the Test Connection button to check whether new configuration settings are correct.

5. Save changes.

6. Restart Veeam ONE Monitor Server service.

Then modify connection settings for Veeam ONE Reporter and Business View. To accomplish that, follow the next steps:

1. In the list of services, locate Veeam ONE Reporter Server service and choose to modify its properties. Open the Log On tab and specify the necessary account for the service in the Log on as section.

2. Make sure this account has sufficient privileges on the Veeam ONE database on the SQL Server side, as it will be used for data collection.

3. Launch the Veeam ONE Settings utility available under the following path:
   
   C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe

4. In the menu on the left, select General, open the Web Identity tab and make the necessary changes in the Web identity section.
   

5. Make sure this account has sufficient privileges on the Veeam ONE database on the SQL Server side, as it will be used for overall Web UI operation and reports creation.

6. Save changes.

7. Restart Veeam ONE Reporter Server service.

More Information

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

How to reset VMware Virtual Machine CBT

July 5, 2016, 6:30 am

≫ Next: HCL - StoreOnce 4500 CIFS

≪ Previous: Moving Veeam ONE database to a different SQL Server

$

0

0

Challenge

This document provides details for resetting CBT of a VMware VM.
 
Under certain circumstances CBT cannot be used please see: http://www.veeam.com/kb1163
 
In Veeam Backup & Replication v7 and older:
Cannot use CBT: Soap fault. A specified parameter was not correct. . deviceKeyDetail: '<InvalidArgumentFault xmlns="urn:internalvim25" xsi:type="InvalidArgument"><invalidProperty>deviceKey</invalidProperty></InvalidArgumentFault>', endpoint: ''
 
In Veeam Backup & Replication v8 and newer:
CBT data is invalid, failing over to legacy incremental backup. No action is required, next job run should start using CBT again. If CBT data remains invalid, follow KB1113 to perform CBT reset. Usual cause is power loss.
 
The following entries can be seen in the job log:
[timestamp] Info [AP] (Client) output: Soap fault. Error caused by file /vmfs/volumes/4b953b81-76b37f94-efef-0010185f132e/name/name.vmdkDetail: '', endpoint: ''\n
[timestamp] Info [AP] (Client) output: --tr:Failed to enumerate changed areas of the disk using CTK. Device key: [2000], size: [26843545600]. VM ref: [vm-xx]. Change ID: [*]\n

Solution

Reset CBT as detailed by VMware KB 2139574 

More Information

When resetting CBT on a virtual machine, the next time the Backup or Replication job runs, the entirety of the disks on the Virtual Machine is read. It will not however create a new full (*.VBK) as blocks are compared to create a normal sized incremental.

Typically, a single job session with CBT warnings does not indicate a malfunction. VMware CBT will be automatically reset due to certain operations, such as Storage vMotion. Note that the presence of snapshots will prevent successful reset of CBT. For more information see http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2048201.
 

HCL - StoreOnce 4500 CIFS

July 6, 2016, 6:42 am

≫ Next: Procedure to split Veeam Backup & Replication Server and Veeam Cloud Connect Server

≪ Previous: How to reset VMware Virtual Machine CBT

$

0

0

Challenge

Product Family: HPE StoreOnce w/CIFS

Status: Compatible – Backup Storage (archive)

 
Classification Description: Suitable for full VM backup and full VM restores, but synthetic full backups, granular restores and vPower features may not provide sufficient performance or be supported

Solution

Product Details

• Model number: StoreOnce 4500
• Number of drives: 12
• Drive type: 4 TB
• Firmware version: 3.13.1-1546.2
• Veeam Build Number: 9.0.902
• Additional support: Available on StoreOnce 4500 or a higher tier model with an equal or greater number of drives using the software versions listed.
• General product family overview: From ROBO to the entire enterprise, HPE StoreOnce System with HPE StoreOnce Catalyst is a single and agile backup and recovery solution. Reduce costs and keep pace with rapid data growth, confident that your SLAs are securely met.

Special Considerations

• Best used as a secondary backup target with backup copy and a GFS full backup once a week
• 10 GbE connectivity between the Veeam Gateway Server and DXi is recommended
• Use per-VM backup files

More Information

Company Information
 

• Company name: Hewlett Packard Enterprise

• Company overview: HPE delivers high-quality, high-value products, consulting, and support services in a single package. That’s one of their principal differentiators. They have industry-leading positions in servers, storage, wired and wireless networking, converged systems, software, services and cloud.