No idea why it was set up this way, but I assume it's unnecessary.Īny ideas, contributions, or suggestions are welcome. In other words, I think there's some redundancy here - the job is touching the databases at the SQL level via the SQL agent, and it's touching the databases and log files at the file system level. And these backups are done at the file system level, but in addition the full SQL backup also has the database itself selected in BackupExec.
MDF SQL file itself, it also backs up the corresponding. On a sidenote, the full SQL backup backs up not only the. I was hoping someone familiar with Enterprise Vault, or at least someone familiar with backing up SQL databases via BackupExec, could speak up and give me his/her opinion. If there an earlier version of Hitachi Content Platform Adapter for Veritas Enterprise Vault installed on the Enterprise Vault Server, uninstall it from the Windows Programs and Features Control Panel. Now I'm really not familiar with SQL, and the above message does not even mention SQL 2005 (my version), nor do I know what altering the configuration of the databases might do. Stop Enterprise Vault Storage Services and Task on the Enterprise Vault Server.
A new full backup should be performed if these settings are changed before a log backup is run. To change the configuration use Enterprise Manager to set the recovery mode to FULL in SQL 2000 or turn off the 'trunc on chkpt' option in SQL 7. V-79-57344-33960 - A log backup was attempted on a database that is not currently configured to support log backups. Only full backups can be performed on the master database. V-79-57344-33959 - The SQL Server master database does not support log backups.
0 kommentar(er)
