kmbay

updated

9 years ago

K

kmbay

1 Rookie

61 Posts

0

7882

May 1st, 2017 10:00

How to Backup NetApp NAS

We are moving to a new building and we are getting a NetApp FAS2650 to be our file system. We will not have any VMware there and no fiber connections. This NetApp is a NAS using Ethernet connections - we will have CIFS, file quotas, etc.

Our Avamar 7.2.1 is in our other datacenter location (currently backing up all our VMs, filesystems and databases). How can I back up this new NetApp FAS2650 with Avamar? Is this a plug in or a different connection?

Thank you.

  • ionthegeek

    2 Intern

    2049 Posts

    5117

    0

    Posted May 1st, 2017 11:00

    Generally speaking, an Avamar NDMP accelerator node is required to back up a NAS device. I recommend discussing this with your Dell EMC account team so they can help with sizing, etc.. NAS devices often need special consideration since the backups tend to be quite large. This can have ripple effects on capacity but also on things like maintenance since initial backups of NAS devices may take significant time, depending how much data needs to be backed up.

    The accelerator node should be installed as close to the NAS device as possible. If the backups will be running over a WAN, it might be necessary to perform some tuning to ensure good performance, particularly if the link has high latency.

  • Ryan_Johnson

    1 Rookie

    73 Posts

    1606

    2

    Posted May 12th, 2017 13:00

    I have experience backing up data over WAN with and without data domains. There are a lot of things that can impact performance many of them already mentioned.  In general Avamar with or without data domain will more more effective over the WAN than other backup solutions.  One thing I haven't seen mentioned yet for consideration is restore speeds.  With Avamar oftentimes in a night you can backup several TB of data over 50 mbps WAN connection but restoring all the data will take significantly longer than backup times.  Restoring 1 TB at 50 mbps will take about 2 days.  There is an option to add compression during restore which would help but it will pretty much always take longer than a local restore.


    If a large amount of data needs to be restored it might save time to restore to a different client at the primary data center and transport a portable device between sites.  There are little details that could possibly end up being a big deal though.  Like you can't really do that with a DB restore, Windows BMR or you might loose NDMP ACLs.

  • Mildur

    12 Posts

    5117

    0

    Posted May 1st, 2017 11:00

    You have to use avamar ndmp accelerator Node for this scenario.

  • kmbay

    1 Rookie

    61 Posts

    5116

    0

    Posted May 1st, 2017 12:00

    Thank you Ian!

    Is the NDMP appliance an easy set up? It has to be physical in our non-VM building.

  • ionthegeek

    2 Intern

    2049 Posts

    5117

    1

    Posted May 1st, 2017 12:00

    My pleasure!

    Setup is reasonably straightforward but I think the procedure might be restricted to employees and partners. Your account team should be able to tell you for sure.

  • 3400

    0

    Posted May 2nd, 2017 22:00

    you have use NDMP accelerator for NAS backup in avamar.

    for more about NDMP configuration, please go through below link

    https://www.emc.com/collateral/software/white-papers/h8235-avamar-nas-ndmp-wp.pdf

  • ionthegeek

    2 Intern

    2049 Posts

    5126

    0

    Posted May 8th, 2017 07:00

    You shouldn't need a back-end capacity license for an accelerator node since it doesn't store any data itself.

    The options you were sent are all storage nodes. None of these are the node type you need. The node type you're looking for is "Avamar Gen4S Accelerator Node" or "Avamar Gen4T Accelerator Node".

  • kmbay

    1 Rookie

    61 Posts

    5117

    0

    Posted May 8th, 2017 07:00

    How do I determine the Back End Capacity License for Avamar Data Store (TB)? Is this via command mccli server show-prop? If so I'm showing Total Capacity 3.9 TB.

    When requesting a quote for the NDMP Accelerator Node, I was also asked which node type I'm looking for.

    I'm not sure but they did send several options (can you provide any guidance here?):

    M600 (2.0 TB licensed capacity) l Six 3.5” hard drives l Dual 750W power supplies l Eight 10/100/1000baseT GbE ports l RMM4 management port

    M1200 (3.9 TB licensed capacity) l Six 3.5” hard drives l Dual 750W power supplies l Eight 10/100/1000baseT GbE ports l RMM4 management port

    M2400 (7.8 TB licensed capacity) l Twelve 3.5” hard drives l One 2.5” SSD drive (internal mounting) l Dual 750W power supplies l Eight 10/100/1000baseT GbE ports l RMM4 management port

  • kmbay

    1 Rookie

    61 Posts

    5126

    0

    Posted May 12th, 2017 07:00

    Thank you Ian, you are always most helpful. I have one more thing to bother you with if I may.

    In this new datacenter with our NetApp FAS2650 and Accelerator Node which will connect back to our Avamar and DD in our other Datacenter (states away) for backups, we will also have about 5 physical servers that would need to be backed up. I'm assuming in order to back up these physical servers in this new datacenter we will require an Avamar Node there as well, to connect over the WAN and store those backups on our main DD. Is that correct? This new datacenter will be all physical, nothing virtual.

  • ionthegeek

    2 Intern

    2049 Posts

    5126

    0

    Posted May 12th, 2017 08:00

    Happy to help!

    With regard to backing up over a WAN, I don't think there would be a lot of benefit to having an Avamar node on-site if the backups are going to the DD across the WAN anyway. Data Domain is much more sensitive to WAN latency than Avamar and the amount of data being sent to the Avamar will be several orders of magnitude less than the amount of data being sent to the DD.

    If it's a sizable remote site with a high latency WAN connection back to the main site, backing up to a small on-site Avamar and DD and replicating to the main site may significantly improve performance but if the number and size of systems at the remote site is low, it may not be worth the investment.