Issue/Error: All SQL Snapshots are set to start at same time. Half will fail due to lack of memory or timeouts. Request/Solution: Stagger the start time of Agent creating Snapshot, according to DB size of PREVIOUS snapshot! Scenario: Our company has recently updated to 2022, and everything is running smoothly with new replication model. Except the weekly snapshot generation fails or produces invalid results for half of all Vaults! Errors are: “Not enough memory resources are available to process this command.” “Exception of type 'System.OutOfMemoryException' was thrown” "The initial snapshot for publication ' ADMS_AI2022...' is not yet available" - after a time out due to long processing time. Turns out Snapshot agent consumes 50 MB memory for small DB and up to 350 MB for larger. When user enables replication for a Vault or CC Library, Vault creates an Agent Job for creation of new Snapshot on a weekly basis. They are all set to start at same time (Sunday 12 AM), which leads to memory overload. In our case with 25 Vaults and 33 Libraries – that leads to memory issue, even with expanded size of Page file. You could (and we do already) limit the memory consumption for SQL Server, but it seems counterproductive to limit the SQL performance for the whole work week, due to a job happening only once a week for maybe 2 hours. Suggestion/request: When user Enables Replication of a Vault or CC Library, ADMS Console checks the size, and staggers the start time so it does not overlap with the previous job. If many changes are done, an additional “Reset Snapshot timing” for ALL jobs could also be welcomed. Feel free to contact us if more info is needed Regards Uffe Bak
Show More