I'm not BE knowledgeable so bare with me, but top of my head:
- when you say duplicated to DD on other side I assume you mean replicated from site 1 to site 2, right?
- I assume this is automated job. What happens if you run the job without replication enabled and then you kick replication of the job on site 1 (DD1) to site 2 (DD2)? Do you still see the same?
- when you query BE for these 3 backup sets (and normally I would assume there should be 3 backups sets all coming from the same job as each VM or source should be one backup set), what does it say for it? In my view, at least when working with other backup applications, I would expect to see 3 backup sets on site 1 as well.
Yes, this is a duplica in fact. In BE you can do a policy that said: after the backup is finished, duplicate the media to another storage.
Customer will test the duplication without a policy. I am awaiting for some results
Query = No restore possible and a wonderful message saying that the media has been erased
The backup set/media set looks like that
So, if there is one media/ backup set containing one backed up source, the duplicate is OK. If there is one media/backup set containing more backed up sources, it will create from one media/backup set, the number of backed up sources at the destination. Means: 1 media/backup set with 3 sources = 3 duplicated backup/media set at the destination.
I don't believe this is soething normal. I should have 1 media set at the end or same amount the backup job used (if 4 are used, I should see 4 on the destination DD).
I would assume key is in communication between BE and DD Boost API and where does it break is really hard for me to say from here. I assume you will need ticket with Symantec to check configuration and confirm all done is as it should be done. Most likely some debug will be needed to check what happens beneath and based on that engineers will know where to look next.
ble1
4 Operator
•
14.4K Posts
0
May 14th, 2014 06:00
I'm not BE knowledgeable so bare with me, but top of my head:
- when you say duplicated to DD on other side I assume you mean replicated from site 1 to site 2, right?
- I assume this is automated job. What happens if you run the job without replication enabled and then you kick replication of the job on site 1 (DD1) to site 2 (DD2)? Do you still see the same?
- when you query BE for these 3 backup sets (and normally I would assume there should be 3 backups sets all coming from the same job as each VM or source should be one backup set), what does it say for it? In my view, at least when working with other backup applications, I would expect to see 3 backup sets on site 1 as well.
Do you also have ticket with Symantec?
olivier_cesar1
1 Rookie
•
31 Posts
0
May 15th, 2014 05:00
Hello Hrvoje,
Here are some answers to your questions:
The backup set/media set looks like that
So, if there is one media/ backup set containing one backed up source, the duplicate is OK. If there is one media/backup set containing more backed up sources, it will create from one media/backup set, the number of backed up sources at the destination. Means: 1 media/backup set with 3 sources = 3 duplicated backup/media set at the destination.
I don't believe this is soething normal. I should have 1 media set at the end or same amount the backup job used (if 4 are used, I should see 4 on the destination DD).
Voilà :-)
ble1
4 Operator
•
14.4K Posts
0
May 15th, 2014 05:00
I would assume key is in communication between BE and DD Boost API and where does it break is really hard for me to say from here. I assume you will need ticket with Symantec to check configuration and confirm all done is as it should be done. Most likely some debug will be needed to check what happens beneath and based on that engineers will know where to look next.