Copy from Copy

[b.vanhaastrecht]

Hi,

In a setup like:
BCK01 Server: Tier1: Local Repository
BCK02 Server: Tier2: Remote Site - Local Repository
BCK02 Server: Tier3: Remote Site - Dedupped (DataDomain) Repository

With v8 it should be posible to set a copy job's repository as the source for another copy job. We've setup the Tier2 repository as source for a DD-Boost enabled copy job to Tier3. When this copy job runs (it the first time) I see traffic flowing from BCK01 to the agent running on BCK02 server, and he puts it on Tier3. According to the feature enhancement I expected to see no traffic between the two BCK servers, and see traffic only from BCK02 to the DataDomain.

Is this feature enhancement not suited for use in conjunction with DD-Boost?

Kind Regards
Bastiaan

[NightBird]

Who is your gateway server (for ddboost), I think it is BCK01.
Try to set it to BCK02

[b.vanhaastrecht]

Who is your gateway server (for ddboost), I think it is BCK01.
Try to set it to BCK02

Hi, nope, thats not it. It's already set to BCK02.

[foggy]

Bastiaan, how the "BCK02 Server: Tier2: Remote Site - Local Repository" repository is added to Veeam B&R console? CIFS share by any chance?

[b.vanhaastrecht]

Bastiaan, how the "BCK02 Server: Tier2: Remote Site - Local Repository" repository is added to Veeam B&R console? CIFS share by any chance?

Hi Alexander, both Tier1 and Tier2 are of type Windows, they are added as Windows Servers local disks.

[foggy]

Then I suggest to take assistance of our technical team to verify your configuration.

[b.vanhaastrecht]

Ok, I created a ticket: #00690900

[b.vanhaastrecht]

I'm finished with support on this. It took a long while to get to the point were we are now. All in all, it came down to this:

Copy from Copy as source is supported, but there are some non documented catchas.
- The use of DataDomain has no influence in this feature
- You must set a fixed source repository, the source which containts the first copy
- You can't use "from jobs" as your VM selection list, as this does not follow the fixed source repository setting (no error message given if you got fixed source set)
- You must use "from backups", or "from infrastructure", this does follow the fixed repository setting
- Keep in mind that Copy from Copy requires the parent copy to be finished with transmitting and merging before the child copy can start

Together with level 2 we've created two feature requests:
- document the use of Copy from Copy as source
- make it posible to use "from jobs" as VM list, as this is THE best way to push the sames backupped VM's to the copy job. "from infrastructure" has one big disadvantage. A VM isnt processed if it's removed from the infrastructure between copy's. And, "from backup" isn't dynamic.

[foggy]

Looks like you've used the original backup job as a source and tried to limit the scope by selecting the particular repository, however, this setting indeed ignores the scope (as it is defined by the source backup job itself). That's why data was retrieved from the original backup job repository.

Thanks for getting back.