I take manual backups regularly, but also use rancid with a git backend. Which then triggers a push to our gitlab repo.
This saves both the tree and command output for easy re-use. It's also very handy to browse diffs and then push back out. (am testing semi-automated pushes)
Many times I may just ssh into one ER, issue show configuration commands, copy, then edit/paste into a new router. I like that method as I can issue a confirm to ensure I don't lock myself out of the remote ER an hour away..
Dpurgert also makes some good points with scp/load.
This saves both the tree and command output for easy re-use. It's also very handy to browse diffs and then push back out. (am testing semi-automated pushes)
Many times I may just ssh into one ER, issue show configuration commands, copy, then edit/paste into a new router. I like that method as I can issue a confirm to ensure I don't lock myself out of the remote ER an hour away..
Dpurgert also makes some good points with scp/load.