Bonjour,
J'ai pour toi un document il suffit de chopisir la solution qui s'applique au type de ta panne :
http://www.symantec.com/business/support/index?page=content&id=TECH126063
et voici la solution :
Configure a log backup of the database(s) in question
For Microsoft SQL:
Create a backup with a Backup Method of "Log - Back up Transaction Log". This can be set in the Microsoft SQL section of the backup job properties.
For Microsoft SharePoint:
Create a backup with a Backup Method of "Log - Back up and truncate transaction Log". This can be set in the Microsoft SharePoint section of the backup job properties.
Note: The ability to perform this type of backup was removed in Backup Exec 2012, so this solution pertains only to the version(s) listed in this article. In BE 2012, the error messages can either be ignored, or the recovery model can be changed to "Simple" as suggested in the error message.
For Enterprise Vault:
Create a backup with a Backup Method of "Incremental". This can be set in the Enterprise Vault section of the backup job properties.
To configure this exception to show after a larger number of backups than the default number or not to show the exception the below registry key on the Microsoft SQL Server will need to be adjusted.
Note : -
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec for Windows\Backup Exec\Engine\SQL Server\Number of Non-Log Backups Before Warning
The default value is a decimal value of 10
Increasing this value will increase the number of full database backups it will take to display the exception
Setting the value to 0 will disable this exception from ever occurring. Symantec does not recommend setting this value to 0.
PS:
Si tu n'est pas ok en anglais je peux te traduire ca en Francais
