PowerSEC backups are designed to run in passes so large sites can complete without relying on one long request.
Reliability on constrained hosting
Recent improvements reduce the chance of memory exhaustion on shared or memory-limited hosting. Large backup file lists are stored outside the WordPress options table, the database export is written in byte-bounded chunks to avoid running out of memory on wide rows, and a backup that previously got stuck can have its stale state cleared automatically when it is safe to do so — so a large site is far less likely to get stuck endlessly retrying a backup that never finishes.
What a .part file means
A .part file means a backup artifact is still being written, or was interrupted before it finished. It is not a finished backup. PowerSEC only treats a backup as usable after the expected files and checksum information are available.
Local completion vs. cloud upload
Local backup completion and off-site (cloud) upload are separate states. A local backup can finish while the cloud copy is still pending, retrying, or failed. A backup is not considered healthy just because a job started — check that it actually completed.
Before a destructive change
For restore safety, use verified restore points and review backup status before making destructive site changes. PowerSEC verifies backup artifacts with SHA-256 checksums.
These improvements make backups much more reliable on constrained hosts, but no backup system can promise that every host will always finish regardless of its limits. If a backup repeatedly fails, review your host's PHP memory limit and available disk space.