Automate backup for Cisco Meraki devices without scripts

Cisco Meraki® configuration backup is the process of making a copy of the complete configuration and settings for Cisco Meraki devices. Configuration backups allow network administrators to recover quickly from a device failure, roll back from misconfiguration or simply revert a device to a previous state.

Because configurations change in time, configuration backups for Cisco Meraki should be created regularly and stored in a secure location.

Restorepoint includes support for the following Cisco Meraki device types:

  • Meraki MS
  • Meraki MX
  • Meraki MR
  • Meraki Networks

Meraki MX Appliances

  • Your Restorepoint appliance needs access to https://api.meraki.com on port 443.
  • The Meraki MX plugin (and accompanying import tool) require Restorepoint 5.4+.
  • Meraki devices require an API Key of an user account created on the Meraki dashboard. The API key should be entered into the password field. An account with Read-only access to the Organisation will only be able to Backup, not Restore configuration.
  • The Meraki MX appliance is required to have a private IP address assigned to an uplink interface. Restorepoint doesn't directly connect to this IP, but it's used for populating device information.
  • The Organisation ID is required by Restorepoint. To find your Organisation's ID, visit the Meraki API Developer page, click the Configuration button and input your API key. Click Save, then Run.
  • Some restore functions will restore the configuration as shown in Restorepoint in it's entirety. This will remove configuration that was added after the backup was taken. This affects:
  • Management Interface
  • Uplinks
  • Cellular Firewall Rules
  • Inbound Firewall Rules
  • Layer 3 Firewall Rules
  • Layer 7 Firewall Rules
  • One To One NAT Rules
  • One To Many NAT Rules
  • Port Forwarding Rules
  • Some restore functions will update or restore all individual parts of the configuration type. Specific, arbitrary configs (an invdividual VLAN, for example) cannot be chosen in Restorepoint. When restoring, this will not delete configuration added after the backup was taken. This affects:
  • LAN Configuration
  • Firewalled Services
  • Static Routes
  • The Meraki API has a limit of 10 requests per second. It is strongly recommended to spread out scheduled backups for all Meraki Networks & Devices in Restorepoint as much as possible to avoid API failures and locking out Restorepoint from backing up your other devices.

Meraki Networks

  • Your Restorepoint appliance needs access to https://api.meraki.com on port 443.
  • The Meraki Network plugin (and accompanying import tool) require Restorepoint 5.4+.
  • Meraki Networks require an API Key of an user account created on the Meraki dashboard. The API key should be entered into the Pa
  • ssword field. An account with Read-only access to the Organisation will only be able to Backup, not Restore configuration.
  • Meraki Networks don't have an IP address, but Restorepoint requires every 'device' to have one. An unused private IP, like 192.0.2.1, should be used. Mutliple Networks can use the same IP.
  • The Organisation ID and Network ID are required by Restorepoint. To find your Organisation's ID, visit the Meraki API Developer page, click the Configuration button and input your API key. Click Save, then Run. Networks can be found using the Get Organisation Networks API endpoint.
  • Network Switch configurations backed up include; Access Control Policies, Access Control Lists, OSPF Configuration.
  • Network Wireless configurations backed up include; non-default SSIDs, SSID Layer 3 & Layer 7 Firewall Rules
  • Restoring Merkai Network configurations are not currently supported.
  • The Meraki API has a limit of 10 requests per second. It is strongly recommended to spread out scheduled backups for all Meraki Networks & Devices in Restorepoint as much as possible to avoid API failures and locking out Restorepoint from backing up your other devices.

Meraki MS Switches

  • Your Restorepoint appliance needs access to https://api.meraki.com on port 443.
  • The Meraki MS plugin (and accompanying import tool) require Restorepoint 5.4+.
  • Meraki devices require an API Key of an user account created on the Meraki dashboard. The API key should be entered into the password field.
  • The Meraki Switch is required to have a private IP address applied to it's management interface. Restorepoint doesn't directly connect to this IP, but it's required for filtering device information.
  • The Organisation ID is required by Restorepoint. To find your Organisation's ID, visit the Meraki API Developer page, click the Configuration button and input your API key. Click Save, then Run.
  • Some restore functions will restore the configuration as shown in Restorepoint in it's entirety. This will remove configuration that was added after the backup was taken. This affects:
  • Management Interface
  • Some restore functions will update or restore all individual parts of the configuration type, and specific, arbitrary configs (an invdividual switchport, for example) cannot be chosen in Restorepoint. When restoring, this will not delete configuration added after the backup was taken. This affects:
  • Switchports
  • Layer 3 Interfaces
  • Static Routes
  • The Meraki API has a limit of 10 requests per second. It is strongly recommended to spread out scheduled backups for all Meraki Networks & Devices in Restorepoint as much as possible to avoid API failures and locking out Restorepoint from backing up your other devices.

Meraki Access Points

  • Your Restorepoint appliance needs access to https://api.meraki.com on port 443.
  • The Meraki MR plugin (and accompanying import tool) require Restorepoint 5.4+.
  • Meraki devices require an API Key of an user account created on the Meraki dashboard. The API key should be entered into the password field. An account with Read-only access to the Organisation will only be able to Backup, not Restore configuration.
  • The Meraki MR AP is required to have a private IP address assigned to an uplink interface. Restorepoint doesn't directly connect to this IP, but it's used for populating device information.
  • The Organisation ID is required by Restorepoint. To find your Organisation's ID, visit the Meraki API Developer page, click the Configuration button and input your API key. Click Save, then Run.
  • Some restore functions will restore the configuration as shown in Restorepoint in it's entirety. This will remove configuration that was added after the backup was taken. All individual parts of the configuration will be restored and dsecific, arbitrary configs (an invdividual SSID, for example) cannot be chosen individually in Restorepoint. This affects:
  • Management Interface
  • The Meraki API has a limit of 10 requests per second. It is strongly recommended to spread out scheduled backups for all Meraki Networks & Devices in Restorepoint as much as possible to avoid API failures and locking out Restorepoint from backing up your other devices.

Restorepoint enables organisations to remove network management complexity by putting routine tasks such as network configuration backup, compliance and change management tasks on autopilot across their multi-vendor network infrastructure.

Using Restorepoint's simple graphical user interface network administrators can quickly schedule network device backups without scripts, analyse devices to ensure security, compliance and automate bulk changes that would otherwise take hours or days to implement manually. Learn more about how Restorepoint how you can save time and ensure you meet your disaster recovery and compliance needs.