✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Kanban for WP Database Backup

WP Database Backup stores every database dump as a row in wp_db_backup_jobs with state, source, and destination. SleekView Kanban reads that data, groups database dumps by status, and lets the team drag a failed card back to queued without leaving the admin.

♾️ Lifetime License available

SleekView Kanban board for WP Database Backup

Why WP Database Backup database dumps fit a kanban view

WP Database Backup keeps every database dump as a row in wp_db_backup_jobs with the state, the source, the destination, and the runtime stored alongside the slot. Related metadata lives in wp_db_backup_archives. The default admin screen shows that data as a flat list sorted by date, which is fine for record lookup but slow when an overnight database dump has stalled and a site database admin needs to see whether it is queued, running, or has actually moved to failed state.

SleekView Kanban points at the same database dump records and renders them as four columns: Queued, Running, Successful, and Failed. Each card surfaces the database dump label, the destination handle, and the runtime. When a failed database dump needs another attempt, the team drags the card back into queued and WP Database Backup picks it up on the next pass. No second list, no manual retry through a settings screen that buries the action behind tabs.

The team can filter the board by destination, schedule, or scope, then save that filtered view as a board for one site or one client. The kanban reads from the live database dump records, so retrying a card here triggers the same code path that the standard run button uses, with the same hooks firing for notifications and logs.

Workflow

From the default DB Backup list to a live board

1

Connect DB Backup as the source

Pick WP Database Backup from the SleekView data source picker. It auto-detects the wp_db_backup_jobs store and the wp_db_backup_archives metadata so the board reads the same records as the
2

Group cards by the status field

Select the status field as the kanban column. SleekView reads every distinct value, surfaces Queued, Running, Successful, Failed, and lets the team rename, reorder, hide, or recolor each column without touching the WP
3

Pick the card front fields

Choose the database dump label, the destination handle, and the runtime as the card front. Add a secondary line for schedule and log line. The card editor previews real database dump data so the team confirms the layout
4

Enable drag-and-drop writeback

Turn writeback on and dragging a card writes the new status back to the WP Database Backup record via the WordPress REST API. Capability checks honor the existing admin role, and every move is recorded for full audit

Sample board

Sample DB Backup board grouped by status

Four real status columns showing how a site database admin moves DB Backup database dumps across Queued, Running, Successful, and Failed during a single working session.
Queued
4
Nightly database dump waiting in queue
Local archive, 02:00 UTC slot
Weekly database to email waiting run
Email, Sunday 03:00 UTC slot
Manual pre-deploy dump waiting in queue
Dropbox folder destination
Running
1
Nightly database dump currently running
Tables 26 of 64 processed
Weekly database to email currently running
Tables 12 of 64 processed
Manual pre-deploy dump currently running
Tables 8 of 64 processed
Successful
210
Nightly database dump finished success
Size 84 MB, finished 02:08
Weekly database to email finished ok
Size 80 MB, finished 03:04
Pre-deploy database dump finished ok
Size 86 MB, finished 11:18
Failed
3
Nightly database dump run did fail
mysqldump returned error 28
Weekly database to email did fail
Email server rejected size
Manual pre-deploy dump run did fail
Dropbox token expired today

Comparison

Default DB Backup screen vs SleekView Kanban

Default DB Backup list

  • Default screen is a flat sortable list hiding database dump status behind a small pill
  • Updating a database dump status takes three clicks and a full page reload every time
  • No live counts per state, so workload across database dumps stays hidden from the team
  • Bulk actions cover delete and trash but never bulk status moves across many rows
  • Filtering by destination resets when navigating between pages of database dumps listing

SleekView Kanban

  • Drag a card from failed to queued and the status writes back live
  • Column counts update live so the database admin sees workload without filtering or scrolling
  • Save filtered boards as URLs, one per destination, schedule, or scope across the site
  • Card front maps to the database dump label, destination handle, runtime, and last log line
  • Permissions inherit from WP Database Backup roles, no second auth layer to maintain inside ad

Features

What SleekView Kanban gives you for WP Database Backup

Status columns you can rename

WP Database Backup ships with Queued, Running, Successful, Failed as the four core states. Rename them to match the runbook, reorder them to match the flow, and recolor each column so the board makes failed database dumps obvious

Drag to retry not re-trigger

Every card move writes back to the same status field that WP Database Backup already reads, so retried database dumps run through the same pipeline as fresh ones. No second queue, no shadow retry list, no risk of two runs racing

Filter by destination or scope

Add a secondary filter on the destination handle, the scope, or the schedule slot and SleekView narrows the board to that subset. Ops sees the full board, the database admin sees one destination, and the manager keeps the

Audience

Where database admins use the DB Backup kanban first

Morning backup triage

Open the board at 9am, scan the failed column for overnight issues, drag failed database dumps back into queued, and watch the running column drain as the next pass processes the retries from across

Pre-release backup checkpoint

Before a release, fire a manual database dump card, watch it move from queued to running to successful, then promote the deploy. If the database dump fails, the card stays in failed until the retry

Multi-site capacity view

Filter the board to one client site at a time and watch the running column count as a live capacity gauge. If running stays full while queued grows, stagger schedules before the queue stalls the next

The bigger picture

Why a kanban beats the default DB Backup screen

WP Database Backup is a great backup engine. The records hold the state, the destination map holds the targets, and the schedule slot holds the timing. What it does not give the team is a daily operating picture of which database dumps are healthy and which are not.

The default screen is a record list, designed to inspect a single database dump, not to triage a column of failed database dumps at once. The site database admin ends up keeping a separate sticky note of failed runs or wiring a notification plugin just to know which database dump died overnight while the team slept. A kanban changes the shape of the work.

Instead of asking which database dumps need attention today, the team sees the answer as soon as the page loads, because every failed database dump is in the failed column and every running one is in the running column. Moving a card writes the new status back to the record, so the picture stays accurate. The database admin works the board, the manager reads the column counts, and the on-call engineer treats the failed column as a single source of truth.

Questions

Common questions about SleekView Kanban for WP Database Backup

No. The board reads from the same wp_db_backup_jobs store that the plugin already uses. When the team drags a card, SleekView writes the new status back to that store, so there is only one source of truth for every database dump on the site and every WP Database Backup hook still fires correctly during the run.

 

Yes. The column titles are display labels, not the underlying status values. Rename queued to waiting, failed to broken, or anything else that matches how the team writes incident notes. SleekView stores the rename separately so the data still uses the standard WP Database Backup values.

 

SleekView Kanban inherits the WP Database Backup capability map. If a user can run a database dump or view the admin screen, they can drag the matching card on the board. If they only have view rights, the board renders in read-only mode and the drag handles stay hidden from each card.

 

Yes. Add a filter on the destination handle or the schedule slot, then save the filtered view as a named board. Each board gets its own URL so one destination board lives next to another, and a single board can stay open on a status monitor without losing the rest.

 

The kanban polls the WP Database Backup record store at a configurable interval, with two minutes as the default. New successful and failed entries appear in the matching column within that window. Existing cards refresh in place so dragging a card never loses its position when a sibling updates.

 

Yes. SleekView reads every distinct value in the status field, including the extra states that add-ons register for cloud destinations and remote stores. The team chooses which of those columns to show on the board and hides the rest without removing the underlying data.

 

Yes. The card editor lets the team pick any field stored on the database dump record, including the destination handle, the runtime, and the last log line. A common layout shows the database dump label, destination, and runtime on the front, with the log line visible on hover for the engineer.

 

Yes. The plugins do not conflict because SleekView only reads and writes the same records that WP Database Backup already manages. Many teams use the admin screen for one-time setup and configuration, and the kanban for daily triage and retries from across the whole site at once.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView