Re: FastCompression Alert: 62405 : FastCompression backup sequence has failed...
David, We have a winner! It turns out that this database had been restored, and that is what threw off the LSN verification. LiteSpeed handled this exactly as it should. It saw that there was an...
View ArticleRe: FastCompression Alert: 62405 : FastCompression backup sequence has failed...
Mark, I need to ask you to open a support case. This is going to require a bit more analysis than we can probably do via the forums. One question though: Have you restored any backups of that database...
View ArticleClik here to view.
Re: FastCompression Alert: 62405 : FastCompression backup sequence has failed...
Intestingly, the LiteSpeed console show that the error is for a different database than shown in the SQL Server log (no doubt due the truncation of the message in that log): LiteSpeed for SQL Server...
View ArticleRe: FastCompression Alert: 62405 : FastCompression backup sequence has failed...
Re-run Instance Configuration on the server itself. Instance Configuration is located in the Quest Software - LiteSpeed for SQL Server Start Menu group. It's a good idea to re-run to ensure you have...
View ArticleRe: FastCompression Alert: 62405 : FastCompression backup sequence has failed...
Once the LiteSpeed Activity Service is running, the first backup will trigger the information in the LiteSpeedLocal that has not yet been reported to the LiteSpeedCentral to update. This first update...
View ArticleRe: FastCompression Alert: 62405 : FastCompression backup sequence has failed...
I had a login failure when I tried to re-run Instance Configuration. I contacted my domain admin and got this response: "The account was disabled, probably due to inactivity. It has been re-enabled."...
View ArticleRe: FastCompression Alert: 62405 : FastCompression backup sequence has failed...
I would recommend you re-run Instance Configuration and make sure your instance is set up correctly to report to the repository. Once that is set up, you should start seeing backup and restore activity...
View ArticleRe: FastCompression Alert: 62405 : FastCompression backup sequence has failed...
I was going to bring this up in a separate post, but I don't see anything in the console for LiteSpeed Activity since 10/22/13 (Period: All, Report type: Backup/Restore/Verify/Check, Status: All,...
View ArticleRe: FastCompression Alert: 62405 : FastCompression backup sequence has failed...
No ad-hoc backups have been done on this server. Backup escalation is enabled. This is a tiny database which rarely changes. It is an empty shell, having a large schema but no data. It runs in simple...
View ArticleClik here to view.
Re: FastCompression Alert: 62405 : FastCompression backup sequence has failed...
You can also see where the error occurred from LiteSpeed Activity in the console by double-clicking the error and viewing the Results tab:
View ArticleRe: FastCompression Alert: 62405 : FastCompression backup sequence has failed...
The error means there was a validation error detected by Fast Compression before any backups were run. We check the curretn backup set and make sure all the backups that are on disk match what's...
View ArticleFastCompression Alert: 62405 : FastCompression backup sequence has failed LSN...
I had received two emails from one of my servers over the weekend. The first tells me that a LightSpeed backup job failed: JOB RUN: 'LiteSpeed Backup Template Vertex Fast Compression User...
View ArticleRe: Netvault Litespeed for SQL Server licensing and differences
Your sales rep will discuss all options with you. Thanks.
View ArticleRe: Netvault Litespeed for SQL Server licensing and differences
Thanks for the prompt response, David. So, will the option to select/request Enterprise (or any other edition for that matter) appear while requesting a quote/trial? Thanks
View ArticleRe: Netvault Litespeed for SQL Server licensing and differences
We license by CPU or by Instance. CPU is best for most virtual environements since it allows for unlimited VM use as long as the host CPUs are licensed. For physical environments, the instance...
View ArticleNetvault Litespeed for SQL Server licensing and differences
Hello, I found this thread on the community http://communities.quest.com/message/66120#66120 before posting this but apparently, there was no follow up/answer to it since the topic creator never...
View ArticleRe: Difference in differential backup sizes
Thanks a lot David ! This was very helpful.
View ArticleRe: Difference in differential backup sizes
My guess is the SAN replication has VSS support in Windows that is triggering the SQL Server VSS Writer at backup time. The VSS Writer is effectively creating a snapshot on the database and running a...
View ArticleRe: Difference in differential backup sizes
That's correct. Many SAN snapshot capabilities leverage VSS for transactionally consistent backups. Running an "out-of-band" full backup from the SAN changes the differential base, meaning that future...
View ArticleRe: Difference in differential backup sizes
I think i misleaded you by quoting wrong words. Sorry for that. Backups are not corrupted. It caused SQL to backup incorrectly when doing differentials. For some reason in our environment SAN...
View Article
![ONEW – KAKERA -Unmei no Piece- – EP [iTunes Plus M4A]](http://is1-ssl.mzstatic.com/image/thumb/Music221/v4/d0/fb/86/d0fb86a5-ba60-4bea-41fb-7f54c125f518/VEATP-45908.jpg/296x296bb.webp)
/pic9814888.png)
