When you test this again, can you get an export of the server task log detail for that task and also the orion log section with those messages? I am curious about them. I would also like a directory listing of the software directory (db\software). The command would be, for example, dir /s > c:\Windows\temp\software.txt when you cd to that directory in command prompt.
Not sure what you are asking with that question, please clarify as this thread doesn't have anything to do wtih laptops.
That is someone else that added a comment to my thread. I looked at what the other user posted and agree that it is not related to my issue.
I have reinstalled ePO 5.9.1 and currently running a disaster recovery snapshot. How do I export the taskmlog for the disaster recovery task. I can see how I can show that it completed but don't know a wayo exporting the actual detail.
Is there a way of sending you the orion log files and that directory listing that you are wanting. Not really in favour of posting the whole log file to a public forum.
Yea, I agree about not posting on public forum any logs that could contain company info. Depending on size of log, you can email them to me at firstname.lastname@example.org and screenshots of the server task log detail
Have just sent you the log files, directory listing of the db\software folderalong with screen captures of the disaster recovery task log.
OK, I've done some more testing and looked at the files you sent in - thanks for that.
It looks like it's just a logging issue, which also existed in previous versions of ePO: I tried 5.3.2, 5.3.3 and 5.9.1, and all show the same pattern of "skipping file..." messages. However the actual files are definitely written to the snapshot in the database: if you run the following query against the ePO database
select * from orionsnapshot order by targetextension
and then check the rows where the targetextension value is RepositoryMgmt, in the Key column you'll see the paths to the stored software packages.
I'm not sure of the exact reason behind the logging, but it appears that a) nothing has actually changed and b) the snapshot process is still functioning correctly.
Hopefully that helps