Product:

AppAssure Agent 5.X

Problem Description:

Linux agent(s) configured for XFS volume with different block size (512, 1024, 2048) fail to mount. This applies to all support Linux OS

Problem Cause:

root@ubuntu:/var/log/appassure# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 19G 6.3G 12G 36% /
udev 485M 8.0K 485M 1% /dev
tmpfs 198M 1020K 197M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 495M 284K 494M 1% /run/shm
/dev/mapper/lvm-lvmext4 5.9G 1.5G 4.1G 26% /mnt/lvmext4
/dev/md127 4.0G 1.4G 2.4G 37% /mnt/raidext3
/dev/sdk2 4.7G 2.1G 2.4G 47% /mnt/5ext4
/dev/sdl1 5.2G 2.2G 2.8G 44% /mnt/5ext4-2
/dev/mapper/lvm-lvmxfs 5.9G 33M 5.9G 1% /mnt/lvmxfs
/dev/md128 4.0G 1.4G 2.7G 34% /mnt/raidxfs
/dev/sdl2 4.8G 2.1G 2.8G 43% /mnt/5xfs-2
/dev/sdk1 5.2G 2.2G 2.8G 44% /mnt/5ext3
/dev/sdm 300G 46G 255G 16% /mnt/sdm

root@ubuntu:/var/log/appassure# ls -la /mnt/sdm/
total 4
drwxr-xr-x 3 root root 21 Nov 4 01:54 .
drwxr-xr-x 12 root root 4096 Oct 31 08:09 ..
drwxrwxr-x 2 root disk 51 Nov 4 02:25 .blksnap

root@ubuntu:/var/log/appassure# du -hs /mnt/sdm/.blksnap/
45G/mnt/sdm/.blksnap/

There is no data on /dev/sdm volume, only data-store.

Resolution:

This issue is resolved in the 5.3.7.60 release of AppAssure 5

Defect ID#: 

D-18483

Affected Builds:

Replay 4.x

Description:

In Replay 4, the Exchange EDB checksum is being skipped due to the following reported error:

“DsmLoadDll failed with error code -1004. EDB checking will be skipped. Please verify that the following DLLs are copied into the Replay Core install directory from the \exchsrvr\bin directory on an Exchange server: ese.dll, jcb.dll, exosal.dll, and exchmem.dll”

We have copied the required files across as instructed in the error event and ensured all files have adequate permission, to no avail, there are no other obvious issues on this Core machine.

Resolution:

Regarding this Replay error “DsmLoadDll failed with error code -1004″ where the Exchange EDB checking is skipped, this is due to an environmental factor.

Replay uses Microsoft’s ESEUtil to run the checks which the log truncation is dependent upon and there are compatibility factors per Microsoft.

If the Exchange EDB is from a 2003 / 32 bit Exchange server, then the ESEUtil can only run on a 2003 Server 32 / 64 bit server.  This is due to the way that the integrity / mount checks are processed by the Microsoft utility and the limitation is per Microsoft.

Now you can indeed continue to protect the Exchange 2003 instance with the Windows 7 / 64 bit core but the checks will not be available due to this incompatibility.

In order to use the integrity / mount checks options and truncate the logs (which is dependent upon a successful check) you would need to protect that Exchange server from a core running Server 2003 / 32 or 64 bit OS.

Here is the Exchange compatibility matrix per Microsoft as a reference so that the correct Core OS / bit version is used for future protection scenarios and all the options can be used.

The Exchange DLL errors are due to the Replay core running 2008 R2 and then the agent running server SBS 2003 with Exchange 2003. Please refer to page 10 of the link in reference to environmental compatibility. You will still be able to snap but the checks wont run due to the compatibility issue.

http://www.appassure.com/wp-content/uploads/2009/12/Replay-4-Environmental-Assessment-Guide.pdf

If you have the core running Server 2003 / 32 or 64 bit OS and still getting the same error, please verify that the following DLLs are copied into the Replay Core install directory from the \exchsrvr\bin directory on an Exchange server: ese.dll, jcb.dll, exosal.dll, and exchmem.dll into the core at C:\ program files\appassure software\

Affected Builds

Replay 4.x

Problem Description:

Some NAS devices used for the repository will include a directory named “Trashbox” on the root of the NAS device as well as the “Tevorepository” directory where the recovery points will be stored

Problem Cause:

You may find that there are some files with the EPS file format within the “Trashbox” directory and possibly other files as well outside of Replay.

These files were not placed in the “Trashbox” by the end user but these files are taking up space that is needed for the repository

Resolution:

The “Trashbox” directory is not created by the Replay core or the Replay agent and is actually created and managed by the NAS device itself. When files are deleted from the NAS or its sub-directories the files will be placed in the “Trashbox” directory instead of simply being removed from the server. This process is completely managed by the NAS and Replay will not look in the “Trashbox” directory and will only look in the “Tevorepository” directory where the agents snapshots / recovery points have been transferred.

Some NAS devices do include an option within the NAS management console / software to disable / remove the “Trashbox” directory. If there are no options to disable or remove this directory then removing the files within this directory will need to be a manual process to regain the space.

It is always suggested to verify the date of the files within the “Trashbox” directory in order to determine if the files are simply old / out of date files or they were placed in the “Trashbox” mistakenly.

Affected Builds:

AppAssure Core 5.3.x

Problem Description:
You want to schedule replication to suspend during peak hours and resume during off-peak hours.

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.

Resolution:
Write two batch files containing powershell command-let for suspending and resuming replication. The Windows Task Scheduler would then be used to schedule peak & off-peak hours.
Create the powershell file to suspend replication:
1. On the Core, create a folder called c:\AAReplication
2. Create a file called c:\AAReplication\Suspend.ps1
Paste in the following code (substituting [ip address] for the core’s name or ip address:
#Importing the appassure powershell module
Import-module appassurepowershellmodule

#Pausing replication on the master Core for all agents
Suspend-replication –outgoing [ip address]

#Pausing replication on the target core for all agents
Suspend-replication –incoming [ip address]
Create the powershell file to resuming replication:
1. Create a file called c:\AAReplication\Resume.ps1
Paste in the following code (substituting [ip address] for the core’s name or ip address:
#Importing the appassure powershell module
Import-module appassurepowershellmodule

#Resuming replication on the master Core for all agents
Resume-replication –outgoing [ip address]

#Resuming replication on the target core for all agents
Resume-replication –incoming [ip address]

Create two batch files for suspending and resuming:
1. Create a file called c:\AAReplication\Suspending.bat
Paste in the following code:
Powershell c:\AAReplication\Suspend.ps1
2. Create a file called c:\AAReplication\Resuming.bat
Paste in the following code:
Powershell c:\AAReplication\Resume.ps1

Create a windows Scheduler Task called AASuspend_0:
1. Choose the location of c:\AAReplication\Suspending.bat
2. Make sure the account used to run the task has all the appropriate permission and select the “Run whether user is logged on or not”
3. Depending on the environment, it may make sense to check the “Run with highest privileges” checkbox.
4. In the Triggers pane, click on “New” and set the schedule for running the task.
5. On the Settings Tab, select the options that make the most sense for you.
6. Repeat the steps above for the Resuming.bat.

Affected Builds
AppAssure 5.3.6.125

Introduction
While performing a mail restore, messages are not displayed and Mail Restore is stuck on ‘Retrieving Messages.’

Description
While performing a mail restore, messages are not displayed and Mail Restore is stuck on ‘Retrieving Messages’ which is displayed on bottom left hand corner of Mail Restore window. It could be a folder with one email and it will never load.

Solution
1. Verify LMU & MR are same version as Core, if not, update then step 2
2. Run Physical check on mailbox, if check comes back clean step 3
3. Close MR, dismount all mount points, close LMU
4. Install CB P-0470 on machine that Mail Restore will be used on:
a. For all MR folders on machine back up .dll’s to be replaced
b. Replace .dll’s with files from P-0470
5. Repeat Mail Restore process, messages should now be displayed and recoverable.

Affected Builds:

AppAssure 5.3.x

Description:

After an upgrade of the Core Service, the Service will not start. In the Apprecovery logs, the following sequence of events is laid out:

INFO 2013-12-26T16:05:55 [9] – Events.CoreService.CoreServiceStartedEvent ()
The AppAssure 5 service on host has started

ERROR 2013-12-26T16:05:56 [9] – Replay.Core.Service.CoreService ()
Caught exception during service start
System.IO.DirectoryNotFoundException: Physical path cannot be found.
at Replay.ServiceHost.Implementation.Hosting.WebServer.VerifyServerConfiguration()
at Replay.ServiceHost.Implementation.Hosting.WebServer.StartListening()
at Replay.Core.Service.Core.Start()
at Replay.Core.Service.CoreService.OnStart(String[] args)

DEBUG 2013-12-26T16:05:56 [9] – Replay.Common.Implementation.Services.ServiceStatusReporter ()
Service stopped. Sending ‘ServiceStopped’ status

Problem Cause:

The Core may have been installed onto one volume and then moved to a different volume than previously. There is a common practice in keeping installed programs off the system volume. When verifying the AppRecoveryInstallation.log there are no install errors or failures. During installation of the Core Service, residual left over information from previous files may revert the “physical path” back to the very original location. Thank can be changed in the registry in order to resolve the problem.

Solution:

• Verify that the “physical path,” or installation path of the Core.Service is accurate in the following registry key: \HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\webServer.
• There will be a “Physical Path” key with a file directory path.
• If it is different than the location of the current Core installation, it will need to be changed.
• With the Core.Service off, make the necessary changes and attempt to start the Service.
• The Service should now start and a detailed repository check will take place.

Problem Description:

When attempting to export to 2012 R2 Hyper-V the following error
WMI call to remote machine failed
Unknown WMI error: Invalid class :

ERROR 2013-12-30T08:11:43 [370] – Replay.Common.Implementation.WmiApi.Wmi (RequestUri=https://localhost:8006/apprecovery/api/core/export/schedule/vm/location/validate ClientAddress=::1:64735 Service=Replay.Core.Management.Export.ExportSchedulerManagement Method=ValidateExportLocation) 
Unknown WMI error: Invalid class 
System.Management.ManagementException: Invalid class 

Problem Cause: 

API’s have changed in 2012 R2 Hyper-V. Virtual Export to 2012 R2 Hyper-V hosts is not currently supported.

Resolution:

This functionality is not supported at this time and will be added in a future release.

Product:

AppAssure 5 Core Build 5.3.x

Affected Builds:

AppAssure 5.3.x

Problem Description:
1. More space needed on source core or target core repositories
2. Agent repository location has changed on source core but not the target core and you are unable to replicate data.

Problem Cause:
You want to move the agent(s) to a repository on the source and the target then continue to replicate.

Resolution:

The steps below will help archive the agent(s) recovery points on the source core and relocate to a new repository.
Complete the steps listed below to direct an agent to a different repository.
1. Pause protection for all agents by doing the following:
• Navigate to the Core Console UI and click the Machines tab.
• Select all agents.
• Click Actions and then select Protection.
• Click Pause Protection.
 
• Repeat for every agent if there are multiple pages on the Machines tab.
2. Cancel all current operations by doing the following:
• Navigate to the Core Console UI and click the Machines tab.
• Select all agents.
• Click Actions, select Cancel and then click All Operations.
• Repeat for every agent if there are multiple pages on the Machines tab.
3. If needed you can archive the current recovery points. Deleting is faster; however you do not get to keep your recovery points.
• Navigate to the Core Console UI and select the Tools tab.
• Click Archive and then select Create and Archive.
• Fill in all options
 
4. To delete current recovery points, do the following:
• Select and agent.
• Click the Recovery Points tab, and then click Actions.
• Select Delete All Recovery Points.
 
5. Create the new repository by doing the following:
• Once deletion or archival has completed, navigate to the Core Console UI and click the Configuration tab.
• Click Repository and select Actions.
 
• Click New Repository and provide a path for the data and metadata. NOTE: This cannot be the root of the drive.
 
• Provide a size and click OK.
6. Point agents to the new repository by doing the following:
• Select an Agent.
• Click the Configuration tab, and then click Change.
• Under Repository, select the drop down box, and then select the new repository.
 
• Click OK.
• Repeat for all agents.
7. Perform an import for archived recovery points if necessary.
• Navigate to the Core Console UI and select the Tools tab.
• Click Archive and then select Import.
 
• Fill in all options.

8. Resume protection by doing the following:
• Navigate to the Core Console UI and click the Machines tab.
• Select all agents.
• Click Actions and then select Protection.
• Click Resume Protection.
 
• Repeat for all agents if there are multiple pages on the Machines tab.

****Base images will now be taken at the next snapshot interval****

—————————————————————————————————————————————-
The steps below will walk you through archiving the recovery points on the target core and moving to a different repository, then breaking and reconfiguring replication.
1. On the Source core, navigate to the replication tab and pause replication for all agents
2. On the target Core, Select core> tools tab and archive
3. Archive the agent(s) that needs to be relocated (Proceed to next steps only if archiving is completed.)
4. On the Target core, navigate to the replication tab
5. Check the box beside the agent(s) you want to move to a new repository
6. Delete the agent from replication along with recovery points (This will permanently delete your agent recovery points)
7. After deletion is finished under events tab, proceed to the next steps
8. Add new repository to target core if applicable
9. On the Source Core, navigate to the replication tab and add agents back to replication
***You will be asked what repository you want the agent to point to, select desired repository location at this time.
10. Quickly navigate to the replication tab and pause replication for the agents just added
11. On the Target core, import the recovery points from step 3 and select the desired repository. They will now show up as recovery points only on the left side menu
12. Once import is finished on the target core, proceed to the next step
13. On the Source core, under replication tab, resume replication for all agents or replicate the newly moved agents first to verify they replicate properly.

Product:

AppAssure 5.x

Problem:

Initial Base Image fails with Timeout error on one drive, but not all.  Progress of snapshot does not progress beyond determining data to send.  Timeout settings on the core and agent have been increased, and timeout is occurring based on the core’s settings, not the agent (ie, timeout occurs at 10 min, and the core settings cannot be extended beyond this)

Resolution:

1) Verify that VSS writers are stable. If they are not, attempt to reset the following services and test VSS writers again:
· COM+ Event System
· COM+ System Application Service
· Distributed Transaction Coordinator Service
· Volume Shadow Copy Service

2) Verify that VSS shadowstorage is set to ‘unbounded’ or ‘no limit’

3) Ensure you can create a shadow copy via CMD
( vssadmin create shadow /for=[driveletter]: )

4) Delete all shadow copies
( vssadmin delete shadows /all )

5) Clear AAlog files for that drive
http://www.appassure.com/support/KB/log-write-failed-for-device-with-aavolflt-error-code-9267/

6) Force snap

Product:

AppAssure 5.x

Replay 4.x

Problem Description:

The AppAssure Core is transferring random base images for protected virtual guests. and there have been no known reasons for additional base images. At the same time these guests are protected by AppAssure, VM snapshots may  also be enabled for the host’s guests.

NOTE:
Other reasons for unexpected base images should be investigated prior to continuing with the information to follow. For more specifics on why unexpected base images are snapped and transferred, please take a look at this KB article: http://www.appassure.com/support/KB/unexpected-base-images-created-in-appassure-5/

Problem Cause:

In your system event logs, following trail of events will be found:
Event 1) Event ID 7036: The Volume Shadow Copy service entered the running state.
Event 2) Event ID 7036: The VMware Snapshot Provider service entered the running state.
Event 3) Event ID 9289: AAFsFlt cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

More information on event ID 7036: http://technet.microsoft.com/en-us/library/cc756308(v=ws.10).aspx

Resolution:

When the VMware Snapshot initiates, it is quiesceing the file system, which includes flushing memory (https://www.vmware.com/support/ws4/doc/preserve_snapshot_ws.html). The VSS process also quiesces the file system (http://technet.microsoft.com/en-us/library/cc785914(v=ws.10).aspx) these events are conflicting, which is preventing the AppAssure filter drivers from accessing the AppAssure change log.

This link from VMware details further how the snapshot process works: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1015180

To resolve the issue of having random base images snapping for protected virtual agents, disable the snapshot feature for those guests within the hypervisor itself.

Affected Builds:

AppAssure 4.x

Description:

An agent is failing to back up, and producing the following error:

“Unexpected internal error verifying recovery points for source ‘[AgentName]‘ SQL statement ‘SelectEpochsNewerThanSnapshotTime’ failed with ‘Locally cached epoch was not found; ‘[AgentName]‘ epochKey ’689′.”

Solution:

• When faced with this error, In the Core registry investigate the agent settings in \ReplayEPS\[AgentName]\
• Navigate to the following path, and ensure that the repositry path is correct:
• “HKLM\SOFTWARE\AppAssure\ReplayEPS\[AgentName]\ProtectionGroups\Vols240MinIntervals”
• Within this hive, you should see a target_path key.
• If the location does not point to the current repository folder, correct the value and force a snapshot of the affected agent.
•  The issue should be resolved.

Product:
DL-4000

Problem Description:
After upgrading the DL4000 to the latest build of AppAssure 5, the appliance tab may throw the following error:
Unable to connect to the Dell Storage Management Web Service. Please try restarting the service and reload this page.

When you attempt to start this service, the service will crash during the starting service phase.

Problem Cause:
This may be caused by the LSI Provider not being installed properly when you upgrade the core software.

Resolution:
Run the unregister.bat file contained in the C:\lsi folder
Run compile_mofs_wmi.bat in the C:\lsi folder.

Once this is done you should be able to restart the Dell Storage Management Web Service, and the LSI.

Affected Builds:

AppAssure 5.3.x

Description:

These are troubleshooting steps to fix the error:
VSS error: DoSnapshotSet failed with error: ‘The system or provider has insufficient storage space. If possible delete any old or unnecessary persistent shadow copies and try again.’

Writer name: ‘Shadow Copy Optimization Writer’
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {b35ca700-99df-48e4-afcb-e2e338f5ebf6}
State: [7] Failed
Last error: Timed out

Error during the last asynchronous operation.
- Returned HRESULT = 0x8004231f
- Error text: VSS_E_INSUFFICIENT_STORAGE
- Please re-run VSHADOW.EXE with the /tracing option to get more details

Solution:

• Complete the steps in this article to delete AppAssure Change Logs and lift VSS limits:
• http://www.appassure.com/support/KB/dosnapshotset-failed-with-error-the-system-or-provider-has-insufficient-storage-space-if-possible-delete-any-old-or-unnecessary-persistent-shadow-copies-and-try-again/
• If after trying the steps above, you still get the insufficient storage error, please do the following
• Open Command Prompt and type the following:
• FSUTIL USN DELETEJOURNAL /N /D X:
• (where X is the letter you assigned to the System Reserved partition above)

Affected Builds:

AppAssure 5.3.x

Description:

Agent service will not start on a Windows Server 2003 machine.
When you go to start the agent it will fail and never start.

In the AppRecovery logs you see this error:
ERROR 2014-01-28T17:19:47 [4] – Replay.Agent.Service.AgentService ()
Caught exception during service start
Replay.Common.Contracts.WmiApi.WmiException: Unknown WMI error: Unknown WMI error: The specified module could not be found. (Exception from HRESULT: 0x8007007E) —> Replay.Common.Contracts.WmiApi.WmiException: Unknown WMI error: The specified module could not be found. (Exception from HRESULT: 0x8007007E) —> System.IO.FileNotFoundException: The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)

Solution:

Re-register all of the dlls and recompile the .mofs in the wbem folder and re-registering WMI Service and Provider.
You can use the following script by saving to txt file then renaming to .bat and running from command prompt with admin rights and changing focus to following directory: C:\Windows\System32\Wbem.

@echo off
sc config winmgmt start= disabled
net stop winmgmt /y
%systemdrive%
cd %windir%\system32\wbem
for /f %%s in (‘dir /b *.dll’) do regsvr32 /s %%s
wmiprvse /regserver
winmgmt /regserver
sc config winmgmt start= auto
net start winmgmt
for /f %%s in (‘dir /s /b *.mof *.mfl’) do mofcomp %%s

Reboot the machine and test WMI

Product:

AppAssure Core 5.X

Problem Description:

When exporting a Windows Server 2012 R2 virtual machine agent to ESXi, the virtual export is not bootable.

Problem Cause:

The exported VM has a different virtual environment configuration (.vmx) than the protected VM. This can be a cause for ‘INACCESSIBLE BOOT DEVICE’ error upon boot. The scsi configuration of the protected VM and exported VM must be identical for the exported VM to boot successfully.

Resolution:

This issue is resolved in the 5.3.7.60 release of AppAssure 5

Defect ID#:

D-16386

Product: 

AppAssure Core 5.X

Problem Description:

SQL metadata is not called when sysadmin rights are not enabled on the agent machine. SQL metadata should be detectable an generate an alert when the SQL user(s) sysadmin role is not enabled.

Problem Cause:

ERROR 2013-10-28T17:36:16 [29] – Replay.Common.Implementation.Metadata.Sql.SqlMetadataService (RequestUri=https://127.0.0.1:8006/apprecovery/api/agent/metadata/fullMetadata ClientAddress=127.0.0.1:63150 Service=Replay.Agent.Management.Metadata.AgentMetadataManagement Method=GetCurrent)
Failed to gather full agent’s SQL metadata
Microsoft.SqlServer.Management.Common.ConnectionFailureException: Failed to connect to server ‘Server_Name’\MSSQLSERVER,1433. —> System.Data.SqlClient.SqlException: Login failed for user ‘sa’.
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.Common.ConnectionManager.InternalConnect(WindowsIdentity impersonatedIdentity)
at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
— End of inner exception stack trace —
at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
at Microsoft.SqlServer.Management.Common.ConnectionManager.get_DatabaseEngineType()
at Microsoft.SqlServer.Management.Smo.Server.GetExecutionManager()
at Microsoft.SqlServer.Management.Smo.Server.GetPropertyMetadataProvider()
at Microsoft.SqlServer.Management.Smo.Server.get_VersionString()
at Replay.Common.Implementation.Sql.SqlInteractionHelper.<Connect>b__1()
at System.Threading.ThreadLocal`1.GetValueSlow()
at Replay.Common.Implementation.Sql.SqlInteractionHelper.Dispose(Boolean disposing)
at Replay.Common.Implementation.Sql.SqlInteractionHelperBase.Dispose()
at Replay.Common.Implementation.Metadata.Sql.SqlMetadataService.GetFullSqlInstanceMetadata(MetadataCredentials metadataCredentials, InstanceSummary instanceSummaryMetadata, SqlClusterMetadata sqlClusterMetadata)
at Replay.Common.Implementation.Metadata.Sql.SqlMetadataService.GetSqlMetadata(MetadataCredentials metadataCredentials, SqlClusterMetadata sqlClusterMetadata)

Resolution:

This issue is resolved in the 5.3.7.60 release of AppAssure 5

Defect ID#: 

D-18394

Product:

AppAssure Core 5.X

Problem Description:

Incorrect OS Version for Windows 2012R2 and 8.1 machines is displayed on the ‘Tools’ >> ‘System Info’ section of the Web UI at the core and agent level.

Problem Cause:

The metadata call for Windows system properties incorrectly identifies Windows 2012 R2 servers as Windows 2012 machines and Windows 8.1 machines as Windows 8 machines.

Resolution:

This issue is resolved in the 5.3.7.60 release of AppAssure 5

Defect ID#: 

D-18428

Product:

AppAssure Core 5.X

Problem Description:

In the ‘Tools’ >> ‘Mounts’ section of the Web UI, the help button (question mark) points to the wrong link at the core and agent level.

Problem Cause:

Context-sensitive Help link on Mounts page goes to the wrong Help topic
URL: /WebHelp/index.htm#AppAssure5_UG/AppAssure5_UG_Ch4/Mounting_a_Recovery_Point_for_a_Windows_Machine.htm
We have corrected this behavior to now point to the correct help resource.
URL: /WebHelp/index.htm#AppAssure5_UG/AppAssure5_UG_Ch5/Dismounting_Local_Recovery_Points.htm

Resolution:

This issue is resolved in the 5.3.7.60 release of AppAssure 5

Defect ID#:

D-13517

Product:

AppAssure Agent Ubuntu 13.10 5.X

Problem Description:

After installing the agent software on an Ubuntu 13.10 the agent service fails to obtain the list of attached devices.

Problem Cause:

ERROR 2013-10-18T08:30:45 [1] – Replay.Common.Implementation.Drivers.BlockSnap ()
bsctl encountered an error when processing command ‘–list-devices’. Error: bsctl: failed to open /dev/blksnap: No such device

ERROR 2013-10-18T08:30:45 [1] – Replay.Agent.Service.Program ()
Error occurred trying to start agent. Dying gracefully…
Castle.MicroKernel.ComponentActivator.ComponentActivatorException: ComponentActivator: could not instantiate Replay.Common.Implementation.Win32Api.LinuxHardware —> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.InvalidOperationException: GetAttachedDevices failed to return a proper list of devices, error code 1
at Replay.Common.Implementation.Drivers.BlockSnap.GetAttachedDevices () [0x00000] in <filename unknown>:0
at Replay.Common.Implementation.Win32Api.LinuxHardware.set_Partitions (IList`1 value) [0x00000] in <filename unknown>:0
at Replay.Common.Implementation.Win32Api.LinuxHardware.set_Disks (IList`1 value) [0x00000] in <filename unknown>:0
at Replay.Common.Implementation.Win32Api.LinuxHardware.RefreshDevices () [0x00000] in <filename unknown>:0
at Replay.Common.Implementation.Win32Api.LinuxHardware..ctor (Replay.Common.Implementation.Win32Api.LinuxHardwareFactory hardwareFactory, IBlockSnap blockSnap) [0x00000] in <filename unknown>:0
at (wrapper managed-to-native) System.Reflection.MonoCMethod:InternalInvoke (System.Reflection.MonoCMethod,object,object[],System.Exception&)
at System.Reflection.MonoCMethod.InternalInvoke (System.Object obj, System.Object[] parameters) [0x00000] in <filename unknown>:0
— End of inner exception stack trace —
at System.Reflection.MonoCMethod.InternalInvoke (System.Object obj, System.Object[] parameters) [0x00000] in <filename unknown>:0
at System.Reflection.MonoCMethod.DoInvoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0
at System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0
at System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) [0x00000] in <filename unknown>:0
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.FastCreateInstance (System.Type implType, System.Object[] arguments, System.Type[] signature) [0x00000] in <filename unknown>:0
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.CreateInstance (Castle.MicroKernel.Context.CreationContext context, System.Object[] arguments, System.Type[] signature) [0x00000] in <filename unknown>:0
— End of inner exception stack trace —
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.CreateInstance (Castle.MicroKernel.Context.CreationContext context, System.Object[] arguments, System.Type[] signature) [0x00000] in <filename unknown>:0
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.Instantiate (Castle.MicroKernel.Context.CreationContext context) [0x00000] in <filename unknown>:0
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.InternalCreate (Castle.MicroKernel.Context.CreationContext context) [0x00000] in <filename unknown>:0
at Castle.MicroKernel.ComponentActivator.AbstractComponentActivator.Create (Castle.MicroKernel.Context.CreationContext context) [0x00000] in <filename unknown>:0
at Castle.MicroKernel.Lifestyle.AbstractLifestyleManager.Resolve (Castle.MicroKernel.Context.CreationContext context) [0x00000] in <filename unknown>:0
at Castle.MicroKernel.Lifestyle.SingletonLifestyleManager.Resolve (Castle.MicroKernel.Context.CreationContext context) [0x00000] in <filename unknown>:0
at Castle.MicroKernel.Handlers.DefaultHandler.ResolveCore (Castle.MicroKernel.Context.CreationContext context, Boolean requiresDecommission, Boolean instanceRequired) [0x00000] in <filename unknown>:0
at Castle.MicroKernel.Handlers.AbstractHandler.Resolve (Castle.MicroKernel.Context.CreationContext context, Boolean instanceRequired) [0x00000] in <filename unknown>:0
at Castle.MicroKernel.Handlers.AbstractHandler.Resolve (Castle.MicroKernel.Context.CreationContext context) [0x00000] in <filename unknown>:0
at Castle.MicroKernel.Resolvers.DefaultDependencyResolver.ResolveServiceDependency (Castle.MicroKernel.Context.CreationContext context, Castle.Core.ComponentModel model, Castle.Core.DependencyModel dependency) [0x00000] in <filename unknown>:0
at Castle.MicroKernel.Resolvers.DefaultDependencyResolver.Resolve (Castle.MicroKernel.Context.CreationContext context, ISubDependencyResolver contextHandlerResolver, Castle.Core.ComponentModel model, Castle.Core.DependencyModel dependency) [0x00000] in <filename unknown>:0
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.CreateConstructorArgumentsCore (Castle.Core.ConstructorCandidate constructor, System.Object[] arguments, Castle.MicroKernel.Context.CreationContext context, System.Type[] signature) [0x00000] in <filename unknown>:0 at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.CreateConstructorArguments (Castle.Core.ConstructorCandidate constructor, Castle.MicroKernel.Context.CreationContext context, System.Type[]& signature) [0x00000] in <filename unknown>:0

Resolution:

This issue is resolved in the 5.3.7.60 release of AppAssure 5

Defect ID#: 

D-18247

Product:

AppAssure Agent 5.X

Problem Description:

Once you have installed the AppAssure Agent on a Linux machine a paired it to a core, there is no ability to create a datastore on a 2 TB volume

Problem Cause:

root@ubuntu:/home/administrator# bsctl –create-data-store /dev/sdn1
bsctl: ftruncate: File too large

root@ubuntu:/home/administrator# bsctl –map-bitmap-store /dev/sdn1
bsctl: ERROR: operation failed: Input/output error

[11282.854252] blksnap: ioctl: map
[11282.854259] blksnap: WARNING: not enough store space! device has 4278188032 sectors, store is 65540 bytes long, 524288 required!

root@ubuntu:/home/administrator# ll /mnt/bigvol/.blksnap/
total 32844
drwxrwxr-x 2 root disk 2048 Mar 27 08:40 ./
drwxr-xr-x 12 root root 2048 Mar 27 08:38 ../
-rwxrwxr-x 1 root disk 36 Mar 27 08:40 AAData.md*
-r——– 1 root root 268435456 Mar 27 08:39 bitmap
-r——– 1 root root 0 Mar 27 08:38 data
-rw-r–r– 1 root root 36 Mar 27 08:39 volume-guid

System.AggregateException: One or more errors occurred. —> WCFClientBase.ClientServerErrorException: Call to service method https://10.10.62.235:8006/apprecovery/api/agent/transfer/snapshots/12e394d7-2fbf-43a7-8d04-168272f1a712/volumes/~|~~|~%253f~|~Volume%257b40236686-a44f-444d-9832-a362cef0673e%257d~|~/driver GET failed: Failed to map offline data storage for device path of ‘/dev/sdn1′ with error code 5 —> System.AggregateException: Failed to map offline data storage for device path of ‘/dev/sdn1′ with error code 5 —> System.InvalidOperationException: Failed to map offline data storage for device path of ‘/dev/sdn1′ with error code 5
at Replay.Common.Implementation.Drivers.BlockSnap.MapBitmapDataStore (System.String devicePath) [0x00000] in :0
at Replay.Common.Implementation.Drivers.BlockSnap.AttachDevice (System.String devicePath, Boolean createBitmapStore, Boolean createCopyOnWriteStore, Boolean isMounted) [0x00000] in :0
at Replay.Common.Implementation.Drivers.DriverApiImplementation.AttachVolume (Replay.Common.Implementation.Win32Api.LinuxPartition partition) [0x00000] in :0
at Replay.Common.Implementation.Drivers.DriverApiImplementation.AttachVolume (Replay.Common.Contracts.Metadata.Storage.VolumeName volumeName) [0x00000] in :0
at Replay.Common.Implementation.Drivers.DriverApiImplementation.EnableVolumeLogging (Replay.Common.Contracts.Metadata.Storage.VolumeName volumeName, UInt32 epoch, Boolean generateNewGuid) [0x00000] in :0
at Replay.Agent.Implementation.Drivers.DriverApi.EnableVolumeLogging (Replay.Common.Contracts.Metadata.Storage.VolumeName volumeName, UInt32 epoch, Boolean generateNewGuid) [0x00000] in :0
at Replay.Agent.Implementation.Drivers.DriverVolumeLinux.Enable (UInt32 newEpochNumber, Boolean generateNewGuid) [0x00000] in :0
at Replay.Agent.Implementation.Drivers.DriverVolumeLinux.Enable () [0x00000] in :0
at Replay.Agent.Implementation.Transfer.TransferSession.RemoveUnReliableVolumes (IDriversService driversService, IStorageService storageService, IEnumerable`1 volumes, IDictionary`2 errorVolumes) [0x00000] in :0
— End of inner exception stack trace —
at Replay.Agent.Implementation.Transfer.TransferSession.GetVolumeInfo (Replay.Common.Contracts.Metadata.Storage.VolumeName volumeName) [0x00000] in :0
at Replay.Agent.Implementation.Transfer.TransferSession.GetDriverMetadata (Replay.Common.Contracts.Metadata.Storage.VolumeName volumeName) [0x00000] in :0
at Replay.Agent.Management.Transfer.TransferManagement.GetDriverMetadata (System.String snapshotSetId, System.String volumeName) [0x00000] in :0
at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&)
at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in :0
— End of inner exception stack trace —
at WCFClientBase.ClientBase.HandleResponse(Uri uri, String method, HttpResponseMessage response)
at WCFClientBase.ClientBase.GetResponse(Uri uri, String method, String knownEtag)
at WCFClientBase.ClientBase.ExecuteServiceCall[T](Uri uri, String method, String knownETag)
at WCFClientBase.ClientBase.ExecuteServiceCall[T](Uri uri, String method)
at Replay.Core.Implementation.Agents.AgentClient.GetDriverMetadata(Guid snapshotSetId, VolumeName volumeName)
at Replay.Core.Implementation.Transfer.VolumeTransferJob.DetermineDataToSendTask()
at System.Threading.Tasks.Task.Execute()
— End of inner exception stack trace —
—> (Inner Exception #0) WCFClientBase.ClientServerErrorException: Call to service method https://10.10.62.235:8006/apprecovery/api/agent/transfer/snapshots/12e394d7-2fbf-43a7-8d04-168272f1a712/volumes/~|~~|~%253f~|~Volume%257b40236686-a44f-444d-9832-a362cef0673e%257d~|~/driver GET failed: Failed to map offline data storage for device path of ‘/dev/sdn1′ with error code 5 —> System.AggregateException: Failed to map offline data storage for device path of ‘/dev/sdn1′ with error code 5 —> System.InvalidOperationException: Failed to map offline data storage for device path of ‘/dev/sdn1′ with error code 5
at Replay.Common.Implementation.Drivers.BlockSnap.MapBitmapDataStore (System.String devicePath) [0x00000] in :0
at Replay.Common.Implementation.Drivers.BlockSnap.AttachDevice (System.String devicePath, Boolean createBitmapStore, Boolean createCopyOnWriteStore, Boolean isMounted) [0x00000] in :0
at Replay.Common.Implementation.Drivers.DriverApiImplementation.AttachVolume (Replay.Common.Implementation.Win32Api.LinuxPartition partition) [0x00000] in :0
at Replay.Common.Implementation.Drivers.DriverApiImplementation.AttachVolume (Replay.Common.Contracts.Metadata.Storage.VolumeName volumeName) [0x00000] in :0
at Replay.Common.Implementation.Drivers.DriverApiImplementation.EnableVolumeLogging (Replay.Common.Contracts.Metadata.Storage.VolumeName volumeName, UInt32 epoch, Boolean generateNewGuid) [0x00000] in :0
at Replay.Agent.Implementation.Drivers.DriverApi.EnableVolumeLogging (Replay.Common.Contracts.Metadata.Storage.VolumeName volumeName, UInt32 epoch, Boolean generateNewGuid) [0x00000] in :0
at Replay.Agent.Implementation.Drivers.DriverVolumeLinux.Enable (UInt32 newEpochNumber, Boolean generateNewGuid) [0x00000] in :0
at Replay.Agent.Implementation.Drivers.DriverVolumeLinux.Enable () [0x00000] in :0
at Replay.Agent.Implementation.Transfer.TransferSession.RemoveUnReliableVolumes (IDriversService driversService, IStorageService storageService, IEnumerable`1 volumes, IDictionary`2 errorVolumes) [0x00000] in :0
— End of inner exception stack trace —
at Replay.Agent.Implementation.Transfer.TransferSession.GetVolumeInfo (Replay.Common.Contracts.Metadata.Storage.VolumeName volumeName) [0x00000] in :0
at Replay.Agent.Implementation.Transfer.TransferSession.GetDriverMetadata (Replay.Common.Contracts.Metadata.Storage.VolumeName volumeName) [0x00000] in :0
at Replay.Agent.Management.Transfer.TransferManagement.GetDriverMetadata (System.String snapshotSetId, System.String volumeName) [0x00000] in :0
at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&)
at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in :0
— End of inner exception stack trace —
at WCFClientBase.ClientBase.HandleResponse(Uri uri, String method, HttpResponseMessage response)
at WCFClientBase.ClientBase.GetResponse(Uri uri, String method, String knownEtag)
at WCFClientBase.ClientBase.ExecuteServiceCall[T](Uri uri, String method, String knownETag)
at WCFClientBase.ClientBase.ExecuteServiceCall[T](Uri uri, String method)
at Replay.Core.Implementation.Agents.AgentClient.GetDriverMetadata(Guid snapshotSetId, VolumeName volumeName)
at Replay.Core.Implementation.Transfer.VolumeTransferJob.DetermineDataToSendTask()
at System.Threading.Tasks.Task.Execute()<—

In case of trying to create data-store manually:

bsctl: ERROR: operation failed: Input/output error

[11282.854252] blksnap: ioctl: map
[11282.854259] blksnap: WARNING: not enough store space! device has 4278188032 sectors, store is 65540 bytes long, 524288 required!

bsctl: ftruncate: File too large

Resolution:

This issue is resolved in the 5.3.7.60 release of AppAssure 5

Defect ID#:

D-14523