01 · Starting point
Situation
Network performance, reliability, security and data backup had to be improved together. Routers, switches, firewalls and backup jobs formed one connected operating landscape.
Constraints
- Changes within an already established IT environment
- Short, clearly scoped engagement
- Internal system and operating details remain confidential
02 · Responsibility
My scope of responsibility
I analysed bottlenecks, optimised network architecture and devices, implemented security measures and set up backup and disaster recovery workflows.
- I assessed the existing network infrastructure and identified bottlenecks.
03 · Technical work
Documented scope of work
Key decisions
Bring network optimisation and recoverability together in one engagement. Reliable operation means not only stable connectivity, but also a tested way to recover after failures.
- I configured routers, switches and firewalls and added security measures.
- I planned backup jobs and disaster recovery workflows with Backup Exec.
04 · Technical context
Technology in use
Networking
Networking was part of the documented toolset in this Virtualisation & Operations engagement.
Routers
Routers was part of the documented toolset in this Virtualisation & Operations engagement.
Switches
Switches was part of the documented toolset in this Virtualisation & Operations engagement.
Firewalls
Firewalls was part of the documented toolset in this Virtualisation & Operations engagement.
Backup Exec
Backup Exec was part of the documented toolset in this Virtualisation & Operations engagement.
Disaster Recovery
Disaster Recovery was part of the documented toolset in this Virtualisation & Operations engagement.
05 · Factual basis
Evidence and limits
Network operations and data backup were developed further on a jointly aligned operating basis.
- Role
- Network Consultant
- Period
- June 2009 — July 2009
Lesson from the engagement
Network reliability is incomplete if backup and recovery are not part of the same operating model.
Confidentiality note: Internal architecture and operating data of this engagement are not published.