Comments
Sort by recent activity
results sent. / comments
results sent.
Run 1 as the standard command I've been using returns: BACKUP DATABASE successfully processed 4008260 pages in 377.103 seconds (83.039 MB/sec). Run 2 with fileoptions = 16 returns: BACKUP DATABASE successfully processed 4008260 pages in 374.802 seconds (83.549 MB/sec). Run 3 with fileoptions = 8 is actually worse with: BACKUP DATABASE successfully processed 4008260 pages in 425.041 seconds (73.674 MB/sec) / comments
Run 1 as the standard command I've been using returns: BACKUP DATABASE successfully processed 4008260 pages in 377.103 seconds (83.039 MB/sec).Run 2 with fileoptions = 16 returns:BACKUP DATABASE su...
I don't have a db that small on that box but I did run the test on the smallest I have and just like the above 1 runs at 176mb a second while the other is at 88mb a second. The 2 instances reside on the same host and the 2 drives are on the same shared storage array so there should be no difference between the backup speeds. If anything the 2nd cmd should be quicker as there's less activity on the 2nd instance. There's no humans on either instance and the 1st is the backside of an AAG mirror so is receiving prod updates and does backups. The other, slower backup is a snapshot of the same instance config with a different name so in my mind they should be equal or close to it. / comments
I don't have a db that small on that box but I did run the test on the smallest I have and just like the above 1 runs at 176mb a second while the other is at 88mb a second. The 2 instances reside o...
That's what i thought so had the network guy do that test and he's reporting 240+mb per second on either. / comments
That's what i thought so had the network guy do that test and he's reporting 240+mb per second on either.
There is no encryption or compression set for either run so in this case a nonfactor. I've used the same command with the only difference being the path in the job and in the adhoc sql and the adhoc takes twice the time. / comments
There is no encryption or compression set for either run so in this case a nonfactor. I've used the same command with the only difference being the path in the job and in the adhoc sql and the adho...
Perfect, worked as advertised, thanks / comments
Perfect, worked as advertised, thanks