4. PA2009 Backup Function Date Selection Error

    Recent Topics


PA2009 Backup Function Date Selection Error

  • J

    I’m pretty sure this issue came up and was resolved a couple of years ago, but . . . .

    Last night I ran my daily backup routines after just having upgraded to PA2009 and after checking my backup files I noticed that they got much bigger than previously. Obviously more files were now being included. I checked the backup routines (the .pbs files) and confirmed that my selection criteria of “newer than 30 days” had not changed during the upgrade process. However, checking the contents of my backup files revealed that files that had been modified MORE than 30 days ago were also included. However, not ALL files were included, so it was not effectively a full backup, but more like “newer than 70 days”.

    I’m not sure if there is a connection, but I use the Canadian date format of day/month/year, but this is a Windows system setting and is application independend.

    0
  • conexware

    are you overwriting the backup file? or updating it? That might be the issue - PA will not delete old archive anymore, it will update it with new files.

    0
  • J

    After I read another thread (“PA Backup File” by Martin), that thought occurred to me as well, but looking at the dates of the files contained in the bakup file, that would not appear to be the case.

    The backup job ran on Oct.2,2008 and was configured to select files “newer than” “30” days. Files found in the resulting ZIP file range in “modified” dates from Oct.2 to July 22. I think that is 71 days (perhaps that is significant somehow).

    0
  • conexware

    ah, newer… modified or created? there is an world of difference just there…

    0
  • J

    I’m not quite sure what you mean with your response spwolf.

    Just to clarify, I have not changed my PBS files, just updated (uninstalled PA2007 and installed PA2009) the program. The “newer than” option and my “30” days setting are still the same as in PA2007 (1022). The resulting ZIP file shows the “modified” date column, just as before. So the “newer than” option has always applied to the modified date, not the created date.

    Are you perhaps saying that in PA2009 the definition of “newer than” has changed?

    0
    J
     1 Reply
  • J

    Any more thoughts on this spwolf? Is this being investigated?

    0 1 Reply
  • conexware

    @Joe:

    Any more thoughts on this spwolf? Is this being investigated?

    fixed, waiting for release… 🙂

    0
  • conexware

    please check with 11.01… thank you!

    0
  • J

    Well, the latest PA2009 updates have fixed the original bug, but today I’ve discovered another problem with the “newer than xx days” option.

    It would seem that there is a fundamental error in the way the actual date is calculated. For instance, if I specify “newer than 30 days”, on the 30th day of the month the backup job will just sit there without doing anything. I suspect if I specify “newer than 1 day” the same problem will occur on every 1st day of each month.

    I’ve changed my monthly backup jobs to a “newer than 32 days” selection criteria, to circumvent this bug, but I need a solution for my weekly jobs (where I specify “newer than 7 days”).

    0 1 Reply
  • conexware

    @Joe:

    Well, the latest PA2009 updates have fixed the original bug, but today I’ve discovered another problem with the “newer than xx days” option.

    It would seem that there is a fundamental error in the way the actual date is calculated. For instance, if I specify “newer than 30 days”, on the 30th day of the month the backup job will just sit there without doing anything. I suspect if I specify “newer than 1 day” the same problem will occur on every 1st day of each month.

    I’ve changed my monthly backup jobs to a “newer than 32 days” selection criteria, to circumvent this bug, but I need a solution for my weekly jobs (where I specify “newer than 7 days”).

    so backup will not run on certain date = if that date= amount of days you entered on newer than?

    0
  • J

    It sure looks that way…the pattern is obvious…(newer than) 30 (days) minus (Oct.) 30 (th) = 0, hence PA2009 launches, but just sits there and processes 0 (nothing).

    I just tested another scenario and changed my system date to the 7th then ran a weekly backup (with “newer than 7 days”) and the same situation occurred again: PA2009 launches, but does nothing.

    0
  • conexware

    who da best support in the history of man kind?
    http://www.powerarchiver.com/test/release10/powarc1102.exe

    🙂

    0
  • conexware

    p.s. let us know if it works properly… thanks

    0
Log in to reply