NovaBACKUP is a scheduled backup system for Windows files, folders, and disk images. It creates restorable backup sets on another drive, a network location, or cloud storage. NovaBACKUP does not behave like a normal file-sync folder: it records selected data through backup jobs, applies retention rules, and maintains a restore catalog that points to saved versions. A first-time user therefore needs to decide what must survive a failure, where each copy will live, and how long old copies should remain.
Choose the backup
A file backup protects chosen folders and can filter their contents by filename mask, date, size, or file attributes. Full, differential, and incremental methods change how much each run writes. A full job copies the selected set again. A differential job records changes since the last full backup, while an incremental job records changes since the preceding backup run.
NovaBACKUP also creates system images for recovery after a damaged drive or an operating-system failure. Image jobs follow a different storage path from ordinary file jobs, and the documented workflow uses legacy storage devices for them. A user who creates a cloud file-backup target should not assume that the same target also accepts a system image. That difference matters before a recovery plan depends on one destination.
Keep two copies
A hybrid backup writes to local storage first, then sends the completed data to cloud storage. The local copy can shorten a routine restore, while the off-site copy remains available after theft, fire, or failure of the local backup drive. Local and cloud retention have separate settings, so changing one does not silently change the other.
The first transfer may consume substantial time and bandwidth when the selected folders contain large media archives. Filters can keep replaceable downloads or temporary files outside the job. NovaBACKUP still needs enough local working space and a stable route to the destination. A cloud account is not a substitute for checking whether the job reached its completed state.
Protect the catalog
NovaBACKUP links each stored backup to an entry in the Restore index. Manually deleting backup files outside NovaBACKUP can leave catalog entries that point to nothing. The opposite mistake can also happen: an advanced retention option may remove an index entry when a removable drive or network share is only disconnected. The backup file can remain intact, but NovaBACKUP will need to import it again before it appears in the restore view.
Moving a local backup device to another computer also depends on exact details. The device name, capitalization, path, credentials, and encryption password must match the original setup. NovaBACKUP does not let the user edit a local device name or path after creation; an incorrect entry requires a replacement device definition. Losing the encryption password can make an otherwise healthy archive unusable.
Prove the restore
A green job result confirms that NovaBACKUP wrote the job it was asked to write. It does not prove that the selected folders contained every important item or that the recovery steps are understood. Open the Restore view, locate several dated versions, and restore a small sample to a separate folder. A disk-image plan also needs boot-media preparation and a test that reaches the recovery environment without writing over the working disk.
Retention cleanup should follow a successful restore test, not precede it. Keep the encryption password outside the protected computer, label removable drives clearly, and reconnect network targets before deleting index records. These steps turn NovaBACKUP archives into recovery material rather than files that merely occupy backup storage.
