Backup Fail BE 2015 Trial Version

[Tokyo2040]

Dear,

I am usign the BE 2015 trial version and traid to backup a folder that contains 700 gb and the jobs is complete but no data inside. There some restriccions for a trial version?

In some folder have a sql base, if apply the next KB (https://www.veritas.com/support/en_US/article.TECH92375) is solved the problem ?

[CraigV · Accepted solution]

Are you backing up a folder where SQL DBs are? If this is so, then Backup Exec will automatically skip them due to Active File Exclusion. You need to activate the license for Applications and Databases in order to backup the SQL DBs while live and running, and this also allows you to restore into them while live and running.

This would explain why no files have been backed up, assuming the folder contains SQL DBs (*mdf, *.ldf etc).

Thanks!

[pkh]

It is not recommended that you disable AFE in order to backup .mdf and .ldf files.  You should purchase and install an Agent for Applications and Databases licence, so that you can use the BE SQL Agent to backup the SQL databases.  By using the BE SQL Agent, you can backup the SQL databases on the fly and restore them on the fly.  If you just backup the .mdf and the .ldf files, you might not be able to restore them due to timestamp differences between the database and the Master database.  Also, if you do not shutdown SQL before backing up the .mdf and the .ldf files, then you would end up with an inconsistent database.

Since you are using the trial version, you can test out the SQL Agent option by activating it.  Click on the BE button then click on Installation and Licencing and Install Options and Licences, then follow the dialogs to activate the SQL Agent option.

There are no restrictions on the functionalities when you are using the trial version, but you are limited to 60-days from the day of first use.  After 60-days, unless you put in a proper licence, your jobs will fail.

[Colin_Weaver]

Any data item store in the file system that shoudk be backed up using a specific mechanism can be silently excluded from a file system (drive letter based) backup.

As examples (but not necessarily a complete list)

- SQL MDF and LDF files.

- Exchange EDB, STM and Log files.

- Any files managed by DFSR

- Any files considered to be part of the System State

There are also silent excludes for files that do not need to be backed up (such as the Windows Swap files and possibly the TEMP folder content

As such I know you mentioned SQL but you need to carefully look at what you are trying to backup and then check for the correct backup methods for such data

[Tokyo2040]

Thanks , for your time , the problem is solved apply the step in the KB https://www.veritas.com/support/en_US/article.TECH92375

[Colin_Weaver]

Not really a solution. This just means you did have one of the items that should be backed up using a specific method and are now backing it up using one of the unofficial methods which may give you more complexity during a restore activity (or perhaps  just after a restore activity to make the data accessible)