Sharepoint backup versus SQL backup and status 1

[Fr_d_ric_Verbey]

Hello,

Does someone already solved the issue: "SharePoint does not truncate SQL transaction log" like explained here: http://www.veritas.com/community/forums/sharepoint-farm-backup-doesnt-truncate-sql-logs?

I like to understand how you solved the satus 1 on the SharPoint Incremental bakup?

Every time I back up SQL with another backup than the SharePoint NBU Intergrated the next incremetal reports a status 1 "can't open object SQl-DB".

So if we need two "tools/backups methods" to protect SharePoint we always will get a status 1 on the next SharePoint backup.  How can we do to get a status 0 on the next SharePoint Incremental?

Thank you in advance.

Cheers,

Fred

[Will_Restore]

Link is for Backup Exec not NetBackup product.

We have not had an issue with NetBackup for SharePoint once it has been properly configured and tested using the sharepoint check utility.

[Fr_d_ric_Verbey]

Hi Will,

Thank you for your answer.

My bad.  I copy/paste the wroing one...

Here are correct ones:

https://www.veritas.com/support/en_US/article.000041289

https://www.veritas.com/support/en_US/article.000082430

https://www.veritas.com/support/en_US/article.000081902

The cutomer wants to flush the transaction log with non-GRT backups but every day (full week-end and incremental week days).

Backuping only with SharePoint does not flush the transaction log

Backuping the transaction logs appart works to flush them but reports an error (status 1) on the next incremental backup

For sure, the last link offer a workaround but only for FULL.   The customer wants to flush the logs on incremental too and avoid the  status 1.

How can we flush the trasaction log every day prior or post the regular NetBackup backup without reporting a status 1?

Thank you

Fred

[Mark_Solutions]

From what all of that says i am afraid it cannot be done in the way you would like

You need to do a Full SharePoint backup every day if you need to flush the transaction logs everyday ... or live with the Status 1 messages.

I dont see anything as a workaround for this .. even it it were virtualised to backups via the vSphere API you wouldnt be able to do incremental backups so would end up with Full backups anyway.

It looks like you need full backups or status 1's .. i would think that if there was another option then Veritas would have addressed it by now

[Will_Restore]

Right.  I think the latter workaround might be best in this case.

https://www.veritas.com/support/en_US/article.000081902

[Michal_Mikulik1]

Hello,

agreed with posts above and with the last workaround link. In other words, SQL log truncation must be performed just before the next Sharepoint FULL backup, not between Sharepoint incremental backups.

Retry to discuss the reason for DAILY log truncation requirement with the customer - I doubt that log generation is so intensive that it must be done daily...

Regards

Michal