So, we have a 5200 appliance and windows master in one domain, and a 5220 acting as its own master in another.
Using Storage Lifecycle Policies, we are replicating between the 5200 and 5220. Seems to be working OK, but the data is travelling on our regular IP network. And we'd like to move the 5220 to another building for added protection.
We were told you cannot directly connect the 5200 and 5220, say, through fibre or some such, so, how are other folks handling this?
Do bear in mind that these are de-dupe units and communicate directly to each other - they will only send data that is not already in their own fingerprint database so it will not re-hydrate or anything - just send optimised de-dupe data across the link
I have one customer replicating their Hong Kong backups back to London and that is fine!
Bonding the 2 nics would be nice but see how it goes on just one - you can push a fair bit of de-dupe over a 1g network!
If you want it to use a different network then configure a second network and IP address on the appliances for the replication traffic and then make sure they can only resolve each other via that network - they talk to each other directly when doing this so it is only the appliances that need such a network
There is also an option when you have this setup to go to the http://appliance/install page to select the backup and replication networks but it is not really needed it you do it all through hosts files
So, confused... you're saying "build a separate private network" for replication traffic, and control via hosts files?
Don't have another nic, they're all bonded for maximum throughput.. and it's me, i'm sure, but would have no idea how to "force" one kind of traffic over one IP vs the other.
Mark is saying if you want to keep your backup traffic off the production network, then you need to have a different network for the traffic to traverse. This is typically done with separate network switches and different IP subnets than what you are using today so that the traffic is completely separated.
Yes - that is what i was saying - to split traffic you need to remove at least one network interface from your bond and set it up as a independant interface for replication traffic
You cannot have 2 IP addresses on the same card so to split traffice that would be your only option
Okay, sorry for the delay in responding.. had another NetBackup appliance crisis and excitement and EEB. But that's a story for another day.
THANKS, now i got it, split traffic, dual network these guys.
Don't have a clue how to do that, prolly should, but don't. That "http://appliance/install" isn't the regular 5200/5220 gui, right? You mean when you plug in your laptop to the configuration port?
Had my networking guy in to help access the situation, and on both boxes he spied the two fibre ports next to the ethernet connections. Wants to use them to run to the switch, and segment replication traffic that way.
When I looked at the gui, it had uses for those fibre ports, but in the appliance reconfiguration portion of the settings, which did have a tab for fibre transport, the choices were:
Enable the SAN Client FT media server [Fibre Transport for backups to this appliance]
can I use one of those options to configure a separate network connection to my switch? If so, how do i tell it to send replication traffic over it?
No, those are Fibre Channel HBA cards, not network cards. You *can* order them with both 10Gb network cards and the FC HBA cards. One way to tell absolutely sure is to go into the CLISH (command line shell), change to the Network menu and run the show status command. You'll get an output like this:
You can see above that eth6 and eth7 are 10Gb. If you don't see these, then you don't have them installed and can't use them for ethernet networks. You can order them if you want, but if you aren't going to use more than 1Gb of bandwidth, or don't have 10Gb switches, then there's no need.
Do this on each appliance specifying the IP address, subnet and gateway you have for it on the backup LAN.
Next just edit its hosts file (either using vi in the O/S or the hosts section in the CLISH) and add an entry for the other appliance on the backup network.
Do this on each appliance and from now on they resolve and talk over the backup network - no need to worry about a different name or anything they will just talk
If you need 2 ports bonded then you will need to unconfigure eth0 fir st and also remove one from the bond on 5220r so that you can then bond eth0 and eth1
Do bear in mind that these are de-dupe units and communicate directly to each other - they will only send data that is not already in their own fingerprint database so it will not re-hydrate or anything - just send optimised de-dupe data across the link
I have one customer replicating their Hong Kong backups back to London and that is fine!
Bonding the 2 nics would be nice but see how it goes on just one - you can push a fair bit of de-dupe over a 1g network!
OH that's good to know also.. Didn't have a firm grasp on how much data actually got passed.. We should be fine, I agree. It's only across the street :)
Glad you are sorted now - it is a shame that you cannot use firbre for AIR / Opttimised Duplication.
The odd thing is that you can use Fibre transport for AIR from a 5020 to a 5020 or 5220 to a 5020 but not a 5220 to a 5220 - maybe it will come in the future?
