Affected Builds

AppAssure 5.3.6

Description

Recovery Point Mount fails with Semaphore Timeout error.

Tevo Library Error Exception

TevoMountReplay failed with error -2147024775 (0×80070079 – The semaphore timeout period has expired)

Resolution

1. Suspend all transfers.
2. Ensure all mounts are dismounted.
3. On the Core Configuration tab, set the Replay Engine timeout settings to 30 minutes.
4. Stop the Core Service.
5. Stop the AAVDisk driver (command: sc stop aavdisk).
6. Extend the AAVDisk driver NetworkTimeout to 600000 (decimal, equivalent to 1 minute). The values are located at HKLM\SYSTEM\CurrentControlSet\Services\AAVdisk\Parameters\.
7. Create the AsyncNetworkTimeout REG_DWORD (HKLM\System\CurrentControlSet\Services\AAVdisk\Parameters\AsyncNetworkTimeout) value and set it to 600000.
8. Start the AAVDisk driver (sc start aavdisk).
9. Increase HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\ExchangeServiceConfiguration\MountabilityCheckingProcessTimeoutMinutes to 1440 minutes.
10. If the drivers start, restart the Core Service and resume transfers.
11. If the drivers do not start, reboot the Core server.
12. After rebooting, restart the Core Service and resume transfers.

Affected Builds

Replay4

AppAssure 5.x

Description:

The above error may occur when accessing UNC paths by NETBIOS name in any context from Replay or AppAssure 5. This is a Microsoft designed behavior and not directly related to Replay or AppAssure 5.

Resolution:

Per this Microsoft KB: http://support.microsoft.com/kb/938120

Use one of the following methods to workaround this behavior:

Method 1

• Use the IP address of the remote server when you try to connect to the network share.

Method 2

• Create a different Domain Name System (DNS) alias for the remote server, and then use this alias to connect to the network share.
• After you use one of these methods, you can use different user credentials to connect to the network share. In this situation, the computer behaves as if it is connecting to a different server.

Affected Builds
AppAssure 5 Core Build 5.x

Replay 4 Core Build 4.x

Description:

Customer has restored a Domain Controller however customer has disabled the NIC. There is a Hidden setting in Active directory which the NIC if removed will cause issues on Domain Controllers.

Resolution:
Enable the NIC Then start the VM guest .

Affected Build

AppAssure 5.x

Problem Description
Core memory usage is very high for the processes running, and/or physical memory usage on the system is 90%+
This does not apply to an under-powered core

Resolution: 

1. In device manager, verify that there are not multiple instances of “Replay VStor Adapter”
2. If multiple instances are present, all but one will like show an error such as “An I/O adapter hardware error has occurred”
3. Delete all but the properly functioning adapter.
4. Run a repair on the core installation
5. Reboot the core
6. Verify only one adapter is present

Affected Build

AppAssure 5.x

Problem Description

ERROR 2013-10-22T15:30:44 [507] – Replay.Core.Implementation.Transfer.TransferJob ()
Job ‘Transfer of volumes [atcns2.automationtool.com” failed
System.AggregateException: One or more errors occurred. —> Replay.Core.Contracts.Transfer.CoreTransferFailedException: The transfer of one or more volume images from a protected machine to the Core failed —> System.AggregateException: One or more errors occurred. —> Replay.Core.Contracts.Transfer.CoreVolumeTransferFailedException: Transfer failed for volume ‘C:\’ —> System.Net.Sockets.SocketException: An established connection was aborted by the software in your host machine

Resolution

1. Complete standard ts’ing to ensure that the issue is not on the agent creating the shadow copy
2. Verify connectivity from Core to Agent and Agent to Core
3. Ensure that NIC drivers are up-to-date
4. Make the following change: Go to the Core GUI -> Agent-> Configuration -> Transfer Settings tab and adjust the transfer settings for the failing agent:

• Maximum concurrent streams. 2
• Maximum concurrent writes. 2
• Maximum retries. 3
• Maximum segment size. 1048576
• Maximum transfer queue depth. 32
• Transfer timeout. 0:30:00
• Snapshot timeout. 0:20:00
• Network read timeout. 0:15:00
• Network write timeout. 0:15:00

Products:

Replay 4

AppAssure 5.x

Problem Description

Core server has crashed, is not accessible, and the Replay/AppAssure environment needs to be recovered.

Resolution

Connect the physical hard disk of the down server to the new Core via iSCSI, SATA, or perc connection, similar to a DAS or removable storage device.

On the new Core server, open ‘Regedit’, and click File – Load Hive. Browse to the drive that was connected via Windows Explorer and open Windows\System32\Config and select the ‘Software’ File. Do not load the Software.sav.

Specify a location to load  the hive, such as ‘Test’, then export the desired “Software – AppAssure (Replay 4)” or “Software – Apprecovery (AppAssure 5)”.

Then Export that key to the desktop and open it in notepad. Change the ‘new’ registry paths (Test\Software\etc…) to the proper paths (HKLM – Software – etc. All paths can be changed at once via Edit – Replace in Notepad.

Once that is finished, save the file and import into the registry.
Unload the registry hive and restart the AppAssure Core or Replay Core service.

Affected Builds

AppAssure 5.3.4.xxx

Problem Description

Cluster disks are displayed as the node’s local volumes when ‘Maintenance’ mode is turned on for cluster disks.  This creates a WMI problem – when the ‘Maintenance’ mode is enabled on the cluster disk, WMI may return empty partition GUID. Without GUID info, the volume cannot be handled correctly. The issue persists for all cluster types both for cluster disks and cluster shared volumes.

Resolution

To resolve this issue, disable Maintenance mode for the protected cluster.

Product:

Replay 4

AppAssure 5.x

Description:

This article details the process of importing a virtual machine into Hyper-V

Resolution:

Once the export is complete, you can view the Virtual Machine files in the storage directory specified for the Hyper-V Host.

Importing a Virtual Machine

Importing a virtual machine can also be done through Hyper-V Manager, to do so click on the Import Virtual Machine link on the right-hand side.

Now navigate to the exported virtual machine and be sure to select folder that your virtual machine was exported into. You can leave the rest of the settings at their defaults and click the import button.

It may take a while for your machine to import depending on its size.  Once it completes, you can then power on the virtual machine.

Affected Builds

AppAssure 5.x

Problem Description

The core runs on an operating system (OS) that does not support Single Instance Storage (SIS).

Attempts to access files in a mounted recovery point on the agent running on Windows Storage Server 2008 with enabled SIS (Single Instance Storage) fails with the following error.

“Error 0×80070780: The file cannot be accessed by the system.”

Resolution

To be able to  access mounted files on different Storage Server 2008 Windows or access future created files, disable SIS on the agent. For info on how disable SIS role, please refer to the following article:

http://technet.microsoft.com/en-us/library/dd573313(v=ws.10).aspx

To access already consolidated files, install the Local Mount Utility (LMU) on the same agent or on the similar Windows Storage Server 2008.

For more information about AppAssure Single Instance Storage support, please refer to the following article:

http://www.appassure.com/support/KB/single-instance-storage-volume-support/

Affected Builds

AppAssure 5.x

Description

Dell AppAssure does not currently protect machines with identical Volume IDs on a single Core server, as the software reads both volumes as identical identities.

This can occur when cloning virtual machines (VMs). Rather than reading the two volumes as separate components, AppAssure will attempt to place the clone VM’s backups with the original VM’s backups.

Solution

An alternative to the Solution presented in this KB:
http://www.appassure.com/support/KB/cloning-virtual-machines/

These steps must be performed on ALL cloned virtual machine agents that you have protected:

1. Remove the agent from protection along with all recovery points
2. Delete the agent’s registry -> perform agent repair so that it creates a new agent ID
3. Run assuremc disable on all volumes.
4. Delete aadata and aafailover on agent volumes.
5. Protect the agent with a new display name.
6. New base images and incremental snapshots will then be successful and mountable.
7. Confirm that the driver IDs are different for all volumes

Should you require, the following steps are the same steps above but in more detail:

Step 1. Remove the agent machine from protection along with all recovery points

Step 2. Delete the agent’s registry and restart the agent service so that it creates a new agent ID:

1) Stop the AppAssure agent service
2) Backup the agent registry folder: HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Agent\
3) Delete the entire agent registry folder: HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Agent\
4) Restart the AppAssure agent service

Steps 3 & 4. Run assuremc disable on all volumes & Delete the aadata and aafailover files from the agent’s volumes.

**Stop the AppAssure agent service before starting.
1. Download the link below to the agent server:
http://aainfo-logs.s3.amazonaws.com/AA-1111/ReplaySupportBundle-NCLIFT-2013-03-13_09-21.zip
2. Extract the zip and browse in.
3. Click on custom files.
4. Extract the assuremc.zip file here. There is a 64-bit and 32-bit version.
5. If the agent machine has a system reserved partition, then you may continue. Otherwise, continue to #7. From diskmgmt.msc right click on the system reserved partition and choose “change drive letter and paths”.
6. Click ‘Add’ then choose a drive letter and click ok.
7. From windows explorer browse to the drive letter, then browse to ‘System volume information’ folder.
- This is a hidden and protected operating system folder so you may have to change the view options for that folder.
- You also may not have access to this folder by default, so you will need to add the user account you are logged in with to the permissions.
8. In this folder see the AAData.md & AAFailover.md files. This is the change log.
9. Open an admin command prompt.
10. cd to the assuremc directory from step 4.
11. Enter the following command:
assuremc disable ‘drive letter you chose in step 6′.
ex. assuremc disable f:
12. Once this completes, you will be able to delete the change logs (aadata and aafailover).
- Right-click on the AAData.md & AAFailover.md files and go to Properties -> Security. Click Edit and Add, then add the account you’re logged in as to the list. Grant yourself Full Control. Then click on Advanced -> Owner and make yourself the owner of the file. Save settings, and open an elevated cmd prompt.
- I have found sometimes when you delete from windows explorer it may not delete it, but if you do it from an elevated command prompt, it will.

Type the following:
> del AAData.md
> del AAFailover.md

13. Once you delete the change logs, remove the drive letter (if one was assigned to the SRP volume) from diskmgmt.msc.
14. Repeat steps #7-13 for each volume
15. Start the agent service.

Step 5. Protect the agent with a new display name.

Step 6. New base images and incremental snapshots will then be successful and mountable.

Step 7. Confirm that the driver IDs are different for all volumes. See the attached screenshot for the registry path and the drive ID keys.

Follow this KB to confirm if the LastDriverId registry key are different for all volumes: http://www.appassure.com/support/KB/how-to-tell-if-an-agent-machine-is-a-cloned-virtual-machine/

Affected Builds

AppAssure 5.x

Description

Dell AppAssure does not currently protect machines with identical Volume IDs on a single Core server, as the software reads both volumes as identical identities.

This can occur when cloning virtual machines (VMs). Rather than reading the two volumes as separate components, AppAssure will attempt to place the clone VM’s backups with the original VM’s backups.

Solution

How to tell if an Agent Machine is a Cloned Virtual Machine

On the Core Server:

**Open regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery. Right click and choose export and save the Appassure registry.

• Open regedit.
• Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\Agents\<the unique identifier for the agent machine>\AgentProtectionConfiguration\ProtectionGroups\0\VolumeNames\0\LastDriverId
• Locate the LastDriverId registry key (click on the screen capture below to zoom in)
  
• Compare this LastDriverId with all other volumes protected for the agent (this is seen as “0″, “1″, “2″, etc depending on the number of volumes protected)
• Compare this LastDriverId with every other agents’ volumes

If the values for the LastDriverId registry key are identical with any volume, then this indicates the virtual machine had been cloned from another virtual machine. This is typically done by creating a virtual machine from a pre-existing virtual machine template.

You may reference these two KB articles to resolve this issue if the virtual machine is already a protected agent.
http://www.appassure.com/support/KB/cloning-virtual-machines/
http://www.appassure.com/support/KB/another-solution-to-cloned-virtual-machines/

Affected Builds

AppAssure 5.x

Description

Agent goes offline with the following error:

Error
The object invoked has disconnected from its clients. (Exception from HRESULT: 0×80010108 (RPC_E_DISCONNECTED))

Stack trace:

System.Runtime.InteropServices.COMException (0×80010108): The object invoked has disconnected from its clients. (Exception from HRESULT: 0×80010108 (RPC_E_DISCONNECTED))
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementObject.Initialize(Boolean getObject)
at System.Management.ManagementBaseObject.get_wbemObject()
at System.Management.ManagementBaseObject.get_ClassName()
at System.Management.ManagementClass.GetInstances(EnumerationOptions options)
at Replay.Common.Implementation.WmiApi.Environment.WmiEnvironment.IsRoleInstalled(UInt32 roleId)
at Replay.Common.Implementation.Metadata.CommonMetadataService.GetDeduplicationSupport(ICommonSummaryMetadata metaData)
at Replay.Common.Implementation.Metadata.CommonMetadataService.GetCommonSummaryMeta

Solution

To resolve this issue, complete the following steps

On the Agent machine,

• In the System Even Logs, verify that a Schannel Event ID 36885 error occurred on the affected agent machine.
• Apply the fix outlined in the Microsoft KB article titled SSL/TLS communication problems to delete the certificate registry key which should resolve this issue:  http://support.microsoft.com/kb/2801679/en-us
• Restart the Agent Service.

On the Core server,

• Go to the affected agent, click on the Actions drop-down menu on the Home tab
• Click Refresh Metadata
• The agent will be repaired and re-appear online

Product

AppAssure 5.3.x

Problem Description

When troubleshooting installation/pairing issues it may be necessary to import a certificate from the core to the Trusted Root Certification Authorities of the machine . If RDP access is not available, the operation can be executed easily via PowerShell.

Please note that Powershell 4.0 is installed by default on Windows 2012 R2 machines.

WARNING: Dell does not support PowerShell scripting in AppAssure. Click here for more details.

Resolution

For the purposes of this article, it is assumed that the certificate is called cert.pfx with the password abc_123 and is located in c:\ on the local machine and that the remote machine is named machine-1. To import the certificate, please do the following:

1. Open a remote session to the machine to be troubleshot

Enter-PsSession -computer machine-1

You will get a prompt showing that you are logged on the remote machine.
(Please note that PowerShell remoting is enabled by default on Windows 2012 and later)

2. Stop the Agent service

Stop-Service AppAssureAgent

3. Enter the password as a secure string

$pass = read-host -assecurestring

(you will be prompted to enter it with the following message
WARNING: A script or application on the remote computer machine-1 is asking to read a line securely.
sensitive information, such as your credentials, only if you trust the remote computer and the application
that is requesting it.)

4. Import the .pfx certificate

import-pfxcertificate -filepath c:\cert.pfx -certstorelocation cert:\localmachine\root -password $pass

You will get a message similar to the one below:

Directory: Microsoft.PowerShell.Security\Certificate::LocalMachine\root
Thumbprint Subject
———- ——-
64AB6D87A6227E650B13299C3AB1B80B0B9452CE O=Root, CN=machine-1, T=AppRecoveryCoreClientCertificate

5. Start the Agent Service
start-service AppAssureAgent

Product

AppAssure 5.3.x

Problem Description

When troubleshooting an AppAssure agent, Support may need to collect in depth information regarding the hard drives present on that computer.

Resolution

The following script will gather the aforementioned detailed information on the hard drives. The path to the text file is held in the $file variable. Please change it accordingly.

#Physical Disks Properties

#Please change the path below to the desired value
$file = “c:\disks.txt”

$strComputer = $env:computername
$x = Get-WmiObject win32_volume -ComputerName $strComputer | select name,label,deviceid | sort-object name
“Private Properties of physical drives on $($strcomputer)`r`nSummary:” > $file

$x >> $file
$colItems = get-wmiobject -class Win32_DiskDrive -namespace root\CIMV2 -computername $strComputer | sort-object deviceid

foreach ( $objItem in $colItems) {

$objitem >> $file
“_______________________________________________
`r`n Properties:`r`n
`r`n Availability: $($objItem.Availability)
`r`n Bytes Per Sector: $($objItem.BytesPerSector)
`r`n Capabilities: $($objItem.Capabilities)
`r`n Capability Descriptions: $($objItem.CapabilityDescriptions)
`r`n Caption: $($objItem.Caption)
`r`n Compression Method: $($objItem.CompressionMethod)
`r`n Configuration Manager Error Code: $($objItem.ConfigManagerErrorCode)
`r`n Configuration Manager User Configuration: $($objItem.ConfigManagerUserConfig)
`r`n Creation Class Name: $($objItem.CreationClassName)
`r`n Default Block Size: $($objItem.DefaultBlockSize)
`r`n Description: $($objItem.Description)
`r`n Device ID: $($objItem.DeviceID)
`r`n Error Cleared: $($objItem.ErrorCleared)
`r`n Error Description: $($objItem.ErrorDescription)
`r`n Error Methodology: $($objItem.ErrorMethodology)
`r`n Index: $($objItem.Index)
`r`n Installation Date: $($objItem.InstallDate)
`r`n Interface Type: $($objItem.InterfaceType)
`r`n Last Error Code: $($objItem.LastErrorCode)
`r`n Manufacturer: $($objItem.Manufacturer)
`r`n Maximum Block Size: $($objItem.MaxBlockSize)
`r`n Maximum Media Size: $($objItem.MaxMediaSize)
`r`n Media Loaded: $($objItem.MediaLoaded)
`r`n Media Type: $($objItem.MediaType)
`r`n Minimum Block Size: $($objItem.MinBlockSize)
`r`n Model: $($objItem.Model)
`r`n Name: $($objItem.Name)
`r`n Needs Cleaning: $($objItem.NeedsCleaning)
`r`n Number Of Media Supported: $($objItem.NumberOfMediaSupported)
`r`n Partitions: $($objItem.Partitions)
`r`n PNP Device ID: $($objItem.PNPDeviceID)
`r`n Power Management Capabilities: $($objItem.PowerManagementCapabilities)
`r`n Power Management Supported: $($objItem.PowerManagementSupported)
`r`n SCSI Bus: $($objItem.SCSIBus)
`r`n SCSI Logical Unit: $($objItem.SCSILogicalUnit)
`r`n SCSI Port: $($objItem.SCSIPort)
`r`n SCSI Target ID: $($objItem.SCSITargetId)
`r`n Sectors Per Track: $($objItem.SectorsPerTrack)
`r`n Signature: $($objItem.Signature)
`r`n Size: $($objItem.Size)
`r`n Status: $($objItem.Status)
`r`n Status Information: $($objItem.StatusInfo)
`r`n System Creation Class Name: $($objItem.SystemCreationClassName)
`r`n System Name: $($objItem.SystemName)
`r`n Total Cylinders: $($objItem.TotalCylinders)
`r`n Total Heads: $($objItem.TotalHeads)
`r`n Total Sectors: $($objItem.TotalSectors)
`r`n Total Tracks: $($objItem.TotalTracks)
`r`n Tracks Per Cylinder: $($objItem.TracksPerCylinder)
`r`n ” >> $file
}

Product

AppAssure 5.3.x

Problem Description

You want to pause the snapshots of a few agents on the core but, due to the complex naming conventions, you would prefer not typing their names in a script or to prepare a file containing the list of agent names.

Warning: Dell does not support the use of PowerShell scripts in AppAssure. Click here for more details.

Resolution

A script using a gridview has been prepared. Please note that due to some inconsistencies in the way Powershell manages grid-views, the code is less synthetic and slightly more complicated than it should. This is based on experience, as the objects passed directly to the grid-view may behave unexpectedly. In a nutshell, after selecting the type of operation (Suspend/resume), the agents protected on the core are displayed in a gridview, in a manner consistent with their status (either only those which are paused or those which are active). Using the Grid-View properties, they can be filtered them based on a series of criteria (name, agent software version etc). Once an easier to handle view is achieved, highlighting the needed agents and clicking OK (on the button placed on the lower right side of the gridview) will start the pause process, which is reported in the Powershell Console. When resuming, only the paused agents are shown in the grid view. Select the desired ones & clicking OK results in starting the resume procedure.

Please note that this script is supposed to run under Powershell 3.0 or later.

#this script suspends or resumes protection on selected agents
write-host “`r`nSuspend or Resume Protection`r`n____________________________`r`n”

#select the type of job to perform
do {
$op = Read-Host “[S]uspend or [R]esume Protection”
}
until (“s”,”r” -contains $op.tolower())

#A little hint to help further
Write-host “Hint:Select desired agents and click OK in the gridview to continue” -f “Yellow”

#Various values to help processing the request
$crit = $False
$pref = “Suspend”
if ($op.tolower() -eq “r”)
{
$crit = $True
$pref=”Resume”
}

#check ISE status & Install if necessary (needed for the grid-view)
$ise = get-windowsfeature | where {$_.name -like “*ise*”}
if ($ise.installstate -eq “Available”){Install-WindowsFeature -name Powershell-ISE}

#Deal with the inconsistencies of the Grid-View

#get agents
$a = get-protectedservers

#create an empty object to add the protected agents one by one
$agents = @()

#create the gridview
foreach ($a1 in $a) {if ($a1.IsPaused -eq $crit){$agents +=$a1}}
$zagents = $agents |out-gridview -passthru

#exit if no agent is selected
if ($zagents.count -eq 0){Exit}

#create the commandlet as a string, transform it into a scriptblock and execute it
foreach ($agent in $zagents.displayname)
{
$t = “$pref-snapshot -protectedserver $($agent)”
$sb = $executioncontext.invokecommand.NewScriptblock($t)
Write-host “Attempting to $($Pref) $($agent)” -f “Yellow”
&($sb)
}

Affected Builds

AppAssure 5.3.x

Problem Description

Upon adding (usually SQL Agents) to Appassure in the windows event logs on the agent the following type of error messages are seen repeatedly.

DATE/TIME: 1/2/2014 11:23:49 AM

DESCRIPTION: Login failed for user ‘testserver\Administrator’. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: 192.15.115.123]

COMMENT: (None)

JOB RUN: (None)

Resolution

This is not an Appassure Issue please reference solution below:

http://www.sqldbops.com/2010/05/token-based-server-access-validation.html

Affected Builds

AppAssure 5.3.x

Problem Description

During the troubleshooting process, it may become necessary to stop services which are not listed in task manager or in the services MMC console. These services may be unlisted dependencies of other services. If the operation fails, the next logical step is to kill the associated tasks. However, to do that, identifying the PID associated with the service/associated is necessary.

Warning: Dell does not support the use of scripting in AppAssure. Click here for more information.

Resolution

In order to achieve this, a few PowerShell commandlets are necessary. Due to the unique nature of each case we do not recommend scripting this process as the results may need more investigation before proceeding. The necessary commented PowerShell Commandlets are shown below between horizontal lines.

#get services with the “StopPending” status
$Service = Get-Service | where { $_.Status -eq “StopPending” }

#list the services in the “StopPending” state by name
$Service.Name

#we assume that only one service is in this state.
#If more services are in the “StopPending” status, you can select the one you need by using its zero-based index
#i.e. Service[0].Name, Service[1].Name etc

#get the PID using wmi
$ServicePID = (Get-Wmiobject win32_Service | Where { $_.Name -eq $Service.Name }).ProcessID

#since the service and the associated process share the same PID, attempt killing the process
Stop-Process $ServicePID

Affected Builds

AppAssure 5.3.x

Problem Description

When attempting to mount a recovery point, a Win32 API Failed Exception: “NetUserAdd failed – the user already belongs to this group” Error occurs. Attempts to dismount or mount other recovery points fail with the same error.

The ephemeral account created by AppAssure to mount a recovery point is not deleted as normal, and its presence blocks the creation of a new ephemeral account for subsequent mounting jobs. This has been known to occur under rare circumstances on core server which have the Active Directory role installed.

Resolution 

1. Open Server Manager and browse to User Accounts 
2. Open Local Users and search for an account named “ReplayEnginexxx”where ‘xxx’ is a unique indentifier. 
3. Delete this account. 
4. Verify that mounting process works properly. 

Product:

Replay 4.x

Problem Description:

Agents Alerts do not reflect updated information which is displayed on the CORE console. The information on the CORE events and Agent events are not in sync.

Resolution:

Replay Events are out of sync due to the size of the current events within the Windows AppAssure log within Windows Event Viewer. You will need to clean up the Appassure events.

Complete the following steps.
1. Log on to the Agent which is not reflecting events correctly
2. Open Event viewer ( Click the Windows “Start” button and click “Run.” Type “”eventvwr” (without the quotes) and press “Enter” to launch the Event Viewer.
3. Select Application and Services logs, then select AppAssure.
4. On the Actions please select Save and Clear to preserve the events or just Clear if you do not want to save the old events.
5. Restart the Replay Agent Service.
6. Restart the Replay Admin Console and select the Agent which was having the events issue and monitor to see if new events populate.
7. If the events do not populate correctly please contact support.

Product

AppAssure 5.x

Description:

CORE Keeps spamming the Apprecovery log for a specific Repository, reporting the following information in the Apprecovery.log file, AAInfo, and the Events tab of the Core Console.

DEBUG 2013-09-05T09:03:25 [12] – Replay.Core.Implementation.Repositories.Repository (Repository)
Verifying remote repository location \\Server Name\Share Name

DEBUG 2013-09-05T09:03:25 [12] – Replay.Common.Implementation.NetworkAccess.NetworkShareMapper (Repoistory MapNetworkPathToLocalDriveInternal(\\Server Name\Share Name))
Mapping network path ‘\\Server Name\Share Name’ to a local drive

DEBUG 2013-09-05T09:03:25 [12] – Replay.Common.Implementation.NetworkAccess.NetworkShareMapper (Repoistory MapNetworkPathToLocalDriveInternal(\\Server Name\Share Name))
Parsed network path into components share=\\Server Name\Share Name, path=

DEBUG 2013-09-05T09:03:25 [12] – Replay.Common.Implementation.NetworkAccess.NetworkShareMapper (Repoistory MapNetworkPathToLocalDriveInternal(\\Server Name\Share Name))
Successfully authenticated network path ‘\\Server Name\Share Name’

DEBUG 2013-09-05T09:03:25 [12] – Replay.Core.Implementation.Repositories.Repository (Repository)
Verifying remote repository location \\Server Name\Share Name

DEBUG 2013-09-05T09:03:25 [12] – Replay.Common.Implementation.NetworkAccess.NetworkShareMapper (Repoistory MapNetworkPathToLocalDriveInternal(\\Server Name\Share Name))
Mapping network path ‘\\Server Name\Share Name’ to a local drive

DEBUG 2013-09-05T09:03:25 [12] – Replay.Common.Implementation.NetworkAccess.NetworkShareMapper (Repoistory MapNetworkPathToLocalDriveInternal(\\Server Name\Share Name))
Parsed network path into components share=\\Server Name\Share Name, path=

DEBUG 2013-09-05T09:03:25 [12] – Replay.Common.Implementation.NetworkAccess.NetworkShareMapper (Repoistory MapNetworkPathToLocalDriveInternal(\\Server Name\Share Name))
Successfully authenticated network path ‘\\Server Name\Share Name’

DEBUG 2013-09-05T09:03:25 [12] – Replay.Core.Implementation.Repositories.Repository (Repository)
Verifying remote repository location \\Server Name\Share Name

Resolution:

This is a work around as this is a Known issue which happens very rarely.

You will need to Recreate the Repository so you must have Auxiliary space to begin with.

Complete the following steps for the workaround:
1. Create a new Repository.
2. Stop the CORE Service.
3. Copy all the contents from the original repository to the new location replacing all the files.
4. Keep the the old Repository ID file and rename the new Repository XML file to old.
5. Start the CORE Service.
6. If you have any issues during this process contact Support.