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

How to Monitor Repository Check Jobs Using PowerShell

$
0
0

Affected Builds

AppAssure 5.3.x and higher

Description

As repository sizes increase, repository check jobs have become time consuming operations. Moreover, on systems short on resources, the GUI may become very slow to respond or even unresponsive for a period of time.

Warning: AppAssure does not support PowerShell scripting. All scripts provided in this article are meant to be used as examples only. Click here for more information.

Solution

A simple PowerShell script which shows in real time the status of the repository check jobs has been prepared. When the checks are done, an e-mail alert is sent.

 

#RepoCheck.ps1

Write-host “`r`n`r`nRepository Check Survey`r`n_______________________`r`n<CTRL-C> to Exit`r`n”

Write-host “$(get-date)… Repository Check Survey Started”  -f  “Yellow”

 

#get cursor position

$saveY = [console]::CursorTop

$savex = [console]::CursorLeft

do{

#place cursor and write the update

[console]::setcursorposition($savex, $savey)

#get-jobs

$x = get-activejobs -all

#refine results

$x | where {$_.Summary -like “*repository*”} | select-object -expandproperty ChildJobsInfo | format-table Summary,Status,@{name=”Progress[%]“;expression={“{0:N2}%” -f($_.progress)}},@{name=”Rate[MB/s]“; expression={“{0:N02}MB/s” -f ($_.Rate)}} -wrap

#get end cursor position

 

#wait for a while

start-sleep 1

}

while ($x)

#exit the loop if job finished

 

 

 

#Make some room the easy way

write-host “`r`n`r`n`r`n`r`n`r`n`r`n`r`n`r`n`r`n`r`n`r`n`r`n`r`n`r`n`r`n`r`n`r`n`r`n`r`n`r`n`r`n`r`n`r`n`r`n`r`n`r`n”

write-host “Repository Check: finished at $(get-date)” -f “Yellow”

#Send e-mail alert

send-mailmessage -from “appassurecore@domain.com” -to “admin@domain.com” -subject “Repository Check Alert” -body “$(get-date)… Repository Check Status: finished” -smtpserver emailsvr.domain.com


How to Monitor Rollup Job Status in Real Time Using PowerShell

$
0
0

Affected Builds

AppAssure 5.3.x and higher

Description

As the number of protected servers increase, rollups become a very sensitive issue. The rollup jobs may take many hours or even days to complete. Moreover, there is a good chance that, in the case of systems short on resources, the GUI becomes slow to update or even unresponsive for periods of time.

Warning: AppAssure does not support PowerShell scripting. All scripts used in this article are meant to be used as examples only. Click here for more information.

Solution

The script focuses on the current rollup job, showing some key indicators and keeps a summary of completed, pending and errored jobs.

When the rollups is finished an alert e-mail is sent (please update the values in the last lane).

 

#get cursor position

“`r`nCurent Rollup Job`r`n____________________`r`nHit CTRL-C to exit`r`n”

 

#change this value for the refresh frequency [default 5 sec]

$timeslice = 5

 

#import Powershell Module if it is not present

if ((get-module -name appassurepowershellmodule) -eq $null){ import-module appassurepowershellmodule}

 

#get the rollup job

$rollupjob = get-activejobs -all | where {$_.summary -like “*roll*”}

 

#Prepare and show the start time and total job size

$start = $rollupjob | select-object -expandproperty starttime

$work = $rollupjob | select-object -expandproperty totalwork

Write-host (“Job Started on $($start) with a total work of {0:N2}GB” -f ($work/1GB))

 

#get & Save cursor position

$saveY = [console]::CursorTop

$savex = [console]::CursorLeft

#do the job!

do

{

#prepare & display current summary of the job

[int]$succ = 0

[int]$err=0

[int]$pend=0

[int]$running

#place cursor and write the update

$R = get-activejobs -all | where {$_.summary -like “*roll*”} | select-object -expandproperty childjobsinfo

foreach($machine in $R){

if($machine.status -eq “Succeeded”) {$succ++}

if($machine.status -eq “Pending”) {$pend++}

if($machine.status -like “*Err*”) {$err++}

if($machine.status -eq “Running”) {$running++}

}

Write-host “Total: $($R.count) machines, $($succ) suceeded, $($pend) pending, $($err) errored, $($running) running” -f “Yellow”

 

#Prepare and display current job

$x = $R| where {$_.status -eq “Running”}

$x | ft Summary,Phase,@{name=”Remaining”;expression={“{0:N2}GB” -f (($_.TotalWork – $_.Progress)/1GB)}},@{name=”Speed”;e={“{0:N2}MB/s” -f($_.Rate/1MB)}} -wrap

 

start-sleep $timeslice

 

#place cursor and write the update

[console]::setcursorposition($savex, $savey)

}

while ($x)

 

#send e-mail alert

send-mailmessage -from “appassurecore@domain.com” -to “admin@domain.com” -subject “Rollup Job Finished” -body “$(get-date)… Rollup Job Status: finished” -smtpserver emailsvr.domain.

How to Remove the Windows System Reserved Partition (SRP)

$
0
0

Affected Builds

AppAssure 5.3.x

Description

Windows 7, 8, 2008R2 and 2012 use a special partition (100MB for Win 7/2008R2 & 350MB for Win 8/2012) called the System Reserved Partition (SRP) to host the files which initiate the boot of the machine.

Backups can be disrupted frequently due to the System Reserved Partition being completely used either with the AppAssure Change Logs or with files created by a third party software. In many cases, attempting to fix the issue without the help of a support engineer, may result in new base image being taken on all volumes of the protected server, due to unloading the filter drivers without having special tools.

Solution

The radical solution is removing the SRP altogether. Please note that this operation will be successful only if all the prerequisites are satisfied and AppAssure Support cannot take any responsibility in the outcome.

Prerequisites:

  • Windows OS is installed on a MBR Volume. UEFI systems with GPT partitions are not supported.
  • For Windows 7/2008R2 The boot files need to reside on a NTFS partition with the cluster size of 4Kb (the default size). This limitation does not apply to Windows 8/2012
  • Bitlocker should not be used and you should noty plan using it at a later date.
  • The partition containing Windows should be a primary partition. If installed in a logical partition, after removing the SRP, the system will not be bootable. (It can be fixed with third party software, including using a boot manager, though)

Simply put, the process will look as follows:

  1. Copy the Windows booting files and Windows RE (Windows 8 only) to the Windows partition,
  2. Apply the necessary BCD file corrections,
  3. Remove the System Reserved partition (optional)
Complete the following steps.
  1. Boot into Windows
  2. Use Disk Management to assign a letter to the System Reserved Partition
  3. Press WinKey+R, type diskmgmt.msc into the Open box,press OK;
  4. Right-click on the System Reserved partition and select Change Drive Letter and Paths… from the pop-up menu.
  5. The partition will most likely be displayed as “100 MB Healthy (Active, Primary Partition)” (Windows 8 will show “350 MB” for the size) and be located at the start of the drive, prior to the Windows partition.
  6. Click the Add button. An available drive letter will automatically be selected. You can keep it or select a different one. When finished, click the OK button.
  7. In this example, E: will be assigned to the System Reserved partition and c: is the Windows System Driv
  8. Start an Administrator mode Command Prompt
  9. Windows 8 only: Disable the Windows Recovery Environment (WinRE). Run the following command:
    1. reagentc /disable
  10. Verify that the winre.wim file was correctly moved to the C:\Windows\System32\Recovery folder by running the following command. You should see the file in the directory listing.
    1. dir /a C:\Windows\System32\Recovery
  11. This step is necessary because WinRE also needs to be moved from the System Reserved partition to the Windows partition. Leaving WinRE enabled will result in a broken/unusable WinRE after this procedure has completed. If the above command does not report success, you may need to manually copy the WinRE files (in the hidden \Recovery\{GUID} folder on the System Reserved partition) to an alternate location.
  12. Unload the BCD registry hive by running the following command:
    1. reg unload HKLM\BCD00000000
  13. Copy the bootmgr file from the System Reserved partition to the Windows partition. Run the following command:
    1. robocopy e:\ c:\ bootmgr
  14. Copy the Boot folder from the System Reserved partition to the Windows partition. Run the following command:
    1. robocopy e:\Boot C:\Boot /s
  15. The booting files have now been copied. If you wish to verify that they were copied correctly, run the following command:
    1. dir c:\ /ah
  16. If the bootmgr file and the Boot folder show up in the list, the procedure was successful.
  17. To update the copied BCD file so it will boot correctly, run the following command:
    1. bcdedit /store c:\boot\bcd /set {bootmgr} device partition=C:
  18. Update the Memory Diagnostic entry by running the following command:
    1. bcdedit /store c:\boot\bcd /set {memdiag} device partition=C:
  19. Close the Command Prompt window.
  20. Remove the drive letter assignment from the System Reserved partition and set the Windows partition as the Active partition.
  21. Return to Disk Management
  22. Remove the assigned Drive letter from the System Reserved partition
  23. Right-click on the Windows partition and select Mark Partition as Active from the pop-up menu.
  24. Click the Yes button to confirm the change. You should see the Active tag move from the System Reserved partition to the Windows partition.
  25. Close the Disk Management window.
  26. Windows 8 only: Enable the Windows Recovery Environment (WinRE). To do this, open an Administrator Command Prompt (if necessary, refer to instructions in Step 6) and run the following command:
    1. reagentc /enable
  27. Windows should now be configured to boot properly from its own partition. Restart the computer.

How to Safely Complete an In-Place Upgrade of the Core Server to Windows 2012

$
0
0

Affected Builds

AppAssure 5.3.x

Description

You want to do a safe in place upgrade of your AppAssure Core Server from Windows 2008R2 or earlier to Windows 2012.

Warning: AppAssure does not support PowerShell scripting. All scripts provided in this article are meant to be used as examples only. Click here for more information.

Solution

To achieve this please do the following. Note that all the command lines are executed from an elevated Powershell command prompt. First, run import-module appassurepowershellmodule to enable the AppAssure specific commandlets.

  1. Export the Core Registry Settings [HKLM\Software\AppRecovery] — This is just to be safe.
  2. Export the Core Repositories Settings [HKLM\Software\AppREcovery\Core\Repositories] — You will need this later.
  3. Suspend snapshots
    1. suspend-snapshot -all
  4. Suspend replication for Master (incoming) and Target (Outgoing) Cores
    1. suspend-replication -incoming <core-name>
    2. suspend-replication -outgoing <core-name>
  5. Make sure that there are no active jobs running on the core. If they are, stop them or wait for them to complete. Please be patient as some jobs take a long time to be cancelled.
    1. get-activejobs -all
  6. Disable the Core Service. You do not want it to start on its own if it does not stop properly
    1. set-service -name appassurecore -startuptype disabled
  7. Stop the AppAssure service
    1. stop-service appassurecore
  8. Delete the [HKLM\Software\AppREcovery\Core\Repositories] repositories registry key. You do not want the repositories to be improperly accessed during the upgrade.
    1. Proceed to the Windows in place upgrade.
  9. After the upgrade is successfully finished, do a Core Installation Repair from Control Panel -> Programs. This will set the core service back to delayed-autostart and start the core service.
  10. Check the Core using the GUI to make sure that it performs as expected.
  11. Stop the core service again. (It will stop graciously as no jobs are running and no repositories are attached).
    1. stop-service appassurecore
  12. Import the Repositories key back in the registry.
  13. Start the core service. Wait for the various checks, mounting and loading recovery points operations to finish.
  14. Re-enable replication.
    1. resume-replication -incoming <core-name>
    2. resume-replication -outgoing <core-name>
  15. Resume snapshots
    1. resume-snapshots -all

How to Get Replay to Recognize SQL on an Agent

$
0
0

Affected Builds

Replay 4.x

Description

SQL options like SQL log truncation and Attachability Check links on the Summary tab for the agent in the Replay core admin console are not available. Furthermore, there is no “SQL” tab with the options to select “Perform Full VSS SQL nightly backup” and “Perform a nightly attachability verification from the most recent recovery point”.

Resolution

Check on the following settings are completed for these options to appear on the Replay core admin console

  • SQL log truncation and Attachability Check
  • SQL tab with the options to select “Perform Full VSS SQL nightly backup” and “Perform a nightly attachability verification from the most recent recovery point”.
Complete the following steps.
  1. Confirm the Replay service account is configured on the agent service, which is found under the log-on tab of the Replay agent service
  2. Ensure that the Replay agent service account has a SQL account with sysadmin permissions to the SQL databases on the agent machine. If there is not one, then create a new SQL account (either using Windows authentication or a local SQL server account)
  3. Check on the agent in the Replay admin console. The “SQL” tab should appear with the options to select “Perform Full VSS SQL nightly backup” and “Perform a nightly attachability verification from the most recent recovery point”, and on the agent’s Summary tab, the SQL log truncation and Attachability Check links should now display.
  4. Now for the attachability checks to be performed during the nightly jobs, make sure a full instance of SQL Server (a version that is equal to or greater than the version that is running on the agent machine(s)) is installed with the same SQL account having sysadmin access.

VM ESXi Export Error Occurs When Running the Free Version of ESXi 5.1

$
0
0

Affected Builds

AppAssure 5.x

Description

The following error appears when attepmpting a VM export to a DR server. The DR server is running the free version of ESXi 5.1 but the VM guests that he is backing up reside on VSphere 5 Essentials Plus.

Appassure Core GUI error:
Error

The VM export for ‘mon-wellston’ failed due to the following error: Error calling createVM. – CreateVM for MON-WELLSTON_VM failed with System.Web.Services.Protocols.SoapException: Current license or ESXi version prohibits execution of the requested operation.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Vim25Api.VimService.CreateVM_Task(ManagedObjectReference _this, VirtualMachineConfigSpec config, ManagedObjectReference pool, ManagedObjectReference host)
at Appassure.Replay.VmwareEsxSoapApi.VmwareEsxVm.CreateVM()..

Solution

Typically this error is displayed when attempting to export to a host that is not running using the minimum license which API supports both read and write. Users need a minimum of a VSphere 5 Essentials license in place on the ESXi host. The following blurb offers more details:

vSphere API’s – Currently, the paid ESXi license allows read-write access to the VSphere API’s. The minimum license is the VMware vSphere 4.1 Essentials Kit for 3 host + 1 year subscription. ESX(i) Virtual Standby does not support the free version of ESXi because API’s are read-only on the free version and do not enable the creation VM’s on them.

VM Workstation Export of a Machine Running Windows 8.1 or Windows Server 2012 R2 Results in Blue Screen

$
0
0

Affected Builds

AppAssure 5.3.6.xxxxx

Introduction

This article describes a potential issue during VM exports of machines running Windows 8.1 or Windows Server 2012 R2 operating systems.

Description

Starting with the release of 5.3.6.xxxx, AppAssure now supports  Windows 8.1 and Windows Server 2012 R2 operating systems. For more information please refer  -   http://www.appassure.com/support/KB/windows-8-and-windows-server-2012-support/

However, an issue may occur while trying to perform a VM Export. VM exports of machines running Windows 8.1/Windows  2012 R2 operation system may result with the following blue screen on boot up:

Solution

You can resolve this issue by doing the following:

  • Locate the .vmx file of the exported machine, open it and make the following changes:
    • Locate the line scsi0.virtualDev = “lsilogic” and replace it with the scsi0.virtualDev = “lsisas1068″
    • Locate the line scsi0.pciSlotNumber = “21″ and replace it with the scsi0.pciSlotNumber = “160″
    • Ensure the following lines exists:
      • pciBridge0.present = “TRUE”
      • pciBridge0.pciSlotNumber = “17″
    • If not, add them.
    • Add the following lines:
      • pciBridge4.present = “TRUE”
      • pciBridge4.virtualDev = “pcieRootPort”
      • pciBridge4.functions = “8″
      • pciBridge5.present = “TRUE”
      • pciBridge5.virtualDev = “pcieRootPort”
      • pciBridge5.functions = “8″
      • pciBridge6.present = “TRUE”
      • pciBridge6.virtualDev = “pcieRootPort”
      • pciBridge6.functions = “8″
      • pciBridge7.present = “TRUE”
      • pciBridge7.virtualDev = “pcieRootPort”
      • pciBridge7.functions = “8″
      • pciBridge4.pciSlotNumber = “21″
      • pciBridge5.pciSlotNumber = “22″
      • pciBridge6.pciSlotNumber = “23″
      • pciBridge7.pciSlotNumber = “24″
  • Save the machine and then run it.
  • The machine should now boot up successfully.

Creating a Seed Drive When Replication is Already in Place

$
0
0

Affected Builds

AppAssure 5.x

Introduction

This article details the necessary steps to create a see when replication is already in place.

Description

If replication between the Source Core and Target Core takes too long to transfer, users can create a seed drive with replication in place. This allows you to transfer the recovery points to the Target Core in a faster process.

Solution

Complete the following steps.

On the Source Core

  • Open the Core Console.
  • Expand the Replication tab.
  • Click the arrow next to the outgoing Core name and find the agent in the drop down menu.
  • Check the agent box and hover over the tool box. Select Copy.
  • Select the location for the seed to copy and start the copy process.

NOTE: Pausing protection on all agents will help the seed process copy faster and cut down I/O failures.

On the Target Core

  • Insert the external drive used for seeding, if applicable.
  • Open the Core Console.
  • Expand the Replication tab.
  • Click the arrow next to the Core name and find the agent in the drop down menu.
  • Check the agent box and hover over the tool box. Select Consume.

NOTE: It is safe to resume protection on the Source Core at this point.


Cyclic Redundancy Check in AppAssure 5

$
0
0

Affected Builds

AppAssure 5.x

Description

The following error appears within the agent logs:

 

ERROR 2013-10-10T11:31:11 [52] – Replay.Agent.Implementation.Transfer.TransferDataChannel (RemoteEndPoint=10.10.0.35:64110)

Sending of volume data at byte offset 0xbbd06000, byte length 0×400000 failed

System.AggregateException: One or more errors occurred. —> Replay.Common.Contracts.Win32Api.Win32ApiFailedException: I/O operation  – Data error (cyclic redundancy check)

at Replay.Common.Implementation.Win32Api.NativeIOReader.EndTransmitFile(IAsyncResult asyncResult)

at Replay.Common.Implementation.Win32Api.NativeIOReader.<>c__DisplayClass4.<StartTransmitFile>b__3(IAsyncResult ar)

— End of inner exception stack trace —

at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)

at Replay.Agent.Implementation.Transfer.TransferDataChannel.SendVolumeDataResponse(INativeIOReader volume, UInt64 byteOffset, UInt64 byteLength, UInt64 zerosLength)

—> (Inner Exception #0) Replay.Common.Contracts.Win32Api.Win32ApiFailedException: I/O operation  – Data error (cyclic redundancy check)

at Replay.Common.Implementation.Win32Api.NativeIOReader.EndTransmitFile(IAsyncResult asyncResult)

at Replay.Common.Implementation.Win32Api.NativeIOReader.<>c__DisplayClass4.<StartTransmitFile>b__3(IAsyncResult ar)<—

Solution

Mainly the reason of this problem is issues with the disks.  Use the Windows Check Disk utility to check the hard drive for errors.

  • Open a command prompt and run checdisk by typing chkdsk /f.
    • NOTE: If an error message stating “The type of file system is NTFS. Cannot lock current drive. Chkdsk will not run because the volume is use by another process. Would you like to schedule the volume to be checked the next time the system restarts (y/n),” press Y and then press Enter. Restart your computer.
  • If the checkDisk shows some “bad sectors”, prepare backup copies for affected disks and use another disks instead.

Permissions Error during Attachability Check for SQL Server

$
0
0

Affected Builds

AppAssure 5

Description

Permission error during attachability check for SQL Server or during snapshots.

 

DEBUG 08/02/13 11:35:07 [1508] – Failed to determine if current logon account has required role membership: Failed to connect to any SQL Server instances: OLE DB Error Record dump for hr = 0x80040e4d

Row #: 0 Source: “Microsoft OLE DB Provider for SQL Server” Description: “Login failed for user ‘<domain-name>\appassure_service’.” Help File: “” Help Context: 0 GUID: {0C733A8B-2A1C-11CE-ADE5-00AA0044773D}

OLE DB Error Record dump end

- Error code 0x80040e4d

Src: DsmRpChecker

Ctx:

Solution

To resolve this issue, complete the following:

  • Make sure that user under which Replay Core service is running is SQL Administrator (if not add appropriate privileges for it within SQL Management Studio).
  • Restart Replay Core service.
  • Run check again.

CryptoLocker Virus Infection during Restore

$
0
0

Affected Builds

Replay 4.x

AppAssure 5.x

Description

When protected volumes are infected by the CryptoLocker vire, standard restoration methods (such as mounting recovery points or volume rollback) may not work.

The CryptoLocker virus encrypts all files contained within the network, making restoration difficult.

Solution

If paying the ransom for the decryption key is not an option, the following work around may resolve this issue (depending on the level of infection).

  • If the infection is contained, mount a safe recovery point and copy the desired files to a location not on the original volume. Once the needed files are restored and the infected files are deleted, copy the restored files back to the original location.
  • If the infection is wide spread, restore an entire volume. Prior to performing a rollback, format the existing volume. Once formatted, perform the roll back while ensuring “dismount” is selected. Users can:
    • Perform the rollback to a volume on another agent, or
    • Create a new server, add it to protection, and roll the volume(s) back to the new agent.

Using Mail Retriever for Exchange 2003

$
0
0

Affected Builds

Replay 4.x

Description

When trying to restore archived 2003 EX recovery points. A 32 bit version OS must be used, and you may encounter an error

Solution

To resolve this issue, complete the following steps.

  • Create a VM of Windows 2003
  • Install Exchange 2003, Outlook, and MR for Replay (a valid key is needed)
  • You must make sure all required dll’s are installed as well.
  • During the install process .Net 2.0 is installed which will provide and error when trying to restore the mailbox. .Net 3.5 is needed, to resolve this either update the .net or download the core installation and .net 3.5 will be installed be default.

After that, MR will function correctly.

Core Consumes Memory Due to Improper Dismounts of Recovery Points

$
0
0

Affected Builds

AppAssure 5.3.1.60393

Description

This article describes an issue where the core service may consume large amounts of memory due to improper dismounting of recovery points.  In rare conditions during the mount/dismount operations, the memory may not be released correctly.

Solution

This defect is resolved in release 5.3.5.64611. Upgrade the core to release build 5.3.5.64611.

AAmount Error “Replay.Common.Contracts.TevoLib.TevoLibraryErrorException.” on a Linux Machine

$
0
0

Affected Builds

AppAssure 5.3.x

Description

Error:

(AppAssure mount) mount 4 1 a /mnt

Getting volume details from server…
Attaching to local block device …
Exception of type: Replay.Common.Contracts.TevoLib.TevoLibraryErrorException. See log for details.

Solution

Check/send the following:

  • Make sure port 8007 is open on the core and agent. AAVdisk driver uses this port to mount the partitions.
  • Disable UAC on the core machine: “Control Panel”>”User Accounts”>”Change User Account Control Settings” Set this to “Never Notify” (This will normally pompt for a reboot)
  • start>run>secpol.msc
  • Local Policies>Security Options
  • “User Account Control: Run All Administrators in Admin Approval Mode” – set to disabled
  • “User Account Control: Only elevate UIAccess Applications that are installed in secure locations” – set to disabled
  • Reboot your core if if you did not after disabling UAC.
  • Also check that you are using the local Administrator account and not a Domain Administrator. (Be sure you use “Administrator” in the username field and not “COMPUTER\Administrator”.)
  • If you are using the 5.3.1 agent and the core is Server 2012 then you will need to upgrade to 5.3.2 or higher for the agent (Which may require you to upgrade your core as well)

Doc Retriever Configuration Information and Usage links

$
0
0

Affected Builds

Replay 4.x

Description

The following information and links is to help with the terminology and configuration steps when installing and using Doc Retriever for SQL and Sharepoint in a Replay 4 environment

Solution

Below is information on how the Doc Retriever configuration should be handled.

  • Protection front-end / back-end SharePoint config
    • The front-end server (SharePoint) where the data is being presented to the customer.
    • The back-end server (SQL) where the databases reside.
    • Protect both servers; when you want to perform a restore you would mount a recovery point from the backend server. Open DR and point it to the Content DB you would like to restore from. The data is then presented to you in DR. You then choose what you want to restore and authenticate with the Frontend server and then start the restore process in place or out of place.
  • Granular restores RE: SharePoint docs, tables etc.
    • Regarding restores for SharePoint and the process to setup Doc Retriever in a SharePoint configuration.

The following links offer information on the installation / setup for Doc Retriever and the restore process for SharePoint whether its a file, site or doc level restore.

  • Install and configuration of Doc Retriever
    • http://docretriever.s3.amazonaws.com/DocRetriever%20for%20SharePoint%20Install%20Guide%202.0.pdf
  • Restoring via Doc Retriever
    • http://www.appassure.com/downloads/Recovering-SharePoint-Objects-with-DocRetriever.pdf

Rollup Fails to Process All the Recovery Points

$
0
0

Affected Builds

Replay4xxx (All Builds)

Description

Either the nightly job runs which includes the Rollup Process or the user manually starts the rollup to process a new retention. When the rollup / retention is processed the end result may not include all the recovery points that are outside the retention policy you have configured. I have included the following info which explains this behavior as well I have included some solutions to these issues.

Solution

If there were snapshots taken at some point that did not include all the protected volumes these recovery points may not be included in the rollup process because they fall under the “broken protection group” status. I have included the following link that explains this behavior:

http://www.appassure.com/support/KB/4130413/

If there are multiple base images then the retention will only apply to the most recent chain which will be the most recent base image to the most recent incremental snapshot. When this occurs you can use the Cleanup option which will allow you to remove older base images and the incremental snaps that are associated with that base image. When you click on an agent in the console the agent summary is displayed. Click on the recovery points tab which will display all the recovery points for that agent. To the top right of the window you will see the Cleanup button. Once you have clicked the cleanup button you will be presented with a list of the base images that are associated to this agent. You can click on the base image that you want to KEEP and then the cleanup will remove the older base images and incremental snaps but NOT the base image you selected. I’ve included the link below which provides a screenshot of the cleanup option which is on page 151 of the guide below.

http://www.appassure.com/wp-content/uploads/2009/12/Backup-Admin-Guide-2nd-Edition.pdf

How to Delete the Dedupe Cache in AppAssure

$
0
0

Affected Builds

AppAssure 5.x

Description

This article contains instructions on how to delete the dedupe cache in AppAssure.

Solution

Below are the steps to delete the dedupe cache in AppAssure:

Warning: Dell recommends completing the following steps with the help of an AppAssure Support engineer to prevent any damage to the environment.

  1. Stop the Core Service.
  2. Make sure that there are no active jobs running then stop the Core service.
  3. On the Core server browse to C:\ProgramData\AppRecovery\RepositoryMetaData.
  4. Delete the content (not the folders) of PrimaryCache and SecondaryCache folders.
  5. Start the Core service.

Install of Agent Software AppAssure Agent Service Will Not Start

$
0
0

Affected Builds

AppAssure 5.3.x

Description

Upon installing the agent software on a given machine the install proceeds without error but when trying to start the Appassure Agent Service the following error message is thrown:

” Windows could not start the Appassure agent service on local computer
Error 1068: The dependency service or group failed to start”

The cause of this can be that the Appassure Agent Service depends upon 2 other services running or starting properly first the “Base Filtering Engine Service” as well as the “IPsec Policy Agent service” On the agent server Operating System browse to and check the Windows Event viewer system log file entries. Specifically look for Error Event ID 7001 Service Control Manager errors. These errors will reference Base Filtering engine service not starting or access denied and look for same type of error for the IPsec Policy Agent service.

Solution

Please reference the following possible solution via Microsoft Tech Net Post below to resolve issue:

http://blogs.technet.com/b/rspitz/archive/2010/09/19/quot-access-is-denied-quot-when-you-attempt-to-start-the-base-filtering-engine-service-after-upgrading-from-windows-server-2003-to-windows-server-2008-r2.aspx

 

How to Create a Missing System Reserve Partition (SRP)

$
0
0

Affected Builds

AppAssure 5.3.x

Description

You have omitted protected the SRP partition of your AppAssure protected Windows 2008R2 or later agent. You are forced to do a BMR or a Virtual Export. The recovery operation goes well but the exported machine does not boot. You need to find a way to quickly re-create the SRP

Resolution

To recreate the SRP:

  1. boot from a WinRE environment (Windows Install Disk would also work), navigate through the various menus to get to a Command Prompt option. Open a DOS Command Prompt.
  2. Run DiskPart.
  3. At the DiskPart prompt type:
    1. list volume
    2. Note that the SRP partition has actually been created but it is reported as unformatted.
  4. Make note of the drive letter for:
    1. the SRP (which is shown as a raw partition)
    2. the system volume (contains the Windows OS)
    3. the CD you have used to boot.
  5. For the following we assume that the SRP is shown as C:, the System Volume as F: and the CD Drive as G:
  6. Identify the disk containing the SRP & the OS by running list disk and guiding yourself by the size of the drives. We assume that it is disk 0
  7. Run
    1. Select Disk 0
    2. List partition
  8. Identify the number of the SRP partition (it should be 1) and select it running
  9. select partition 1
  10. Format the SRP
    1. format fs=NTFS label=”SRP”
  11. Set the SRP Partition as active by running
    1. Active
    2. (Note that it is marked with an * now, when running list partition)
  12. Exit DiskPart
  13. Change the focus from X: (the default) on the SRP partition (c:) by running:
    1. c:
  14. create a folder called Boot Mkdir Boot
  15. Copy the content of the boot folder on the system partition (F:) to the new folder.
    1. xcopy c:\windows\system32\boot c:\boot /e /h
  16. Copy the bootmgr from the root of the CD (g:\)
    1. copy g:\bootmgr
  17. Change the focus back to drive X: and change the location to x:\sources\recovery
    1. X:
    2. cd \sources\recovery
  18. Run startrep
    1. Startrep
  19. Reboot — your machine; it should boot all the way now.
    1. Note: In some rare instances you need to redo the boot sector (i.e., for an mbr drive, bootsect /nt60 ALL /force /mbr)

Copy (Seed) and Consume in Replay 4

$
0
0

Affected Builds

Replay 4.x

Description

This article details the steps necessary to copy (commonly known as seed) and consume a drive in Replay 4.

Solution

Complete the following steps. Note that rollup should be disabled throughout the seed process.

  1. Use the Admin Console to configure replication for each protected server on the Core using the assigned Target Core hostname and credentials.
    1. NOTE: Ensure that the “Pause replication on the protected server” box is checked when configured replication.
  2. Connect to the Core using the Admin Console.
    1. Open the Admin Console and select File.
    2. Select Connect to Core and enter the remote hostname and credentials.
  3. Use the Admin Console to disable rollup for all of the agents that are having their data copied. You must do this on both the Source Core and Target Core using the Admin Console (you can login to the Target Core by using the File menu, connect to a Replay CORE command in the Admin Console). To disable rollup, right click each server, choose properties, go to the Retention tab, and uncheck Rollup. Rollup must remain disabled until the data has been fully consumed in the remote data center and Replay indicates that both sides are fully synchronized.
    1. NOTE: Failure to properly follow this step may cause the seed process to fail and subsequently start over. Please disable rollup.
  4. Perform a copy operation.
    1. Open the Admin Console and expand the Core status pane.
    2. Expand the Replication, select one or more servers, and click Copy to copy the initial seed data to the disk or NAS device.
  5. Send the disk to the Target Core location and connect the seed disk.
  6. Highlight the agent that is being seeded and click Consume to begin the consume process.
  7. Use the Admin Console to connect to the Source Core and resume replication.
  8. At this point, Replay may take a significant amount of time to commit the recovery points from the replication staging area to the repository. The length of time is dependent upon the amount of data, as the software will verify the checksums of the data to ensure no data was corrupted while on drive. This can take several days or longer for large amounts of data (hundreds of GBs or TBs). Once this completes, Replay will then upload recovery points from the Source Core to the Target Core. Once completed, the Replay Admin Console will show a synchronized status with both sides in sync.
  9. Do not re-enable rollup on either the Source or Target Core(s) until replication for each agent is synchronized. Once the Admin Console reports that replication is synchronized, login to both the Source and Target Core and enable rollup for each server that was seeded.
    1. Right click the Server and select Properties.
    2. Open the Retention tab.
Viewing all 587 articles
Browse latest View live