2011-03-02 10:33 AM - edited 2015-12-18 01:28 AM
We are running SQL backups using snapmanager, when executing a second instance of a backup on another instance on the same server via SQL agent we get the following error. "There is another SnapManager operation currently in progress on this server. Please retry this operation after the conclusion of current job.", can this tool only do single thread/job? Our 15 minutes tran log update is interferring with our nightly full. My plan is to restart on failure since the tran log backup only runs for a few minutes. I would like the ability to run mutiple jobs but it doesn't look like that's the case, anyone have any input on this?
C:\Program Files\NetApp\SnapManager for SQL Server\SmSqlBi.exe -H "SERVER\INSTANCE1" -D 3 -R -G -S "SERVER\INSTANCE1" -C 0 -N -Daily
2011-03-02 11:57 AM
You cannot run multiple threads, you will always receive that error. Usualy this tends to be a good thing since creating a backup means quiescing the database and moving around log files from log disk to snapinfo disk, so it generates a certain load. Multiple threads would generate even more load.
As for interferance with your nightly full, you might be able to skip one 15min transaction log backup in your schedule so the nightly full has enough time to complete.eg. start your schedule at 0:30am and end it at 12pm, so the nightly full has 30 minutes to complete.
2011-03-02 01:44 PM
I agree, more snaps more resources, but the DB's are small and only run a few minutes based off the logs. I would rather be backing up a few small 2GB databases at the same time then need to stagger them.
At this point I will end up adjusting the 15 minute tran backup to stop start around the full's on the other instances. In the end I would like that option and control. It's the SAN / SQL admin's responsibility to monitor resources and backups.