Robocopy MINLAD:N

scottclarke · 2013-03-22T14:56:47.000Z

I have this robocopy script that I’m testing out before putting into the production environment…

robocopy Z:\Docs E:\Backup /e /zb /copy:dats /move /minlad:30 /vb

But the test files I’m trying to move all come back as being too new in the verbose output log despite having last modified dates from December 2012.

Ideas?

Little-Green-Man · 2013-03-22T15:05:51.000Z

Does it work if you change your copy mode to /COPYALL ? or if you change dats to datsu?

scottclarke · 2013-03-22T15:06:58.000Z

Nope, still says too new.

Little-Green-Man · 2013-03-22T15:09:47.000Z

/minage:0 ?

scottclarke · 2013-03-22T15:11:17.000Z

Still the same I’m afraid…

Little-Green-Man · 2013-03-22T15:20:45.000Z

If those are just standalone files (not folders) then I would try removing the /e since there are no sub folders to copy.

scottclarke · 2013-03-22T15:21:46.000Z

There are files that are in the root directory and then files that are inside sub directories. I want to move them all where they meet the minimum age constraint.

scottclarke · 2013-03-25T14:05:39.000Z

Anyone have any ideas with this?

brentmhk · 2013-03-25T15:45:09.000Z

You are trying to filter based on the Last Access Date, which is completey different from the last modified date. Often just browsing a folder in Windows Explorer will update acess timestamp on all files in that folder.

I would try using /MINAGE instead of /MINLAD and see if that resolves the issue.

scottclarke · 2013-03-25T15:52:17.000Z

That works a treat but its the last time that the file was modified that I need as I’m looking to deploy this script on a 1TB file server to move everything thats not been touched in 18 months onto our Archive machine.

martinpeverley · 2013-03-25T16:16:44.000Z

From the attached:

/MAXAGE:n Excludes files with a Last Modified Date older than n days or specified date. If n is less than 1900, then n is expressed in days. Otherwise, n is a date expressed as YYYYMMDD.
/MINAGE:n Excludes files with a Last Modified Date newer than n days or specified date. If n is less than 1900, then n is expressed in days. Otherwise, n is a date expressed as YYYYMMDD.
/MAXLAD:n Excludes files with a Last Access Date older than n days or specified date. If n is less than 1900, then n is expressed in days. Otherwise, n is a date expressed as YYYYMMDD.
/MINLAD:n Excludes files with a Last Access Date newer than n days or specified date. If n is less than 1900, then n is expressed in days. Otherwise, n is a date expressed as YYYYMMDD.

So, MINAGE should do it, as Brent says.

robocopy.pdf (120 KB)

Little-Green-Man · 2013-03-25T18:31:51.000Z

BrentMHK:

You are trying to filter based on the Last Access Date, which is completey different from the last modified date. Often just browsing a folder in Windows Explorer will update acess timestamp on all files in that folder.

I would try using /MINAGE instead of /MINLAD and see if that resolves the issue.

I had suggested the same thing.

Little-Green-Man · 2013-03-25T18:33:06.000Z

Limey:

From the attached:

/MAXAGE:n Excludes files with a Last Modified Date older than n days or specified date. If n is less than 1900, then n is expressed in days. Otherwise, n is a date expressed as YYYYMMDD.
/MINAGE:n Excludes files with a Last Modified Date newer than n days or specified date. If n is less than 1900, then n is expressed in days. Otherwise, n is a date expressed as YYYYMMDD.
/MAXLAD:n Excludes files with a Last Access Date older than n days or specified date. If n is less than 1900, then n is expressed in days. Otherwise, n is a date expressed as YYYYMMDD.
/MINLAD:n Excludes files with a Last Access Date newer than n days or specified date. If n is less than 1900, then n is expressed in days. Otherwise, n is a date expressed as YYYYMMDD.

So, MINAGE should do it, as Brent says.

Agreed ^^