One of my customers is using SnapDrive to perform rolling updates and scheduled updates of the SQL databases between their Primary and Secondary sites. They have noticed an issue over the past few weeks where they are expereincing periodic outages on their link between sites, which often occurs during a Snapmirror update. They are aware that they need to get this issue resolved, and that is a something they are working with their provider on, however I've noticed a behavior that I consider to be flawed. SnapDrive, when it triggers an update that gets interrupted, does not resume that update when the link becomes available again. Nor does it allow further scheduled updates to trigger a Snapmirror update. Apparently, when the triggered update gets interrupted, SnapDrive queues further updates indefinitely, and the only mechanism for getting automatic updates to resume is to restart the SnapDrive service.
I hesitate to tell the customer to build a process which automatically restarts SnapDrive on a daily basis to get these updates to resume, but this is the only mechanism I can find to get this working again. If I try a manual update after an interrupted transmission using SnapDrive, I will get an application log warning indicating the requests has been queued. Days can pass and this behavior will not change, even though I can use the CLI or FilerView to directly submit a SnapMIrror update just fine. Only a service restart clears this up.
Is it possible to manually clear this queue without changing the service state, or to have a timer on queued requests so that they expire after a period of time? We are using SDW 6.0.2. Any advice would be appreciated. Thanks in advance!
-Jarred