Quantcast
Channel: Backup Software for Windows Servers | Backup Software for Virtual Machines
Viewing all 587 articles
Browse latest View live

Boot CD Does Not Boot

$
0
0

Affected Builds

Replay 4.x

AppAssure 5.x

Introduction

This article describes a potential issue with the data files in your AppAssure repository.

Description

After creating a Boot CD, you attempt to open the Universal Recovery Console (URC) to being a rollback or bare metal restore (BMR) but receive the following error.

Status: 0xc00000e9
Info: An unexpected I/O error has occurred.

This error results from the use of improper NIC or disk drivers within the Boot CD.

Also this error is a hardware error pertaining to your system’s BIOS.  Basically it is telling you that the computer is not able to reliably communicate with the hard drive.

Solution

To resolve this issue, complete the following steps.

  1. Ensure you are using the correct NIC.
  2. Ensure that Windows 7 PE 32 bit drivers are used for both your NIC and disk drivers for all similar hardware restores.
  3. If you are performing a dissimilar rollback or BMR, you will need the Windows 7 PE 32 bit drivers as well the RAID controller or disk driver from the hardware that you will inject at the end of the process.

Cannot Complete a Console Task with Multiple Agents Selected

$
0
0

Affected Builds

AppAssure 5.x

Introduction

This article describes a potential issue in completing tasks within the Core Console.

Description

When attempting to complete a task after selecting multiple agents, the following error appears.

Method Not Found: ‘Int32 System.Web.Util.AppSettings.get_MaxJsonDeserializerMembers()’.

This is the result of outdated .NET Framework security settings.

Solution

To resolve this issue, apply the following security update to the .NET Framework on your system.

http://support.microsoft.com/kb/2656351

Error 12029: A Connection with the Server Could Not Be Established

$
0
0

Affected Builds

AppAssure 5.x

Introduction

This article describes a potential issue when installing an AppAssure agent.

Description

When attempting to install or upgrade an agent from the License Portal, you receive the following error.

Error:(12029) A connection with the server could not be established.

This error is the result of one or more environmental issues.

Solution

To resolve this issue, install the AppAssure Agent Full Installer.

Error Message: Nothing to Consume for this Core on the Selected Seed Drive

$
0
0

Affected Builds

AppAssure 5.3.x

Introduction

This article describes a potential issue when consuming a seed drive in AppAssure 5.

Description

When attempting to consume a seed drive to replication on the Target Core, the following error message appears:

“Nothing to consume for this Core on the selected Seed Drive. If you specified a path to a mapped network drive, please, use it’s UNC path with valid credentials instead. Core does not support access to mapped network drives, only to CIFS shares.”

Furthermore, the error appears when attempting to consume a seed from a drive which is not mapped from the network.

Solution

To resolve this issue, complete the following steps.

  1. Check the file path specified for the seed drive location.
  2. Enter the file path to the directory above the AAbackup directory.
    1. For example, if the seed drive is created on G:\Seed, the directory G:\Seed\AAbackup will be created automatically. When consuming the seed, specify the directory G:\Seed. Entering the directory G:\Seed\AAbackup will reproduce the aforementioned error.

Moving Installed Cores to a New Group in the License Portal

$
0
0

Affected Builds

AppAssure 5.x

Introduction

This article details the steps necessary to move previously installed Cores to a new group within the AppAssure 5 License Portal.

Description

During the course of routine maintenance, it may become necessary to move previously installed Cores from the root account to different subgroups within the AppAssure 5 License Portal.

Solution

Complete the following steps:

  1. Replace the key in the Core(s) with the key from the new subgroup.
    1. Select Core Console and open the Configuration tab.
    2. Expand the Licensing tab and click Change Key.
    3. Copy and paste the license key.
  2. Force contact from the Core(s).
    1. Select Core Console and open the Configuration tab.
    2. Expand the Licensing tab and click Contact Now. This will validate the license on the License Portal.

Repository Data Files Missing

$
0
0

Affected Builds

AppAssure 5.x

Introduction

This article describes a potential issue with the data files in your AppAssure repository.

Description

During routine maintenance, you notice that your repository data files are missing, but your metadata files are still visible. Such situation is possible only if the someone deleted those files or the drive on which they were stored was removed\crashed.

Solution

To resolve this issue, complete the following steps.

  1. Stop the Core Service.
  2. Delete the old repository files.
  3. Delete the repository registry branch from the AppRecovery registry branch.
  4. Restart the Core Service.
  5. Create a new repository.
    1. Navigate to the Core and select Add New Repository.
    2. Assign the new repository to all of your agents.
    3. Force a new snapshot.

Skipping Protection of Volumes That are Grouped

$
0
0

Affected Builds

AppAssure 5.3.x

Introduction

This article describes a potential issue when adding an agent to protection.

Description

When adding an agent to protection that is running either Exchange or SQL, AppAssure will group all volumes together if the data and log files are on separate partitions. This is because the software is application aware and will not allow protection to skip on Exchange and SQL volumes.

Solution

To resolve this issue, complete the following steps.

NOTE: Backup  the registry prior to completing these steps.

WARNING: If the volume that contains the database logs is removed/deleted, AppAssure will not be able to restore the database.

  1. Stop the Agent Service.
  2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\Agents\{guid_id_of_agent}\AgentProtectionConfiguration\ProtectionGroups\0\VolumeNames\{volumes} and delete the volume folder that does not need protection.
  3. Restart the service

VM Export Fails with Tevo Library Error Exception

$
0
0

Affected Builds

AppAssure 5.x

Introduction

This article describes a potential error when exporting a virtual machine (VM) in AppAssure 5.

Description

VM exports fail with the following error:

“Tevo Library Error Exception
TevoGetFlagsInOfflineVolume failed with error -2147024893 (0×80070003 – The system cannot find the path specified)”

This issue may occur when multiple, continuous virtual exports run congruently.

Solution

To resolve this issue, complete the following.

  1. Pause protection on all agents.
  2. Verify there are no jobs in progress.
  3. Ensure all mounts are dismounted.
  4. Stop the Core Service.
  5. Stop the AAVDisk and AAVStor drivers.
  6. Extend the AAVDisk and AAVStor driver network timeout to 60000 (dec).
    1. These values are located at HKLM\SYSTEM\CurrentControlSet\Services\AAVdisk\Parameters\ and HKLM\SYSTEM\CurrentControlSet\Services\AAVStor\Parameters\
    2. Restart the AAVDisk and AAVStor drivers.
    3. Restart the Core Service and resume replication.

If the drivers either did not stop or did not restart, reboot the machine.

Stopping the AAVDisk
  1. Run a cmd as an administrator
  2. Type sc stop aavdisk and select Enter to stop the disk.
  3. Type sc start aavdisk and select Enter to start the disk.

VSS Exchange Writer Error in AppAssure 5

$
0
0

Affected Builds

AppAssure 5.3.x

Introduction

This article describes a potential VSS Exchange Writer error in AppAssure 5.

Description

The following errors regarding the VSS Exchange Writer appear.

WebUI Errors

VSS error
“There was a problem with the VSS subsystem on “exchange1.universalsewing.com
• VSS error: DoSnapshotSet failed with error: “Expected provider error. Check event log for details”

Log Errors

ERROR 2013-05-13T19:37:55 [6] – Replay.Agent.Implementation.Transfer.TransferSession (RequestUri=https://exchange1.universalsewing.com:8006/apprecovery/api/agent/transfer/snapshots
ClientAddress=172.16.0.2:9623 Service=Replay.Agent.Management.Transfer.TransferManagement Method=TakeSnapshot)
Failed to take snapshot
Replay.Agent.Contracts.ShadowCopy.ShadowCopyException: DoSnapshotSet failed with error: ‘Expected provider error. Check the event log for details.’

ERROR 2013-05-13T19:37:55 [6] – Replay.ServiceHost.Implementation.Hosting.ServiceHost (RequestUri=https://exchange1.universalsewing.com:8006/apprecovery/api/agent/transfer/snapshots ClientAddress=172.16.0.2:9623)
Service Host Error: Service error while handling request [POST https://exchange1.universalsewing.com:8006/apprecovery/api/agent/transfer/snapshots]: The transfer failed: unexpected error
Request Uri: https://exchange1.universalsewing.com:8006/apprecovery/api/agent/transfer/snapshots
Client Address: 172.16.0.2:9623
Identity: Kerberos:STNT02\administrator
Service: Replay.Agent.Management.Transfer.TransferManagement
Method: TakeSnapshot

Replay.Agent.Contracts.Transfer.TransferFailedException: The transfer failed: unexpected error —> Replay.Agent.Contracts.ShadowCopy.ShadowCopyException: DoSnapshotSet failed with error:’Expected provider error. Check the event log for details.’

Solution

To resolve this issue, apply the following Microsoft hotfix.

Availability of Windows Server 2003 Post-Service Pack 2 COM+ 1.5 Hotfix Rollup Package 12.

Next, complete the following steps.

  1. Check the status of the VSS writer using the command “vssadmin list writers”
    1. See what the output shows. If there are any writers showing a state of “Failed” and the last error states “Retryable error” or “Non-Retryable Error,” reboot the server
  2. Try manually create the shadow copy on the agent machine (vssadmin create shadow /for=”volume”: ). If this is not possible, re-register the vss writers using the following batch file on this particular server.
    1. net stop “System Event Notification Service”
    2. net stop “Background Intelligent Transfer Service”
    3. net stop “COM+ Event System”
    4. net stop “Microsoft Software Shadow Copy Provider”
    5. net stop “Volume Shadow Copy”
    6. cd /d %windir%\system32
    7. net stop vss
    8. net stop swprv
    9. regsvr32 /s ATL.DLL
    10. regsvr32 /s comsvcs.DLL
    11. regsvr32 /s credui.DLL
    12. regsvr32 /s CRYPTNET.DLL
    13. regsvr32 /s CRYPTUI.DLL
    14. regsvr32 /s dhcpqec.DLL
    15. regsvr32 /s dssenh.DLL
    16. regsvr32 /s eapqec.DLL
    17. regsvr32 /s esscli.DLL
    18. regsvr32 /s FastProx.DLL
    19. regsvr32 /s FirewallAPI.DLL
    20. regsvr32 /s kmsvc.DLL
    21. regsvr32 /s lsmproxy.DLL
    22. regsvr32 /s MSCTF.DLL
    23. regsvr32 /s msi.DLL
    24. regsvr32 /s msxml3.DLL
    25. regsvr32 /s ncprov.DLL
    26. regsvr32 /s ole32.DLL
    27. regsvr32 /s OLEACC.DLL
    28. regsvr32 /s OLEAUT32.DLL
    29. regsvr32 /s PROPSYS.DLL
    30. regsvr32 /s QAgent.DLL
    31. regsvr32 /s qagentrt.DLL
    32. regsvr32 /s QUtil.DLL
    33. regsvr32 /s raschap.DLL
    34. regsvr32 /s RASQEC.DLL
    35. regsvr32 /s rastls.DLL
    36. regsvr32 /s repdrvfs.DLL
    37. regsvr32 /s RPCRT4.DLL
    38. regsvr32 /s rsaenh.DLL
    39. regsvr32 /s SHELL32.DLL
    40. regsvr32 /s shsvcs.DLL
    41. regsvr32 /s /i swprv.DLL
    42. regsvr32 /s tschannel.DLL
    43. regsvr32 /s USERENV.DLL
    44. regsvr32 /s vss_ps.DLL
    45. regsvr32 /s wbemcons.DLL
    46. regsvr32 /s wbemcore.DLL
    47. regsvr32 /s wbemess.DLL
    48. regsvr32 /s wbemsvc.DLL
    49. regsvr32 /s WINHTTP.DLL
    50. regsvr32 /s WINTRUST.DLL
    51. regsvr32 /s wmiprvsd.DLL
    52. regsvr32 /s wmisvc.DLL
    53. regsvr32 /s wmiutils.DLL
    54. regsvr32 /s wuaueng.DLL
    55. sfc /SCANFILE=%windir%\system32\catsrv.DLL
    56. sfc /SCANFILE=%windir%\system32\catsrvut.DLL
    57. sfc /SCANFILE=%windir%\system32\CLBCatQ.DLL
    58. net start “COM+ Event System”
    59. net start “System Event Notification Service”
    60. net start “Background Intelligent Transfer Service”
    61. net start “Microsoft Software Shadow Copy Provider”
    62. net start “Volume Shadow Copy”
How to use batch file:
  1. Create a notepad file
  2. Copy the aforemention command to this file and save as batch file
  3. Run as an administrator

VSS Failures Error 0×80042304

$
0
0

Affected Builds

AppAssure 5.x

Introduction

This article describes a potential VSS issue in AppAssure 5.

Description

The following error appears in your logs:

“Error 0×80042304: The volume shadow copy provider is not registered in the system.”

This error results from improperly registering the volume shadow copy provider in the system.

Solution

To resolve this issue, register the following DLLs from a command line prompt.

  • cd %systemroot%\system32
  • net stop vss
  • net stop swprv
  • regsvr32 ole32.dll
  • regsvr32 vss_ps.dll
  • Vssvc /Register
  • regsvr32 /i swprv.dll
  • regsvr32 /i eventcls.dll
  • regsvr32 es.dll
  • regsvr32 stdprov.dll
  • regsvr32 vssui.dll
  • regsvr32 msxml.dll
  • regsvr32 msxml3.dll
  • regsvr32 msxml4.dll

Once the DLLs are registered, reboot the server. If any DLL cannot be registered, reboot the server and register the DLL again.

Using PowerShell to Check Active Jobs in Real-Time

$
0
0

Affected Builds

AppAssure 5.x

Introduction

This article details the steps necessary to check active jobs in real-time using PowerShell.

Description

The AppAssure PowerShell module provides customers with the ability to check the progress of all active, running jobs in real-time without opening the Core Console.

Warning: All scripts provided in this article are meant to be used as examples and are not supported by AppAssure. For more information on Dell | AppAssure scripting support, click here.

Solution

The following script will check all active jobs in real-time. This script should be run from an elevated PowerShell console on either the Source or Target Core. Prior to running the script, please note the following:

  • The script runs indefinitely, “catching” the active jobs on the selected core and updating them in semi real-time (i.e. every second).
  • When possible, progress is tracked both in MB and percentages. Due to the limitations of the AppAssure PowerShell module, this is not always possible. For instance, in AppAssure 5.3, the replication progress can be tracked from the Target Core but not on the Source Core.
  • The script can be exited gracefully by pressing the Q key or by hard stop using Ctrl-c.

#You may need the line below; try without it first
#[System.Reflection.Assembly]::LoadWithPartialName(“System.Windows.Forms”)

Write-host
Write-host “Real Time AppAssure Active Jobs Monitor”
Write-host “—————————————”
Write-host Hit “Q” to exit.
$Qkey = 81 #value of Quit key

#get the name of the core to monitor. Local machine is default
$corename = Read-Host “Enter the name of the Core to monitor [default $($env:computername)]”
if ($corename -eq “”) {$corename = $env:computername}
Write-host

#check if the appassure powershell module is installed
$module = “appassurepowershellmodule”
if (-not(Get-module -name $module)) {import-module appassurepowershellmodule}
Write-host “$($module) is installed”

#starting Position
$StartPos = [console]::CursorTop

#make a filler row; there are better ways to achive this, though
for ($j=1; $j -lt [console]::WindowWidth; $j++){$m+= ” “}

#set the max y position
$maxpos = $StartPos

For (;;) #dummy loop

{
#Set starting Point
[Console]::SetCursorPosition(0,$StartPos)

#Get Active Jobs
$jobs = get-activejobs -all -core $corename

#Prepare the table with the active jobs

$jobs | Format-Table -Wrap -property @{n=”Summary”; e={$_.Summary};width=20}, Status,
@{n=”Total Work”;e={“{0:N2}” -f ($_.TotalWork/1MB)+”MB”}},
@{n=”Progress”;e={“{0:N2}” -f ($_.Progress/1MB)+”MB”}},
@{n=”PercentComplete”;e={“{0:N2}” -f ($_.Progress/$_.TotalWork*100)+”%”}},
StartTime | out-default

#Get the last position of the cursor
$Endpos = [console]::CursorTop

#Wait for a second
start-sleep -m 1000

#get the screen area to be cleaned
if ($maxpos -Lt $Endpos){$maxpos = $Endpos}

#set cursor location to begin cleaning
[Console]::SetCursorPosition(0,$Endpos-2)

#clean area
for ($i=$endPos; $i -le $maxpos; $i++) {$m}

#exit the loop
if ($host.ui.RawUi.KeyAvailable)
{
$key = $host.ui.RawUI.ReadKey(“NoEcho,IncludeKeyUp”)
if ($key.VirtualKeyCode -eq $Qkey)
{
Write-host
Write-host
Write-Host “Exiting…”
Write-host
break

}
}
}

VSS SqlServerWriter Errors

$
0
0

Affected Builds

AppAssure 5.3.x

Introduction

This article describes a potential error with the VSS writer SqlServerWriter.

Description

There may be instances in which the system reports a VSS SqlServerWriter error. These instances are listed below.

  1. SqlServerWriter VSS fails during DoSnapshotSet phase
  2. When running VSSadmin list writers, the SqlServerWriter reports no information

Solution

To following solutions may resolve these issues.

Option 1

Apply the following hotfix to alleviate any conflict between MSDE and the SQL writers: http://support.microsoft.com/kb/913100.

If this hotfix does not work, complete the following steps:

  1. Open the Core Console.
  2. Open the agent and select the Configuration tab.
  3. Select Transfer Settings.
  4. Press Change and select the SQLServer Writer check box.
  5. Click Save.
Option 2

Ensure that the SQL Server instances have access to the Windows account, either explicitly or through group membership of BUILTIN\Administrators.

Once that granted, complete the following steps.

  1. Bounce the SQL Server Writer Service.
  2. Run vssadmin list writers to ensure the SQL Server Writer is listed.
  3. Refresh the agent metadata in the Core Console.
  4. Force a snapshot of the agent.

Linux AAMount Exception Error

$
0
0

Affected Builds

AppAssure 5.x

Introduction

This article describes a potential exception error on a Linux machine.

Description

The following error appears when performing a rollback or mounting a recovery point using the AAMount utility:

“Exception of type: Castle.MicroKernel.ComponentActivator.ComponentActivatorException”

This is the result of restrictions within the UAC that cause the connection to drop.

Solution

The following work around(s) may resolve the issue.

  • Ensure the user is “root” when using AAMount.
  • Ensure a 32 character UUID is used for the recovery point. For example:
    • r 00000000-0000-0000-0000-000000000000:1 /dev/sda1
  • Use the local admin on the Core, as this will bypass all UAC restrictions.
    • NOTE: The local admin should be used here, not the domain admin.

Linux Agent Installation Error: Unexpected EOF in Archive

$
0
0

Affected Builds

AppAssure 5.x

Introduction

This article describes a potential error when installing a Linux agent.

Description

The following error appears when installing an agent on a Linux machine:

Error:
gzip: stdin: invalid compressed data–format violated
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now

This is the result of a disruption of the line feed characters, as Windows and Linux use different codes. Windows uses CR/LF at the end of each line, while Linux uses LF.

Solution

The following work around(s) may resolve the issue.

  • From a command line on the Linux server, run perl -i -pe’s/\r$//;’ appassure-installer_ubuntu_amd64_5.3.3.63056.sh
  • Download dos2unix and run it as dos2unix appassure-installer_ubuntu_amd64_5.3.3.63056.sh
  • Use wget to grab the file directly to the agent
    • wget https://s3.amazonaws.com/appassure5releases/appassure-installer_ubuntu_amd64_5.3.3.63056.sh
  • Ftp the files from a Windows machine to the Linux agent using binary mode.
  • Use the command-line ftp change to binary mode with the following commands:
    • ftp example-windows-machine.com
    • bin
    • get appassure-installer_ubuntu_amd64_5.3.3.63056.sh bye
    • NOTE: If using a GUI client, ensure the client is set to Binary Mode.

Configuring Virtual Standby for Servers with Disk Larger than 2 TB

$
0
0

Affected Builds

AppAssure 5.x

Introduction

This article offers special considerations when configuring virtual standby for servers with disks larger than 2 TB.

Description

Virtual standby does not support exports of disks larger than 2 TB. Presently, VMware does not support VMDK files larger than 2048 GB minus 512 bytes.

 

NOTE: For the purposes of this article, 2 TB = 2048 GB.

Solution

VMware

Though VMFS5 supports files larger than 2 TB, the current maximum VMDK file size is 2048GB minus 512 Bytes. Due to this limitation, there is no workaround for 2+ TB VMDK files for virtual standby exports to VMware.

Hyper-V

Though typically present on Windows Server 2008 R2 and Windows 7 machines, it is possible that the System Reserve Partition (SRP) may not exist in some configurations.

When performing a virtual standby export (ad-hoc or continuous) for a server with physical disks in excess of 2 TB, it is not possible to complete the export of the disks which exceed 2 TB in size; however, in certain scenarios it is possible to export just the C: and SRP (if applicable) partitions and then perform a rollback or live rollback of the remaining volumes. The following criteria must be met to accomplish this procedure:

  • The physical disk on which the C: and SRP (if applicable) reside must be smaller than 2 TB.
  • The Hyper-V server receiving the export must be support virtual disks larger than 2 TB.  Currently, only Windows Server 2012 and Windows 8 (using VHDX) have this capability.

To execute this workaround, perform the following.

  1. Verify that the C: and SRP (if applicable) reside on a disk that is less the 2 TB. This can be done using MSINFO32 or disk manager for the original agent server, if still available.
    1. If using MSINFO32, navigate to System Summary\Storage\Disks. Typically, the system disk will be the partition labeled “Disk #0, Partition #0″. If this disk is larger than 2 TB the export will not complete.
    2. If using Disk Manager on the original agent server, simply observe the size of Disk0.
  2. Configure an ad-hoc or continuous virtual standby export, selecting only the C: and SRP (if applicable) volumes.
  3. Once the initial export is complete, manually create one or more virtual disks using the VHDX format. Be sure to size them appropriately.
  4. Attache any VHDX virtual disk to the virtual machine configuration.
  5. The new virtual machine can now be booted. Once booted, the 2+ TB disks should be visible in Disk Manager.
    1. Please note that some applications may not function properly yet, as not all volumes will be present in the operating system (OS).
  6. Perform a rollback or live rollback for the remaining volumes using typical procedures as if it were a physical server.

For more information, please refer to the following links:

 


Virtual Exports to VMware Fail with “File /.vmx is Larger Than the Maximum Size Supported by Datastore” Error

$
0
0
Affected Builds

AppAssure 5.x

Introduction

This article describes a potential issue with virtual exports to VMware.

Description

The following error appears when performing a virtual export to VMware, even though the volume or combined size of the volumes being exported is not larger than 2 TB:

“Creating virtual machine snapshot on <AgentName>- 25.8.2013 21:05:39 failed with Replay.Common.Implementation.Virtualization.VSphereApi.EsxRemoteException: Task ‘CreateSnapshot_Task failed: File <AgentName>/<AgentName>.vmx is larger than the maximum size supported by datastore ‘[VMFS]”

Solution

Additional limitations exist with VMware environments that dictate the size of virtual standby exports. For example, if the datastore to which the VMware export is being performed is configured with a block size of 4MB, the maximum file size is 1024GB. Also, a 1024GB volume has a maximum VMware snapshot file size of 8GB. The maximum exportable size is equal to the VMDK size and snapshot file combined. In cases where the snapshot file becomes large, the maximum size of an exported agent volume set may be smaller. VMware recommends allowing for the following “worst case scenarios.” The snapshot file size is referred to as “overhead.”

Maximum file size based on block size (VMFS5)
Block Size Maximum File Size
1 MB 256 GB – 512 Bytes
2 MB 512 GB – 512 Bytes
4 MB 1 TB – 512 Bytes
8 MB 2 TB – 512 Bytes

 

Maximum VMDK size when maximum overhead is reached
Maximum VMDK Size Maximum Overhead Maximum Size Less Overhead
256 GB – 512 Bytes ~ 2 GB 254 GB
512 GB – 512 Bytes ~ 4 GB 508 GB
1 TB – 512 Bytes ~ 8 GB 1016 GB
2 TB – 512 Bytes ~ 16 GB 2032 GB

 

For more information, please refer to the following articles:

 

Changing the Metadata Access Timeout in AppAssure 5

$
0
0

Affected Builds

AppAssure 5.x

Introduction

This article details the steps necessary to change the metadata access timeout on an agent in AppAssure 5.

Description

The metadata access timeout settings may need to be changed during routine network maintenance. This may become necessary when the metadata from the agent takes too long to transfer, causing the job to fail with a timeout error.

Solution

Complete the following steps.

  1. Stop the Agent Service.
  2. Open the registry and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Agent\AgentTransferSettings.
  3. Set the MetadataAccessTimeout setting to 10 minutes.
  4. Restart the Agent Service.

Core is Unreachable When Attempting a BMR or Export

$
0
0

Affected Builds

AppAssure 5.x

Introduction

This article describes a potential error with the Core during a BMR or export.

Description

Bare Metal Restore (BMR) or virtual export fails within one minute. An error message appears stating “The core is unreachable via <IP>.”

Solution

To resolve this issue, complete the following steps.

  1. In the Core UI, select Core.
  2. Select Configuration and click Settings.
  3. Select Replay Engine Configuration and click Change.
  4. Confirm that the correct Core IP is listed as the IP address.
    1. If not, change the IP address to the correct IP.
    2. If it is properly configured, change the IP to the local host IP of 127.0.0.1.
  5. Disable the IPv6
  6. Retry the BMR or export.

Installation of a Prerequisite Failed with Error Code 110

$
0
0

Affected Builds

AppAssure 5.x

Introduction

This article describes a potential error when installing AppAssure 5.

Description

CRT 2010 or other prerequisites may fail if either the installation temp folder or download installer are located in an encrypted location.

Solution

To resolve this issue, complete the following steps.

  1. Open a command prompt and type set | find “TEMP”
  2. Note the path that displays.
  3. In Explorer, navigate to the path given in the step above and open the Properties folder.
  4. Click Advanced.
  5. Deselect the box marked Encrypt Contents to Secure Data.
    1. NOTE: If the box is checkered gray, repeat steps 3-5 for each Parent Folder until encryption is removed.
  6. Re-run the installer.
  7. If the previous steps do not resolve this issue:
    1. Move the installer to a confirmed un-encrypted location.
    2. Re-run the installer.

Error: Installation of Prerequisite Hotfix KB940349 (x86) ENU Failed

$
0
0

Affected Builds

AppAssure 5.x

Introduction

This article describes a potential error when installing an agent in AppAssure 5.

Description

Installation of an agent fails due to a missing prerequisite on Windows Server 2003. The following error appears:

Error Message: “Installation of prerequisite: Hotfix KB940349 (x86) ENU failed with error code: 1603.”

Solution

To resolve this issue, install the Microsoft Hotfix located in KB article 940349. Choose the download link that matches the agent chipset (32 or 64 bit).

Viewing all 587 articles
Browse latest View live