• State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 28 subscribers
  • Views 4069 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Best way to migrate archive recovery points from 5.6 to 6.0 format to enable "archive attach"

chris
over 7 years ago

Hi

We have about 8TB of archives that we want to migrate to stick in Azure blob storage for long-term storage that have come out of Appassure 5.6, currently sat they are in 1TB(ish) chunks on external HDDs what is the best way get these converted over to the 6.0 format to allow the use of the new archive attachment function as opposed to having to pull the full data into the local repository to be able to mount it? Is the only way to build a 6.0 core, load each archive up into the local repository and then offload reachive it and upload it to Azure. We have build a "recovery console" in Azure to pull the content back from the blob storage and that seem to work great - just as long as you don't have to upload 1TB+ of data first. Is the most efficient way to do this going to be load all known the recovery points back for a given VM and then archive it all up again in the hope it de-dupes.

Chris

  • 0 over 7 years ago
    Hi Chris:
    If I understand correctly you have 8TB of local archive data divided in 1TB chunks. You want to store the data on Azure in the new 6.0.x archive format which allows mounting archives as read-only repositories.

    Unfortunately there is no direct 5.4.x - 6.0.x archive conversion mode.

    To achieve your goal, I would create a temporary local 6.0.x core -- a VM would do -- with appropriate storage, import the local archive and export to blob storage on Azure.

    Since you have historical data (and as such some timing leeway) if the storage for the temp core is a constraint, you should be able to set the size of the repository so it is able to accommodate only the largest machine in the archive. After the machine is imported, you can archive it in the Azure cloud using the INCREMENTAL option, delete the repository and dedupe cache, re-create both and move to the next archived machine(s). If you have several smaller machines, you can import/archive them together to reduce the number of steps.

    The result will be one archive with multiple increments, each increment containing the recovery points of one (or more) machines. The archive will be mountable either on a Core in the Azure Cloud or even on a core at your location. This is a good solution if you need to do a small file restore rather than a full volume.

    Although you may lose some of the dedupe ratio, I know from experience that, in most cases, this would not be significant.

    Hope that this helps.