Activity overview
Latest activity by mrclod
Full Text not observing MOVE on a RESTORE
Running into an issue when restoring a backup to an alternate server. This server contains multiple restores at any given time.
To get around file conflicts, we move files to appropriate places or...
Converted native backup and 3rd party apps
I recently converted some .sqb files to native backup format. That worked fine, however, I am finding 3rd party applications such as a log reader could not open the files claiming multiple errors....
sqb2mtf errors
I have copied over several different RedGate backups and have attempted to use sqb2mtf to convert to native format.
Version: 6.2.0.134
The examples of errors I get are:
Data decompression error: ZL...
Extended SP Documentation
I can only find stuff on the sqlbackup procedure. I have used sqbstatus, sqbmemory, sqbdir, but what might the rest be used for?
Can we have full documentation in the next release perhaps?
Thanks,...
Would the value of MemToLeave affect this by chance since redgate routines appear to be external stored procedures? / comments
Would the value of MemToLeave affect this by chance since redgate routines appear to be external stored procedures?
Set Threads to 3, MAXTRANSFERSIZE to 960 on the LOG backup only.
A reply from RedGate would be nice so I could stop taking stabs in the dark at this. / comments
Set Threads to 3, MAXTRANSFERSIZE to 960 on the LOG backup only.
A reply from RedGate would be nice so I could stop taking stabs in the dark at this.
I've tried reducing threads. Still get these errors. A second attempt (as specified for the backup job to do) is successful. Just doing a LOG backup at this point.
Threads are down to 2 and MAXTRANSFERSIZE is 1024.
Going to attempt to move the MAXTRANSFERSIZE down just a notch to see what happens. Not sure why a chunk of memory cannot be found in 3GB of free memory.
Does 6.2 address any of these issues??
2009-09-10 14:00:01.27 spid291 Error: 18210, Severity: 16, State: 1.
2009-09-10 14:00:01.27 spid291 BackupVirtualDeviceSet::Initialize: Request large buffers failure on backup device 'SQLBACKUP_FCBD0467-A16F-4C07-B32F-B2B1674D3188'. Operating system error 0x8007000e(Not enough storage is available to complete this operation.).
2009-09-10 14:00:01.27 spid291 Error: 18210, Severity: 16, State: 1.
2009-09-10 14:00:01.27 spid291 BackupVirtualDeviceSet::Initialize: Request large buffers failure on backup device 'SQLBACKUP_FCBD0467-A16F-4C07-B32F-B2B1674D3188'. Operating system error 0x8007000e(Not enough storage is available to complete this operation.). / comments
I've tried reducing threads. Still get these errors. A second attempt (as specified for the backup job to do) is successful. Just doing a LOG backup at this point.
Threads are down to 2 and MAXT...
Looks like our IT department didn't specify a max memory, setting SQL Server to have a max of 29G of the 32G on the system.
Not sure if that will do it, but not finding a lot of definitive information on the subject. / comments
Looks like our IT department didn't specify a max memory, setting SQL Server to have a max of 29G of the 32G on the system.
Not sure if that will do it, but not finding a lot of definitive informat...
Failed Virtual Allocate Bytes: FAIL_VIRTUAL_RESERVE
The backup worked locally, but appears to have failed to move the copy. I have 2TB of free space and the backup is about 40GB compressed. Backup Pro 5.4 running on a cluster.
Have included infor...