Connect. Secure. Manage.
Network Configuration Backup
Design recoverable configuration protection for supported Cisco and Meraki environments, checking coverage, access, retention and realistic restore capability.
Devices supported
across the UK
Client locations
supported
Traffic handled
at peak time
Average
response time
Average response is not a resolution time or a contractual guarantee. Support scope and response commitments are agreed for each engagement.
Network configuration backup should give your team usable material for recovery. We check which Cisco and Meraki settings can be saved, who can reach the copies and how they would be restored. The scope also names what depends on other platforms or licences. A downloaded file alone does not prove that a service can be recovered.
Useful visibility
Monitor service-relevant conditions rather than collecting alerts without ownership.
Controlled change
Keep maintenance, automation and configuration work reviewable and recoverable.
Clear escalation
Connect incidents to the right engineering, provider and business contacts.
Identify what recovery actually requires
We inventory the devices, controllers and cloud-managed services included in scope. Traditional switch setup, management-platform data and Meraki settings do not necessarily have the same export and restore behaviour. The design records the supported method for each rather than assuming a universal text file can rebuild the whole estate.
Recovery can also depend on software images, certificates, licences, external accounts and hardware compatibility. We identify those needs alongside the setup itself. A backup plan that omits them may appear complete until a replacement device arrives and cannot reproduce the original service.
Standards & partnerships
Confidence in the team behind your network.
Cisco Partner
Cisco Meraki
Cyber Essentials
Cyber Essentials PlusMCI Network Services is operated by Proxar Ltd. Certifications apply to the certified legal entity and the scope of its certificates. View accreditation information
Define collection coverage and frequency
The schedule reflects change frequency, service importance and the available supported interfaces. We consider whether collection should occur periodically, after approved changes or through a combination. The aim is a recoverable record with an understood recovery point, not merely the largest possible number of duplicate files.
Coverage checks identify missing devices and failed collection jobs. A newly installed switch or moved controller should enter the process through a defined onboarding step. Retired systems are removed deliberately while historical records are retained according to the customer’s agreed needs.
A useful starting point
Tell us what is happening.
A short description of the problem is enough for an initial discussion.
Protect sensitive configuration data
Network settings can contain credentials, keys, addresses and information about security boundaries. We agree storage, encryption, access and sharing controls appropriate to that sensitivity. Backups should not be placed in public web directories or copied into ordinary tickets without reviewing their contents.
Collection accounts receive the access needed for the supported export method. Credentials used by the backup system are themselves protected and recoverable through an approved process. If the backup depends on one person’s account or workstation, the design should identify that fragility rather than treat the file location as sufficient protection.
Different environments. The same care.
Built around the work
your network supports.
Finance, banking and the wider private sector. We start with the systems and people that depend on your connections.
Finance & banking
Market-data paths, routing and provider coordination on clients’ behalf.
Financial-market services ↗Offices & multi-site teams
Reliable access between people, workplaces and business applications.
Office network design ↗Data centres & cloud
Network boundaries, workload connections and operational ownership.
Data centre networks ↗Verify integrity and completeness
Checksums can help detect a changed or incomplete transfer. But they do not prove that the content can restore a service. We also examine whether the expected data was collected and whether an error message or truncated response has been saved in place of a setup. A successful job status needs appropriate supporting checks.
For controllers and cloud-managed platforms, export limitations are documented. API collection may provide useful records without constituting a full restorable backup of every feature. We distinguish setup evidence, replication of settings and vendor-supported restoration rather than calling all three the same thing.
Plan restoration before an outage
The recovery procedure identifies the supported replacement platform, software preparation, access and sequence of setup actions. It includes dependencies such as identity, routing and management network access. The team should know which steps can be completed in isolation and which require coordination with other service owners.
Restoration can itself disrupt a network if old addresses, keys or relationships are reintroduced incorrectly. We plan a safe test setup and controls around reconnecting recovered equipment. A backup is not permission to attach a cloned production setup to the live network without assessing its consequences.
Exercise selected recovery scenarios
Where agreed, we test retrieval, preparation and restoration using representative equipment or a suitable setup. The exercise records what worked, what information was missing and the time consumed under the test conditions. It does not on its own prove a universal recovery time for every future failure.
Untested components and vendor-dependent steps remain visible. The customer can then decide whether further testing, spare equipment or a different recovery design is needed. This is more useful than a blanket assurance based solely on the fact that scheduled exports have been completing.
Maintain the protection process
Changes in hardware, firmware, licensing or management platforms can invalidate an old recovery method. We set out ownership for reviewing those changes and keeping the procedure current. Retention and deletion are also agreed so sensitive historical settings are not kept indefinitely without a purpose.
MCI can establish setup protection within network operational assurance or review a current backup process. The deliverable explains coverage, limitations and tested recovery evidence for your Cisco and Meraki estate, giving the operating team a practical capability rather than a folder of files whose usefulness remains unproven.
Recovery access must also survive loss of the production authentication service; otherwise an available backup can remain inaccessible during the incident.
Talk to a specialist
Need a specialist view?
Tell us what is affected, what changed and what your team has already checked. A short outline is enough to start.
+44 203 196 6566Choose option 1
sales@proxar.co.ukUK-wide service.
Most of our engineers are based in Kent, with a focus on London, Sussex, Essex and Berkshire.
Existing customers should use their agreed support and escalation channels. This form is for service enquiries, not a monitored emergency ticket.
Tell us what you need.
A short outline is enough. Please do not include passwords or sensitive network details.
Thank you. Your enquiry has been submitted.
Please check your name, email and message, then try again.
Your form session expired. Please try again.
Please wait a minute before sending another enquiry.
We could not submit your enquiry. Please call or email us instead.