NetWorker

Last reply by 10-05-2022 Solved
Start a Discussion
2 Bronze
2 Bronze
215

avmar with datadomain

why Avamar backup server integrated with data domain?

Solution (1)

Accepted Solutions
3 Argentum
210

Sorry is that even a question? And in the Networker community nonetheless?

Better asked in the Avamar or Datadomain community?

Ourselves had Avamar in a few Networker environments, years ago. Project showed that Avamar as a backup product at the time did not support wide range enough of applications and OS'es, hence Avamar was not going to be used as backup product, but only as deduplication appliance to have Networker backup towards. However as we also had DataDomain already in other environments, DD was deemed better suited with use of NW than Avamar ever could (*).

Avamar however was - at the time at least - way better suited for automation through REST API's, something NW actually got through the BM&R appliance at the time, something that came from Avamar. Also the older NW VDP vmware solution was actually avamar under the hood, stroing metadata on the appliance. Even more recent NW vproxy appliances are actually Avamar systems, same goes for NW NVE (virtual edition). Still a lot of Avamar references to be found on those Suse-based systems. SO also good things came from Avamar, however we did not have that good a experience with Avamar as backup target for NW, so now we only have DD as backup target, which works very well...

It is however also a sign on the wall, that Avamar itself nowadays also uses DD as a backup target, instead of its own dedupe technology/storage...

(*) some Avamar drawbacks (at least at the time with NW):
- having to take into account the black out window where it performed its housekeeping so no backup activities should be occurring
- if something is the matter needing to go back to an earlier - let's call it - snapshot as corruption occurred on avamar, then NW will not be able to scan in any data from later backups than the moment that was restored to. So that means actual data-loss. The cause at the time was an incorrect NTP occurring due to which some had problems needing to go to an earlier snapshot time.
- needing EMC support to perform updates
- replication between avamar systems was completely outside of the awareness of NW, unlike is the case with cloning between DD's were NW is aware and fully in control.

-----------------------------------------------------------------------------------------------------------------
Not a Dell employee. Just doing this to try to help out others. Sharing with the community.
-----------------------------------------------------------------------------------------------------------------

View solution in original post

Reply (1)
3 Argentum
211

Sorry is that even a question? And in the Networker community nonetheless?

Better asked in the Avamar or Datadomain community?

Ourselves had Avamar in a few Networker environments, years ago. Project showed that Avamar as a backup product at the time did not support wide range enough of applications and OS'es, hence Avamar was not going to be used as backup product, but only as deduplication appliance to have Networker backup towards. However as we also had DataDomain already in other environments, DD was deemed better suited with use of NW than Avamar ever could (*).

Avamar however was - at the time at least - way better suited for automation through REST API's, something NW actually got through the BM&R appliance at the time, something that came from Avamar. Also the older NW VDP vmware solution was actually avamar under the hood, stroing metadata on the appliance. Even more recent NW vproxy appliances are actually Avamar systems, same goes for NW NVE (virtual edition). Still a lot of Avamar references to be found on those Suse-based systems. SO also good things came from Avamar, however we did not have that good a experience with Avamar as backup target for NW, so now we only have DD as backup target, which works very well...

It is however also a sign on the wall, that Avamar itself nowadays also uses DD as a backup target, instead of its own dedupe technology/storage...

(*) some Avamar drawbacks (at least at the time with NW):
- having to take into account the black out window where it performed its housekeeping so no backup activities should be occurring
- if something is the matter needing to go back to an earlier - let's call it - snapshot as corruption occurred on avamar, then NW will not be able to scan in any data from later backups than the moment that was restored to. So that means actual data-loss. The cause at the time was an incorrect NTP occurring due to which some had problems needing to go to an earlier snapshot time.
- needing EMC support to perform updates
- replication between avamar systems was completely outside of the awareness of NW, unlike is the case with cloning between DD's were NW is aware and fully in control.

-----------------------------------------------------------------------------------------------------------------
Not a Dell employee. Just doing this to try to help out others. Sharing with the community.
-----------------------------------------------------------------------------------------------------------------
Latest Solutions
Top Contributor