Forum Discussion

Contonso's avatar
Contonso
Level 4
13 years ago

'TRUNCATE_ONLY' is not a recognized BACKUP option.

Hello together,

we have moved our EV Databases to a new SQL server yesterday.

Some details about our environement:

EV 9.01. for Exchange. New SQL server is a SQL 2008 x64 R2.

From the compatibility charts I could see that SQL 2008 x64 is supported with EV9.

The problem what we have is with the Backup.

Since the move the Logs display the error: "'TRUNCATE_ONLY' is not a recognized BACKUP option."

It seems that SQL 2008 does not support the command TRUNCATE_ONLY.

How can I solve this? Has anyone any idea?

Thanks & Regards

  • If you are looking for how to set this up properly ... there are several ways. Here is a support provided cookbook that will properly maintain your SQL server in every way (not just truncate the log)

     

    http://www.symantec.com/business/support/index?page=content&id=TECH74666

     

    This is tried and true.

     

    If this suggestion or any of the above resolved your issue .... please mark it as such

     

  • Check here:

    http://madhuottapalam.blogspot.com/2008/05/faq-how-to-truncate-and-shrink.html

    In SQL Server this process have been changed. In 2008, just change the recovery model to simple and then use DBCC SHrinkfile command.

    select name,recovery_model_desc from sys.databases
    GO
    Alter database YourDatabaseName Recovery simple
    GO
    Declare @LogFileLogicalName sysname
    select @LogFileLogicalName=Name from sys.database_files where Type=1
    print @LogFileLogicalName

    DBCC Shrinkfile(@LogFileLogicalName,100)

  • Hi ZeRoc00L,

    Thanks for reply.

    Are you sure, that I can easyl change the recovery model of EV Databases? I do remember that it was not recomended to change the recovery model settings.

    Regards

  • Just do a "real" transaction log backup and the log should be truncated afterwards, what won't happen is that the file size will not be smaller unless you do a shrink.

    However you'll get white space in the transaction log file so it will use that space first before the file will grow further.

  • If you are looking for how to set this up properly ... there are several ways. Here is a support provided cookbook that will properly maintain your SQL server in every way (not just truncate the log)

     

    http://www.symantec.com/business/support/index?page=content&id=TECH74666

     

    This is tried and true.

     

    If this suggestion or any of the above resolved your issue .... please mark it as such