Check backup visibility
An empty backup view shows what the selected account can see for this VPS. Confirm the actual backup arrangement before inferring a failed job.
An empty Virtualizor view is not a reason to restore, reinstall or start a new backup. Confirm the service's backup availability, schedule, retention and restore rights; panel visibility is account-specific.
Write down the VPS identifier, the last restore point you expected and why that date matters. If data has just been lost, ask the application owner to limit further writes where practical and preserve the current state for diagnosis. A backup taken now cannot recreate an older missing file or database state; it may still be useful as a separate preservation step once its impact and entitlement are understood.
Make three read-only checks in the authorised panel
- Open the VPS from your authorised service or Virtualizor link and confirm its identifier and hostname. Another VPS in the same account can have a different backup history.
- If your account offers a Backup action on the VPS management page, open its listing and record the visible restore-point dates, statuses and any error. Virtualizor documents a view that lists existing backups and may offer Backup Now; the button's presence does not establish a scheduled backup, retention promise or successful recovery.
- Compare the displayed time and time zone with the expected backup window. Note whether the whole backup control is absent, the list is empty, a specific date is missing or a listed task is incomplete. These are different symptoms. Do not click Restore, Reinstall or Backup Now simply to see whether the display changes.
If the backup area is absent, check your service terms or ask Novasean whether this VPS has an included or optional backup and whether your account is allowed to view it. Do not assume a vendor feature is enabled in your plan. If you use a separate application, DirectAdmin or third-party backup service, check that service's own inventory; it need not appear as a Virtualizor VPS backup.
Separate visibility, creation and restoration
| What you observe | What to verify next |
|---|---|
| No backup control for this VPS | Confirm the service's backup entitlement, panel permissions and whether another approved backup route is used. |
| Control exists, but the list is empty | Ask whether a backup plan was assigned, whether a job has completed, and whether retained copies exist outside this account view. |
| An older point is listed, but the expected one is absent | Record both dates and the expected schedule; ask the operator to check the relevant task, plan and retention evidence. |
| A point is listed, but Restore is absent or disabled | Check whether end-user restoration is permitted for the assigned plan and arrange an operator-led recovery if needed. |
Virtualizor documents end-user backup and restore permissions as conditional in its Backuply plan. Backuply is a particular backup system; its documentation does not establish that it is deployed for your Novasean VPS. A completed or listed backup is also not a verified application recovery. Databases, files, external storage and secrets may need coordinated restoration.
Illustrative distinction: one backup date is visible but yesterday's point is missing. Record both timestamps and ask the operator to check the scheduled job and retention for this VPS.
Protect the live VPS before considering a restore
Restoring onto the same VPS can replace its current state with an older one. Virtualizor also documents an administrator route to restore to a new VPS, but that is an operator workflow and may not be available for your service. Before anyone starts a restore, agree the exact source restore point, target VPS, expected data loss, downtime, application dependencies and person who approves the change. Preserve a separate current-state copy where feasible. Do not overwrite the only working instance just to test whether a backup is usable.
For a business-critical recovery, ask whether an isolated restore test can be arranged. Check representative files, database records and application behaviour there before treating the restore point as dependable. A VPS image alone may not capture application-consistent state while transactions are being written; use the related application-consistent backup guide when that matters.
Ask support a question they can investigate
Send Novasean the service and VPS identifiers, the expected backup date and time zone, the most recent point visible, the exact panel message or task identifier, and whether this is an active data-loss incident. Ask which backup arrangement applies to this VPS, whether the expected job completed, what retention applies and who is authorised to restore it. Novasean can check the platform side within the agreed service boundary; the customer's application owner still needs to identify a valid recovery point and test the recovered workload.
Share a redacted screenshot only if needed. Keep passwords, private keys, backup encryption keys, personal data and raw customer database contents out of the ticket. If support confirms no suitable VPS restore point, inspect independent application or off-VPS backups before declaring the data unrecoverable. Record the outcome and set a tested backup and restore routine appropriate to the service.
For an accepted matching VM Start with Managed OS order, the published schedule describes daily same-datacentre PBS backups; their presence is not proved by a Virtualizor list.
Common questions
Should I press Backup Now when an older point is missing? Not as a substitute for diagnosis. A new copy captures a later state and cannot recreate the missing historical point. Confirm permission, capacity and operational impact first.
Does a backup icon mean automatic backups are included? No. Confirm the actual service, assigned plan, schedule and retention with the provider.
Can I restore the only visible point immediately? First confirm its date, target and effect on current data. Arrange an approved recovery plan and, where possible, test it away from production.
Sources and technical references
Related guides
Was this guide helpful?
If you accepted optional analytics, your Yes/No answer and this guide’s page address are sent to Google Analytics. No written feedback is collected. Read our privacy statement or change your choice in .
Need help with your service?
Open your client area or contact Novasean. Describe the symptom and checks you have performed. Keep passwords, recovery codes and private keys out of your message.