Skip to Content
Browse documentation

Backup, Restore and Transfer Logs

Find manual and scheduled backup logs, account restore diagnostics and per-task migration startup, package and account logs.

Identify the workflow first: a scheduled backup, a manual account archive, a restore and a migration task use different log destinations.

Backup and restore locations

Default locationPurpose
/var/log/backup/backupacct.logCommon manual account backup log when the caller uses that default.
/var/log/backup/backup.<username>.<timestamp>.logPer-account manual backup logs selected by the account backup command.
/var/log/backup/schedule/Scheduled backup logs; select the matching schedule/account and run.
/var/log/backup/restore/restoreacct.logCommon restore log when no more specific filename is selected.
/var/log/backup/restore/Other restore operation and account logs.

Commands and workers can supply operation-specific filenames. Some older package rotation policies also mention /var/log/backup/restoreacct.log or /var/log/eenos/backupacct.log; a rotation rule alone does not prove that the current operation writes there. Prefer the log path reported by the command or displayed for the task.

See Backup Manager and Migration restore for the corresponding workflows. An archive being created or transferred is not proof that its restore completed successfully.

Migration task logs

Current transfer jobs default to /var/log/transfer/<task-id>/.

Path inside the task directoryPurpose
transfer.logOverall transfer/controller progress.
startup.logDetached controller stderr; useful when startup fails before normal progress logging.
packages.logPackage import and mapping diagnostics when package work writes a log.
accounts/<username>/transfer.logDiagnostics for the selected account.

Use the actual task UUID and destination account name. A file may be absent if its stage never ran. startup.log may be empty when no stderr was emitted. A non-default transfer storage root changes these locations.

Correlate task, account and stage

Transfer log records include time, severity, task ID, account scope and stage. Review the overall task and then the affected account. The controller can report an account failure while other accounts continue.

The shared transfer formatter redacts recognized secrets, but stderr and external output still need review before sharing. Task directories also contain private state and credential material: do not send the entire task folder as a support attachment.

Use Transfer Progress to match the task's recorded outcome. Do not restart an import or restore solely because the last visible line looks incomplete; check account state, running work and existing task status first.