Improve existing functionality

Explain how we could improve existing OnApp functionality, and how it would help you.

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Safe delete resources

    We regularly face one issue: users or our employees under certain circumstances delete all the resources.

    Situation 1:
    user creates a server, sets the back-ups on it and everything works good. Once he decides to delete the server. All the back-up are being deleted with the server, as the user didn't read the notification that they will be deleted.

    Situation 1a:
    All the above mentioned actions are made not by the user, but by a violator, who fit or stole a password, or even by an offended contractor.

    Situation 2:
    An employee deletes the account. And after this all the…

    7 votes
    Sign in Sign in with OnApp
    Signed in as (Sign out)

    We’ll send you updates on this idea

  2. Speedup auto backups by using existing instances of daily backups for weekly, monthly, yearly copies.

    If there is configured a daily backups schedule, successfully created daily backup can be easily turned in to copies of other longer periods. No need wasting time and resources for creating separate instances executing weekly, monthly or yearly schedules. Just use existing daily copy instead of removing it on next turn.

    7 votes
    Sign in Sign in with OnApp
    Signed in as (Sign out)

    We’ll send you updates on this idea

  3. Make LVM snapshot size configurable for backups

    Currently, when a backup is created, a LVM snapshot of the disk is made. This snapshot has the same size as the original.

    This means you need to leave a *lot* of free space on each data store. Since a backup will complete in a relatively short amount of time, the snapshot will never fill for more than a few percent.

    So, I'd like to have smaller LVM snapshots when taking backups. Perferably a configurable percentage of the original disk size.

    --

    Lvm snapshot`s Create as full disk size. One moment 3-4 backup from one storage used 500-700 GB and…

    6 votes
    Sign in Sign in with OnApp
    Signed in as (Sign out)

    We’ll send you updates on this idea

  4. Clone server from backup 2+ disks

    The task is that the user wants to restore the backup of the current server to a new virtual machine, and everything is fine if the user has an entire server from one disk (then the task is simple, we make the template and roll the whole server out of it ).
    But what should a client do if his server consists of several disks? He can clone the system, but how to get the remaining disks from backups?
    Then I take out a large "saw" and climb into the database by changing the backup target disk to the new…

    2 votes
    Sign in Sign in with OnApp
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Backups  ·  Admin →
  • Don't see your idea?

Improve existing functionality

Feedback and Knowledge Base