Datto SIRIS and Oracle Database VSS Writers Mastered
Datto SIRIS and Oracle Database
This article discusses issues that may be found when backing up Datto SIRIS and Oracle Database using ShadowSnap’s VSS backups as well as Oracle’s Intellisnap backup engine. Datto uses Microsoft Shadow Copy Provider’s Volume Shadow Copy Service, or VSS, and is the first process of most image based backup solutions. VSS was first available for Windows 2000 Operating System to create volume shadow copies. For VSS backup solutions it is important that only one process on the production machine uses these VSS Writers at the same time. If one or more of these processes are running on the same environment then this will cause a conflict between the solutions resulting in the failure of one or more VSS writers.
As discussed in this article via IntelliSnap, there is a known issue with the Oracle Intellisnap backup and the Oracle VSS writer:
“There is a known issue with Oracle VSS Writer memory leak (metalink ID 1358570.1). Hence, if Oravssw.exe consumes more memory, restart the service.”
Workaround for Datto SIRIS and Oracle Database Intellisnap Backup Engine
We have found this issue with Oracle 11 specifically, although other versions may be affected. Our findings have shown that this memory leak can eventually make its way into the pagefile of a device and cause a server to run out of memory, hindering all server operations. Restarting the service is a good start for this. If you’d like less VSS processes to be occurring, you can switch to the STC Backup Engine in the configure agent settings page, but the issue may still persist in the Oracle VSS writer.
Should the issues persist, it is recommended to contact Oracle support for further assistance in regards to this error.