Comments
Sort by recent activity
It's not ideal, but you could always import the DB (structures only, not data) into a local copy of SQL and do the compare locally... / comments
It's not ideal, but you could always import the DB (structures only, not data) into a local copy of SQL and do the compare locally...
Update:
Yesterday around noon, it failed for about 1 hour then fixed itself.
Then began failing again around 3:00 PM for about 9 hours and fixed itself again around 1:00 AM this morning.
petey wrote:
Could you pls post the results of running the following:
exec master..sqbmemory
The server it has been failing on (although currently it is working):
Type Minimum Maximum Average Blk count Total
Commit 4096 1073479680 0 1419 -1398685696
Reserve 4096 67063808 747046 294 219631616
Free 4096 3801088 305949 344 105246720
Private 4096 1073479680 0 1043 -1229021184
Mapped 4096 1536000 165290 48 7933952
Image 4096 5836800 67577 622 42033152
One of the servers it works correctly on:
Type Minimum Maximum Average Blk count Total
Commit 4096 1073479680 0 1261 -1406857216
Reserve 4096 8384512 492136 239 117620736
Free 4096 15007744 797885 270 215429120
Private 4096 1073479680 0 900 -1335246848
Mapped 4096 1536000 184320 44 8110080
Image 4096 5836800 68165 556 37900288
I will post it again later when it begins to fail again.
petey wrote:
An upgrade does not require you to reboot the server if you can release xp_sqlbackup.dll cleanly. It also does not require you to restart the SQL Server service, only the SQL Backup Agent service.
In the past it has caused problems on one of the servers during install, forcing a reboot, and my boss has made it clear that it's not worth the risk. / comments
Update:
Yesterday around noon, it failed for about 1 hour then fixed itself.
Then began failing again around 3:00 PM for about 9 hours and fixed itself again around 1:00 AM this morning.
petey wro...
I am currently using: SQL Backup 4.1.0.207 - Professional edition
And I can not upgrade to 4.2 (or reboot the server, or restart the SQL Server Service) until at least Sunday during the next scheduled Maintenance Window... / comments
I am currently using: SQL Backup 4.1.0.207 - Professional edition
And I can not upgrade to 4.2 (or reboot the server, or restart the SQL Server Service) until at least Sunday during the next schedu...
I had this same problem. petey sent me version 4.2.0.318 which solved the problem.
It seemed to be caused by the primary DB name differing from the restore DB name... / comments
I had this same problem. petey sent me version 4.2.0.318 which solved the problem.
It seemed to be caused by the primary DB name differing from the restore DB name...
petey wrote:
Exactly. Or if ProdDB was backed up on ServerA, but is now restored on ServerB (as ProdDB).
So this means LogShipping could never delete the files by definition? / comments
petey wrote:
Exactly. Or if ProdDB was backed up on ServerA, but is now restored on ServerB (as ProdDB).
So this means LogShipping could never delete the files by definition?
I'm sure you rarely get messages that are not complaints/questions, but I would liek to thank you for the quick help via PM... The new version you had me download does seem to be working well. / comments
I'm sure you rarely get messages that are not complaints/questions, but I would liek to thank you for the quick help via PM... The new version you had me download does seem to be working well.
petey wrote:
There is a bug that prevents a deletion if the backup server name and database name does not match the restore server name and database name.
So, if I have a DB named "ProdDB" and it's being restored to another server as "ProdBackUp" it won't allow deleting the log files after processing them? / comments
petey wrote:
There is a bug that prevents a deletion if the backup server name and database name does not match the restore server name and database name.
So, if I have a DB named "ProdDB" and...
memstat - Yohz Software (c) 2005 - 2006
NULL
Type Minimum Maximum Average Blk count Total
Commit 4096 1073479680 0 3468 -1268203520
Reserve 4096 4128768 390352 196 76509184
Free 4096 3735552 143414 822 117886976
Private 4096 1073479680 0 3162 -1226461184
Mapped 4096 1536000 166461 50 8323072
Image 4096 5836800 58503 452 26443776
NULL
NULL / comments
memstat - Yohz Software (c) 2005 - 2006
NULL
Type Minimum Maximum Average Blk count Total
Commit 4096 1073479680 0 3468 -1268203520
Res...
This houses a production DB which handles all login requests to our system
As well the other production servers are using native SQL Log Shipping (yes I know, I'm planning to move it to SQL Backup Log Shipping soon) and this server is the one which they are being shipped to
So there are constantly alot of processes on this machine at any moment in time, however it generally has fewers concurrent processes at any given moment than the other productions servers
Once I switch to SQL Backup Log Shipping I will be doing a round robin type of setup for the Log Shipping (server 1 sends to 2, 2 sends to 3, 3 sends to 4, 4 sends to 5, 5 sends to 1) which may reduce the traffic to any one server.
I do plan to upgrade to v4, but as this is a production environment, I'll have to wait for a scheduled maintenance window, and it would be nice to have this working a bit more regularly in the meantime. / comments
This houses a production DB which handles all login requests to our system
As well the other production servers are using native SQL Log Shipping (yes I know, I'm planning to move it to SQL Backup ...