Affected Builds:

AppAssure 5.3.x

Description:

When doing a virtual export, it fails with the following error:

ERROR 2013-12-19T11:23:34 [58] – Replay.Core.Implementation.Export.ExportQueueEntry ()
Export task ’8a8b49a4-9dcf-4356-855f-6b521979005d’ failed
System.AggregateException: One or more errors occurred. —> Replay.Common.Contracts.TevoLib.TevoLibraryErrorException: TevoMountReplay failed with error -2147024775 (0×80070079 – The semaphore timeout period has expired)

Solution:

• Stop the AppAssure Core services
• Navigate to: HKLM\SYSTEM\CurrentControlSet\Services\AAVDisk\Parameters
• Change the NetworkTimeout to 600000 (Decimal Value)
• Next, Navigate to: HKLM\SYSTEM\CurrentControlSet\Services\AAVStor\Parameters
• Change the NetworkTimeout to 600000 (Decimal Value)
• Reboot the Core server for driver changes to take affect.
• Once server is backup, test your exports again.

Affected Builds:

AppAssure 5.3.x

Description:

Agent(s) are showing under replication tab more than once.
If Agent(s) are listed under the replication tab but not listed on main core summary page

Solution:

• On the Source Core
• Go to the replication tab and click the action bar next to the Core name and pause replication

• On the Target Core
• Select the replication tab and remove the duplicate name agents from replication while keeping recovery points.
• NOTE: A window will appear asking whether or not you wish to remove the recovery points as well. Do not check the box marked “with recovery points” if you wish to keep the recovery points for that agent on the Target Core.
• If only one agent displayed under replication tab, but not showing on the main summary page, then remove that agent.

• On the Source Core
• Select replication tab
• Select arrow beside core name and select add machine.
• Add agent(s) back into replication.

• On the Source core
• Select to resume all replication that was paused in step 1.

Link:  Removing and Re-Adding an Agent to Replication

Affected Builds:

AppAssure 5.x

Description

While trying to export or create a virtual standby for a recovery point the following error is received:

Invalid Operation Exception
Cannot execute an export task :

Vddk Api Init Ex Failed Exception: Operation ‘InitEx’ with libDir = ‘C:\Program Files\AppRecovery\Core\CoreService\vddk\bin’ configFilePath = ” failed with System.TimeoutException: The VDDK disk library initialization operation took too long and was cancelled. This is often caused by missing or incorrect VDDK DLLs
Timeout Exception: The VDDK disk library initialization operation took too long and was cancelled. This is often caused by missing or incorrect VDDK DLLs

Resolution

Please contact Appassure Support for a resolution.

Affected Builds:

AppAssure 5.3.6.125

Description

All agents display as offline after upgrading the core to the latest build.

Error:
A call to remote server failed

Details:
Metadata capture from ‘agentname’ has failed
This error could be caused by one of the following:
- Hardware complexity in the system.
- The resource-intensive tasks are running in the system.

When forcing a metadata refresh via the core console agent actions menu, an ‘authentication’ error is displayed.

Resolution

To resolve this issue, re-pair the agents via the ‘Protect Machine’ button on the Machine’s Tab or via the bulk protect tool. This will require re-entering the machine names and credentials.  The core will automatically repair the connection, and the agents will then show as online.

Product:

AppAssure 5.x

Description:

AppAssure 5 does not directly support mailbox level restore from Exchange 2013 at this time. As a work-around, the following procedure will demonstrate how to recover mailbox level items using the Exchange Recovery Database feature.

Connect to the Exchange 2013. All operations will be performed directly from the live server environment. If not yet installed, download and install the Local Mount Utility for AppAssure 5 located in the download section at http://appassure.licenseportal.com.

1. Run the Local Mount Utility, attach to the BCDR, select the Exchange 2013 server from the list of protected servers, and select Refresh Recovery Points. 
2. Browse to the desired recovery point and mount it in Writable mode.
3. Explore the mounted recovery point and browse down to the Exchange 2013 database file. 
4. Create a new folder RDB1 one level up from the backup version of the database file. 
5. Cut the database .EDB file and paste it into the RDB1 folder.
6. Open a CMD windows and change directory to the RDB1 folder.
7. Perform a repair on the database file to enable it to be mounted by Exchange. 
8. From the CMD prompt, run: ESEUTIL /R E00.  Note: Be sure you run this command from the RDB1 directory with the database.EDB file in place. 

A progress bar should display detailing the repair operation. Note that there are (3) separate phases to the repair and if the database is very large this will take quite some time to complete. Once the repair operation is complete, proceed with the remaining steps below.

Create a Recovery Database in Exchange 2013 

Open the Exchange Command Shell and run the following:

New-MailboxDatabase -Recovery -Name RDB1 -Server <ServerName> -EdbFilePath “<full path to .EDB database file in RDB1 directory>” -LogFolderPath “<Full path to RDB1 folder>”. 

To verify successful creation of the database, run the following:

Get-MailboxDatabase 

Mailbox Database RDB1 should be in the list

Restart the Microsoft Exchange Information Store service on the Exchange server 

Run the following command to mount the Recovery Database

Mount-Database RDB1 

The database should mount cleanly provided the repair operation above completed successfully 

Verify the state of the existing user mailbox

Get-MailboxStatistics “<User Alias>”

This will list the item count of the user mailbox prior to the restore. Repeat this command after the restore is complete to verify the recovery was effective.

Recover Mailboxes into the Live Exchange Database 

Restore mailboxes from the Recovery Database to the live database with the following:

New-MailboxRestoreRequest -SourceDatabase RDB1 -SourceStoreMailbox “<User Alias>” -TargetMailbox “<User Alias>” 

Note: If the mailbox was originally created with an earlier version of Exchange and you get an error referencing LegacyDNMismatch, add the parameter -AllowLegacyDNMismatch to the command above. 

The command output should indicate that the request has been queued. To check on the status of the request, run the following command:

Get-MailboxRestoreRequest

Once all outstanding requests show as “Completed” then the recovery is complete.

Affected Builds:

AppAssure 5.3.x

Description:

Volume is not showing up in the Core UI for an Agent system
When you have an active healthy volume on your agent, it is not showing up in the Core

Solution:

1. Log into the Agent system
2. Open up My computer
3. Open up Disk Management
4. Compare the free space between the volume in Disk Management and My Computer
5. If Disk Management is showing 100% free space, but My Computer shows used space, do the following.

• Note: You can continue with the steps below even if the size is the same, but may not be the solution for your specific issue

• Add security an put in this account: SYSTEM
• Assign the SYSTEM account, full control

Now go back to your Core and click on your agent (Core > Machines > Click <Agent-name>)
Click on the action bar near the top-right
Select Refresh Metadata and the drive should now appear.

Affected Builds:

AppAssure 5.3.x

Description:

When opening up the Core Console you see the following error:

ERROR 2013-12-31T15:12:06 [24] – Replay.ServiceHost.Implementation.Hosting.ListenerService ()
Caught exception processing HTTP operation
System.IO.FileNotFoundException: Could not load file or assembly ‘ServiceHost.Implementation, Version=5.3.6.125, Culture=neutral, PublicKeyToken=null’ or one of its dependencies. The system cannot find the file specified.
File name: ‘ServiceHost.Implementation, Version=5.3.6.125, Culture=neutral, PublicKeyToken=null’
at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMarkHandle stackMark, Boolean loadTypeFromPartialName, ObjectHandleOnStack type)
at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, Boolean loadTypeFromPartialName)

Solution:

The Core UI relies heavily on the proper functioning of the .NET Framework. If these XML related errors are presented when loading the UI and the error above is found in the AppRecovery logs, a repair of .NET will need to be performed.

• To repair .NET, navigate to Control Panel -> Programs and Features -> scroll down to .NET Framework and select it.
• Right click and select “change.”
• A popup window will display and select the Repair option.
• When completed, a reboot of the system will be necessary.
• Open up your Core Console once rebooted

Affected Builds:

AppAssure Core 5.3.X

Description:

The AppAssure Core Service Core.Service.Exe terminates without user intervention. As Windows has not crashed, the Core Service restarts automatically shortly thereafter. Agent transfer jobs fail with NullRef exceptions just before the Core Service crash occurs.

Resolution:

This issue is resolved in the 5.3.7.60 release of AppAssure 5

Defect ID#:

D-19052

Affected Builds:

Replay 4.x

Description:

While setting up replication you receive the error message: “Failed to get server replication settings from repl service: Failed to create replication service instance – Class not registered”

Resolution:

The Replay installation was installed under the domain admin account. Replay should always be installed under the Local system admin account. 

On the Core server: 

1. Logoff the current user and logon as Local Admin to the system
2. Open the run command type REGEDIT , select okay
3. Drill down to AppAssure registry key and export the key to a safe location
4. Open the Services menu and stop the Replay Core service
5. Reinstall the Replay software
6. Open Replay console and setup replication

Affected Builds:

Replay 4.x

Description:

When viewing the recovery points in Windows explorer, they are showing up as ?’s rather than the Replay symbols/icons (large and small dots and diamonds) to differentiate the base images from the incremental recovery points and be able to see the detailed properties information (ie: for which volumes).

Resolution:

To resolve this issue, the TevoAddin.dll will need to be re-registered, then you will be able to view the recovery point metadata in the repository when viewing in Windows explorer.

On the Core,

1. Stop the Replay core service

2. Unregister TevoAddin.dll by doing the following:

a. Open a command prompt in elevated mode,

b. Enter the following command to re-register the DLL that handles the file properties and icons:

regsvr32 “C:\Program Files (x86)\AppAssure Software\Replay Server\AddIns64\TevoAddin.dll”

cd C:\Program Files (x86)\AppAssure Software\Replay Server\AddIns64

regsvr32 -u TevoAddin.dll
3. Reboot the core server

Once the Core comes back online, within Windows Explorer navigate to the repository volume, open a protected agent’s repository directory:

I. Verify that the icons are now present

II. Replay tab is present within the file properties

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\

Product:

AppAssure Core 5.X

Problem Description:

When performing a rollback of Exchange or SQL databases using Live Recovery, the job status shows as ‘Error’ and shows all databases as ‘Succeeded’ once the job is expanded in the Events tab on the Web UI.

Problem Cause:

The rollback job was not able to successfully mount one or more Exchange or SQL Server databases. We now show which database(s) on which volume(s) failed to mount during the rollback.

Resolution:

This issue is resolved in the 5.3.7.60 release of AppAssure 5

Defect ID#: 

D-08625

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

Product:

AppAssure Agent 5.X

Problem Description:

After successfully taking a base image of a Linux agent, forcing an incremental snapshot or waiting for the next automatic snapshot results in a new base image being processed.

Problem Cause:

ERROR 2013-09-03T04:45:09 [11] – Replay.Common.Implementation.Drivers.BlockSnap (RequestUri=https://10.10.1.224:8006/apprecovery/api/agent/transfer/snapshots/62c8f083-3edd-4534-93b0-4868f70f3f75/volumes/~|~~|~%253f~|~Volume%257b4ffdbb11-e1b9-4309-8b19-a35568fe9c0c%257d~|~/blocks/changed ClientAddress=10.10.10.187:51149 Service=Replay.Agent.Management.Transfer.TransferManagement Method=GetVolumeChangedBlocks) bsctl encountered an error when processing command ‘–changelog /dev/sde1′. Error: bsctl: ERROR: device /dev/sde1 is busy, please try again later

ERROR 2013-09-03T04:45:09 [11] – Replay.ServiceHost.Implementation.Hosting.ServiceHost (RequestUri=https://10.10.1.224:8006/apprecovery/api/agent/transfer/snapshots/62c8f083-3edd-4534-93b0-4868f70f3f75/volumes/~|~~|~%253f~|~Volume%257b4ffdbb11-e1b9-4309-8b19-a35568fe9c0c%257d~|~/blocks/changed ClientAddress=10.10.10.187:51149) Service Host Error: Service error while handling request [GET https://10.10.1.224:8006/apprecovery/api/agent/transfer/snapshots/62c8f083-3edd-4534-93b0-4868f70f3f75/volumes/~|~~|~%253f~|~Volume%257b4ffdbb11-e1b9-4309-8b19-a35568fe9c0c%257d~|~/blocks/changed]: GetChangedBlocksForSnapshot failed to return a list of changed blocks, error code 16

Request Uri: https://10.10.1.224:8006/apprecovery/api/agent/transfer/snapshots/62c8f083-3edd-4534-93b0-4868f70f3f75/volumes/~|~~|~%253f~|~Volume%257b4ffdbb11-e1b9-4309-8b19-a35568fe9c0c%257d~|~/blocks/changed

Client Address: 10.10.10.187:51149
Identity: POSIX:root
Service: Replay.Agent.Management.Transfer.TransferManagement
Method: GetVolumeChangedBlocks
Resolution:
This issue is resolved in the 5.3.7.60 release of AppAssure 5

Defect ID#: 

D-17206

Product:

AppAssure Core 5.X

Problem Description:

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

Problem Cause:

Mounting fails when block size is different (512, 1024, 2048):

(AppAssure mount) m 6 1 a /mounted2
Getting volume details from server…
Attaching to local block device …
Successfully attached volume image ’44350188-5e7b-4b9c-b66f-d5a25acc0f20:2′ to /dev/nbd1
Mounting ‘/dev/nbd1′ to ‘/mounted2′ as readonly…failed. Please make sure you have the appropriate permissions. Are you running with sudo?

suse11x32:/home/administrator/Desktop # dmesg | tail
[14572.784913] appassure-vss: data store utilization on 8:18 (memory: 7/2048, disk: 0/197128)
[14572.788621] appassure-vss: prune: removing 2 blocks (7 remaining)
[14572.791343] appassure-vss: 8:18 (/dev/sdb2): snapshot ended (mode: stop)
[14575.945213] appassure-vss: data store utilization on 8:193 (memory: 6/2048, disk: 0/196186)
[14575.947324] appassure-vss: prune: removing 4 blocks (6 remaining)
[14575.948879] appassure-vss: 8:193 (/dev/sdm1): snapshot ended (mode: stop)
[14832.058679] XFS (nbd0): Mounting filesystem in no-recovery mode. Filesystem will be inconsistent.
[14909.997243] attempt to access beyond end of device
[14909.998259] nbd1: rw=0, want=10534018, limit=10534016
[14909.999337] XFS (nbd1): last sector read failed

suse11x32:/home/administrator/Desktop # less /var/log/appassure/aamount.log
WARN 2013-10-17T10:17:37 [1] – Performance.Replay.Core.Client.CoreMetadataManagementC
oreClient ()
Execute Action GET https://10.10.1.181:8006/apprecovery/api/core/metadata/ took 00:00:
11.1718999, which is too long

DEBUG 2013-10-17T10:17:39 [1] – Replay.Aamount.Handlers.CommandHandler ()
Mounting ‘/dev/nbd1′ to ‘/mounted2′ mount arguments ‘-o ro,nouuid,norecovery ‘…

DEBUG 2013-10-17T10:17:39 [1] – Replay.Common.Implementation.Utilities.LinuxUtilities
()
Mounting device ‘/dev/nbd1′ at mount point ‘/mounted2′, mount args ‘-o ro,nouuid,norec
overy ‘

DEBUG 2013-10-17T10:17:39 [6] – Replay.Common.Implementation.Utilities.LinuxUtilities
()
Child process status – 10/17/2013 10:17:39 – Process (StdErr) ‘mount’ – mount: /dev/nb
d1: can’t read superblock

Snapshots made via ‘dd’ are mounted successfully when volume is not mounted regardless on block size:

suse11x32:/home/administrator/Desktop # dd if=/dev/sdm1 of=/tmp/test.img

10483712+0 records in
10483712+0 records out
5367660544 bytes (5.4 GB) copied, 68.8575 s, 78.0 MB/s
suse11x32:/home/administrator/Desktop # mount -o ro,loop,nouuid /tmp/test.img /mounted/
Method: GetVolumeChangedBlocks
Resolution:
This issue is resolved in the 5.3.7.60 release of AppAssure 5

Defect ID#: 

D-18232