Based on a similar issue discussed here: the errors you are getting are issues related to Windows memory managent and availability of specific kind of resources (Kernel Paged Memory) which could happen during backups of big filesystems, or particularly large files.
Windows has a certain amount of memory pool space that it can allocate to programs, if the program uses all the memory available from that pool then ERROR 1450 (0x000005AA) raise up.
As literature several Microsoft Knowledge Base Articles describe this error code:
- Q304101 - Backup Fails with Event ID 1450
- Q247904 - How To Configure the Paged Address Pool and System Page Table Entry Memory Areas
- Q142719 - Windows Reports Out Of Resources Error When Memory Is Available
- Q236964 - Delayed Return of Paged Pool Causes Error 1450 "Insufficient Resources"
- Q192409 - Open Files Can Cause Kernel to Report
Specially Q304101 describes how to monitor resources to determine your state and offers a possible solution by tuning PoolUsageMaximum setting in Memory Management; this involvers changing registry settings therefore requires many cautions; you have been warned to read careffully the article before.
One thing you might do is separate the backup into different backups; together with monitoring memory this could help isolating the problem.
Let me suggest you an additional hint, to consider adding the /XJ
switch to your command line script; this way robocopy eXclude Junctions , this is important for example when copy user accounts (the \Users.. foleder) in some Windows such as Vista, because without this you can run in loop coused by some kind of hidden links called "junctions"