Messages

1

General Software Discussion / Re: Anyone familiar with Oops!Backup?

« on: October 20, 2010, 11:57 AM »

Hi Jim,

Thanks! I'm happy to help.

Also I wanted to point out that if you are concerned about filling up a backup drive you can easily choose how many versions to keep from the Advanced Settings.  You can have old versions deleted automatically based upon these two options:

Option a:  Only keep old versions for a period of time (eg.  Delete versions after 1 month, 6 months, 2 years etc.)
Option b:  Set a size quota for the folder that is used to store previous versions.  (eg.  Only store 20GB of old versions)

Thanks,
Simon

2

General Software Discussion / Re: Anyone familiar with Oops!Backup?

« on: October 19, 2010, 10:36 AM »

Hi Armando,

Yes exactly - disabling that option would have prevented the problem. 

I really like your suggestion and I will definitely add it to our development wish list.

Thanks,
Simon

3

General Software Discussion / Re: Anyone familiar with Oops!Backup?

« on: October 19, 2010, 09:27 AM »

Hi MerleOne, yes you are right..

Unfortunately for a backup destination to receive the delta file with changes and then rebuild the original file, it needs to be an "intelligent" backend, which a USB drive or network share is not.
We will be working on this type of functionality (ie. a backend receiver application) in the future though.

Thanks
Simon

4

General Software Discussion / Re: Anyone familiar with Oops!Backup?

« on: October 19, 2010, 08:44 AM »

Hi Armando,

Just saw your second post now... Thanks for the offer.  It would be best to contact us on our support email or forum.

Thanks,
Simon

5

General Software Discussion / Re: Anyone familiar with Oops!Backup?

« on: October 19, 2010, 08:37 AM »

Hi Armando,

Thanks again for your help on this.  It's strange that Oops!Backup is taking up so much RAM for you even on simple start-up.  I have just checked on my system which is Windows 7 with 4GB RAM and you can see much lower RAM usage in the attached screenshot.  I agree with your points about the RAM fluctuating etc. I wish we could figure out why your RAM requirements are higher from startup.



Regarding the date discrepancy if a few files are skipped due to being locked then Oops!Backup still considers that as a successful backup.  Therefore the timestamp will still show up in the backintime browser.  There is a way to protect against this:

From the Advanced Settings in the Manager window -
- Enable VSS
- Disable "Backup anyway if VSS fails".

This way you would have been given a backup failure message instead of a warning.

Again I hope this helps   And thanks once again for all your help.

Thanks,
Simon

6

General Software Discussion / Re: Anyone familiar with Oops!Backup?

« on: October 19, 2010, 05:10 AM »

Hi Armando,

I am one of the developers of Oops!Backup and I wanted to give you some more information regarding the RAM requirements.  We have performed many tests to ensure that Oops!Backup is not using extra RAM.  Keep in mind that there is always a balance between better performance and low system requirements.

RAM Requirements

Normally you should be seeing this RAM Usage:

Oops!Backup Manager - around 50 MB of RAM
Oops!Backup Engine - around 23 MB of RAM
Oops!Backup VSS Service - around 10 MB of RAM.

We have noticed though that on Windows 7 systems with a large amount of RAM (3GB +) Oops!Backup uses more RAM.  Compared to a Windows 7 machines with 1GB RAM we see that the 3GB system can use up to twice as much RAM.  We have tested this with Performance Monitor and noticed that in Windows 7 when the system is running out of RAM then then Oops!Backup suddenly uses less RAM.  Also after leaving the system idle for a long period of time (0.5 - 1 hours) in Windows 7 Oops!Backup suddenly starts using much less RAM.  For example we see the Manager going down to 5/10 MB of RAM.  As soon as the UI of Oops!Backup is used then this jumps backup to 25MB and then to 50MB as the manager and backintime screens are loaded.

Also after a backup using ReverseDelta for large files (eg. PST) then you may see the Engine shoot up to 100MB of RAM.  This will only occur if the system has available RAM and will eventually be release once the backup has been completed.  This may not be release immediately but will be released when needed.

The point that I am trying to make is that we are sure that there are no Memory Leaks / Excessive RAM usage.  The more RAM available on a windows 7 machine the more RAM that is used.  When RAM is required for other applications then Oops!Backup will use less.

That being said we are always trying to reduce the resources that we use without effecting performance   In fact you can see that we managed to keep the CPU usage as low as possible.

Restore Issue

I also wanted to make a quick not regarding the restore issue that you had.  Oops!Backup will never overwrite the original file when restoring unless you enable the "Overwrite" checkbox manually.  It also allows for a Full Preview which restores the file to a temporary folder and opens it for you to check whether it is the correct version.  Finally if you set your backup frequency to every 5 minutes the previous version will never be older than 5 minutes as long as you keep on saving the file.

VSS Issue

Finally please note that VSS allows for the backup of locked and open files, but the file still needs to be saved before Oops!Backup can back it up.  Therefore if you are working on a word document Oops!Backup will backup the document while it is open but will only backup the last saved version of the file.  Therefore CTRL-S remains very important

I hope this helps and that you will continue to use Oops!Backup.

Thanks,
Simon (Altaro Software)