Activity overview
Latest activity by msalas
Fieldmapping not valid for MatchingMappings
I have a SQL Data Compare Profile that I had been using and I just maintain this Profile. Now, when I am opening this profile, I get the error on Mapping. "Fieldmapping not valid for MatchingMappi...
The email and attempts finally stopped/cancelled. Whew!
Is it possible to have a link to the documentation for sqbdata?
Thanks a lot! / comments
The email and attempts finally stopped/cancelled. Whew!
Is it possible to have a link to the documentation for sqbdata?
Thanks a lot!
Hmmm... there are 5 records that even though they were already showing a status of "C", earlier, after a while it goes back to "A" and the count increases.
Any idea on how to really stop those, now it's down to 5 records (hopefully the others doesn't come back to life.
Out of curiosity, there are subsequent copies (from job) that were not copied over, and they have a status of "P"... what does that mean? "Pending?" When will they be fulfilled?
Is there a documentation regarding this that I can read on?
Thanks a lot! / comments
Hmmm... there are 5 records that even though they were already showing a status of "C", earlier, after a while it goes back to "A" and the count increases.
Any idea on how to really stop those, no...
Okay,
I finally was able to script out the SELECT with the correct filter (I probably have written it wrong earlier).
Now that I was able to, although there were (0) affected earlier during the UPDATE, i can see that the status has now been changed/changing to "C"... looks like there may just be a delay with affecting the records. Now there's only few incorrect records that doesn't have "C" which I will view as "Cancel", the rest are in "A" (Attempt?) Hopefully soon they will become "C".
Will keep you posted. / comments
Okay,
I finally was able to script out the SELECT with the correct filter (I probably have written it wrong earlier).
Now that I was able to, although there were (0) affected earlier during the UPD...
Okay, I finally saw the ID's that i needed to apply the second script on:.
The IDs are as follows (I just listed it here also so I hope I won't need to run the first script)
356714, 356716, 356718, 356720, 356722, 356724, 356726, 356728, 356730, 356732, 356734, 356736, 356738, 356740, 356742
When I run the script:
EXEC master..sqbdata 'UPDATE backupfiles_copylist SET status = ''C'' WHERE ID = 356716'
Result is: (0 row(s) affected) [image] Please help! I hope it stop retrying soon. / comments
Okay, I finally saw the ID's that i needed to apply the second script on:.
The IDs are as follows (I just listed it here also so I hope I won't need to run the first script)
356714, 356716, 356718,...
Thanks a lot Peter... I am just soooo glad to know that there is a way out of this.
I'm doing the first query for now. I tried passing in some filter for the SELECT query because it looks like its listing out things that has copyto clause from the beginning that redgate backup was used.
Is there a way to apply filter to this statement? Like filter by COPYTO (I can see the wrong path from the hundreds of email that I have been receiving.
How many retry attempt will this do?
Thanks a lot! / comments
Thanks a lot Peter... I am just soooo glad to know that there is a way out of this.
I'm doing the first query for now. I tried passing in some filter for the SELECT query because it looks like its...
SQL Log backups with COPYTO (How to Stop the retries)
I have executed a script for log backups without a DISKRETRYCOUNT, with a COPYTO section. However, the path that was given was incorrect and the script kept on retrying and retrying. How can I st...
hi Pete,
On this server, we have log-backup occuring every 15 minutes, and there are 5 databases that is also mirrored (high-safety mirroring) to another DB server. Aside from those activities, there's really not much going on at that time-frame.
Would you recommend a different set of steps for the FULL backup and the VERIFY backup? I'm not sure if that would help, but my goal for that is to isolate the result of those two. It's kind of alarming to see that the FULL backup fails everyday although it was actually the VERIFY that did error out.
Thanks a lot! / comments
hi Pete,
On this server, we have log-backup occuring every 15 minutes, and there are 5 databases that is also mirrored (high-safety mirroring) to another DB server. Aside from those activities, th...
Hello, Red-gate support.
This problem continues to happen where the log would show as:
Main: SQL Backup required 0 bytes of free SQL Server memory, which was not available.
This is normally during verification. When I do a manual verify of the file that was created, it shows that the backup file is valid. However, this is an additional manual process and resolving the issue about requiring 0 bytes of free SQL Server memory can probably help out a lot.
Email notification:
7/18/2010 8:41:04 PM: VDI error 1010: Failed to get the configuration from the server because the timeout interval has elapsed. SQL Backup required 0 bytes of free SQL Server memory, which was not available. VDI error: An abort request is preventing anything except termination actions.
7/18/2010 8:41:04 PM: SQL error 3013: VERIFY DATABASE is terminating abnormally.
7/18/2010 8:41:04 PM: SQL error 18210: BackupVirtualDeviceSet::Initialize: Request large buffers failure on backup device 'SQLBACKUP_BF059D37-01AF-4A5A-8D75-E91CC6ACAF21'. Operating system error 0x8007000e(Not enough storage is available to complete this operation.).
7/18/2010 8:41:04 PM:
7/18/2010 8:41:04 PM: Memory profile
7/18/2010 8:41:04 PM: Type Maximum Minimum Average Blk count Total
7/18/2010 8:41:04 PM:
7/18/2010 8:41:04 PM: Commit 296353792 4096 158056 7608 1202491392
7/18/2010 8:41:04 PM: Reserve 4190208 4096 182621 5066 925159424
7/18/2010 8:41:04 PM: Free 458752 4096 55062 359 19767296
7/18/2010 8:41:04 PM: Private 296353792 4096 167533 11874 1989296128
7/18/2010 8:41:04 PM: Mapped 1060864 4096 112364 171 19214336
7/18/2010 8:41:04 PM: Image 24948736 4096 189412 629 119140352
7/18/2010 8:41:04 PM: / comments
Hello, Red-gate support.
This problem continues to happen where the log would show as:
Main: SQL Backup required 0 bytes of free SQL Server memory, which was not available.
This is normally during...