Importing backup to disk storage

[escoba]

Hello,

I copied backed up data from External disk "A"  to External disk "B".

The backup in Disk "A" was carried out using backup exec 2012 using the disk storage option.

Disk "B" is and external hard disk with no disk storage created onto it. I wanted to make acopy of the data backedup onto disk "A"

I copied the following folders;

BEControl

BEData

How can I read this data from disk "B" using Backup Exec?

[CraigV]

Hi,

Don't do a manual copy at all...you'll mess up the catalogs on the second disk.

Create another stage in the job cycle to duplicate your data to the second drive rather...this keeps catalogs etc. intact, so if you ever need to restore from the 2nd drive you won't run into any issues.

Thanks!

[pkh]

You should not copy the BEControl and BEData directories.  What you need to do is to plug your Disk B into the media server and define storage on Disk B.  After that, in the Storage tab, click on the storage defined on Disk A and click on backup sets, and duplicate them to Disk B.

[escoba]

CraigV

As of now I have already done the manual copy, Is there any way I can catalog this other disk?

The backup takes quiet a long time about 24hours (2TB) of data, any options?

[escoba]

pkh

How long would the duplicating take?

[CraigV]

...delete the copy as it is going to become useless in the event of a restore and duplicate as mentioned above.

You can do this over a weekend if need be.

[pkh]

It is almost like a copy, except that BE will be cataloging the duplicated backup set so that you can use it. It should not take as long as the backup.

[escoba · Accepted solution]

I later worked it out throgh rebiulding the *.xml file in disk "B" and matching the Name of Hard Disk "A" with Hard Disk "B"

Therefore its now detected as the Original Disk Storage that was created in "A"

Atleast the restoring worked fine, so I believe even the data is consistent.

The rebiult xml file:

<?xml version="1.0"?>

<controlFile><!--Backup Exec Storage Control File--><version>1.02</version><parentGuid>74ae5a1e-ba04-4632-9d5a-92f56be03f12</parentGuid><machineGuid>e0e189e1-0935-4616-bd8c-0b2ae86ab730</machineGuid><virtualDiskGuid>c6a46eaf-74a5-4c34-82e2-66f62743e3c5</virtualDiskGuid><osVolumePath>\\?\Volume{3c2e4f43-662b-11e1-ba64-782bcb2a157a}</osVolumePath><volumeSignature>00000000-0000-0000-0000-000000000000</volumeSignature><isDeleted>0</isDeleted><storageRole>0000</storageRole><storageOwner>00000000-0000-0000-0000-000000000000</storageOwner><storageOwnerName>&amp;nbsp;</storageOwnerName><isSelfContained>1</isSelfContained><dataPaths><path

id="85c6e338-a28c-48b8-8b90-6e4e9e6ff167">\BEData\</path>

</dataPaths><containerGuid>85c6e338-a28c-48b8-8b90-6e4e9e6ff167

</containerGuid><isLocalDisk>1</isLocalDisk><isRemovable>0</isRemovable></controlFile>

[CraigV]

...you're doing things the wrong way around to short-cut doing it properly. If you're not going to follow Symantec's recommendation to duplicate the B2D files, then you're going to run into issues somewhere along the line.