How to identify if a file has not been backed up in Windows 10

We have a Cobian backup apps that is configured to backup 'increment' form.   However, after upgrading our computers to Windows 10, for some reason, it detects that the files programmed to backup, reads them ALL as "not backed"; thus, running a backup for over 30gb of data.

We figure that the best bet to have the apps running again as increment is:

Search all files in backup area for files last modified after the correct backup performed which was 12/8/2015
Change the configuration of those files identified as modified after 12/8/2015 to NOT-BACKED-UP (don't know the correct technical wording to Not0Backed-Up-Status)
Run the Cobian apps again so it can backup all modified after 12/8/2015

We came to this conclusion based on the properties of the files in this periodic backup routine we have setup (see below)
backup or not status
Please advice what Windows program we can use to find the files modified after 12/8/2015 and what windows program we can use to change
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
Sounds as if the Archive file attribute as been set on all files. Sounds strange, though.
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
Using PowerShell seems to be best here:
$Source = 'C:\Users\RIO\Documents\New Folder'
$BackupDate = [DateTime] "2015-12-08 22:00"

get-childitem -recurse $source |
  ? { $_.Attributes -like '*Archive*' -and  $_.LastWriteTime -lt $BackupDate } |
  % { 
    $_.Attributes += 'Archive'

Open in new window

This might look strange  - adding the archive bit to files it is already set -  but that in fact toggles the attribute.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
janaAuthor Commented:
OK, so there is an attribute we can change!!! Thanx!!

To understand it, in line '$_.Attributes -like '*Archive*' -and  $_.LastWriteTime -lt $BackupDate } ', the '$_.LastWriteTime' is the "condition" where it says if FILE-CHANGE-DATE is greater than '$BackupDate'?

Also, running this will also modified the sub-folders?
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
The logic is reversed. The archive bit is set whenever a file gets modified (or created). It is not "has been archived" but "needs to get archived", where "archived" means "backed up".
So the condition will check for the archive bit set (= will get backed up), but being modified prior to the timestamp of "2015-12-08 22:00" (08-Dec-2015 10:00pm). I've assumed an arbitrary time, change as needed.
-lt stands for "less than", and in time references means "before".

get-childitem -recurse will go thru all subfolders and files starting at the path provided. -recurse is saying that.
janaAuthor Commented:

Can we use that same script or maybe changed it to only display, not change the attribute?
(we want to see how many files has been modified after 1218/2015)
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
Replace line 7 with
That will just push the file object to the pipeline, and since we are not doing anything with it, display it.
janaAuthor Commented:
Line 7 says '$_.Attributes += 'Archive', where should we place '$_'?
That's all good, but first: is your cobian software aware of the archive bit - are you sure? Some softwares use their own hashing methods to determine if a file has changed and needs to be backed up.
Also: you say it does not work the way you like it after upgrading to win10. So when was the last backup done? Before the backup to 10? Then 30 GBs of increment would be perfectly normal.
Lastly: what does cobian support say and is the software known to be win10 compatible?
janaAuthor Commented:
is your cobian software aware of the archive bit - are you sure?

Yes, the cobain software is aware of the archive bit (we've been in using the apps for some years).

So when was the last backup done? Before the backup to 10?

On December 8, 2015 and the before upgrading to w10

what does cobian support say and is the software known to be win10 compatible?

We did go into Cobain site prior upgrade and there is no mention of w10 compatibility, but lots a forums has said works with no problem; so we gave it a go.
janaAuthor Commented:
Ok, we think we got it; how to display all files that are with the ARCHIVE active and before 12/8/2015 (had to take a short course on powershell but came in good time):

dir  -recurse |  ? { $_.Attributes -like '*Archive*' -and  $_.LastWriteTime -lt $BackupDate}

so our question on ID: 41389183 can be omitted.

Now test the changing of attribute
janaAuthor Commented:
We tested the script on a test folder and it changed the attribute to every file before 12/8/2015!
(note: the $BackupDate value changed it to 12/8/2015 23:59)

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage Software

From novice to tech pro — start learning today.