be 16

3 Topics

Backup Exec 16 Exchange GRT backup error with deduplication
After windows in place upgrade from windows server 2012 R2 to 2016, and BE services started normally and all job are running successfully, except Exchange and VMware GRT backup failed with the following error. Final error: 0xe0001203 - An error occurred while creating or accessing the directory specified for this operation. Check to make sure that the B2D folder and/or the temporary path specified for this operation are valid. V-79-57344-4611 - An error occurred creating or accessing the directory \\.pdvfs\servername\2\BEData specified for this operation. Ensure that the directory is accessible and can be written to. I changed storage from deduplication disk to tape drive and job success . FP 2 and latest HF 128051are installed .
Solved
Ahmed_Shebl1
5 years ago Place Backup Exec
3KViews
0likes
3Comments
Backing up SQL databases and transaction logs Clarification needed.
I am trying to make sense of the following statement from atech article which I will be providing a link below and I am not sure if I am understanding the context properly, "Additionally, Backup Exec runs a full backup when you select the Automatic or Log backup methods if a full backup was not previously run on the database." Does that statement mean that If I have selected the following option, "Log - Back up and truncate transaction log" without scheduling a full backup to run that day it will automatically run a full backup then backup the log and trucate them every day that it is schedule for? or is it referring to only the firstfull backup? The reason why I am asking is the first job backup method is set by default to do a full backup of the entire database. Then the second job you can specify to do one of 9 options from log to copy, full etc.. Lastly by selecting to do a log backup and truncation is it suppose to show up as incremental backup as the Job Type under the for the selected server under backup and restore as seen below? https://www.veritas.com/support/en_US/article.000108901
Solved
Vdang
8 years ago Place Backup Exec
1.2KViews
0likes
1Comment
Upgrade Backup Exec 2010 R3 SP4 To BE 16
Are you currently using Backup Exec 2010 R3 SP4 and planning to upgrade to Backup Exec 16 ? If so, then Veritas recommend you to read this blog and follow the steps before installing Backup Exec 16. Backup Exec supports a direct upgrade from Backup Exec 2010 R3 SP4 to Backup Exec 16. However, specific to 2010 R3 SP4, you need to ensure that your current SQL version is compatible with Backup Exec 16. The Backup Exec 16 Environment Check will block an upgrade , if your implementation is using a local SQL Express instance created by Backup Exec with the name ‘BKUPEXEC’, which is installed with SQL 2005 SP3. Refer to the following screenshot. To avoid this error you must have SQL 2005 SP4 installed, which is compatible with Backup Exec 16. SQL 2005 SP4 version can be installed with Windows updates (if it is enabled on your setup). Make sure your systems are fully patched with Windows updates. You can also download SQL 2005 SP4 from Microsoft: http://www.catalog.update.microsoft.com/Search.aspx?q=KB2463332 To verify that the correct version of SQL is installed on your setup, go to the SQL Server Configuration Manger and select SQL server 2005 services > SQL Server > SQL server (BKUPEXEC) > Properties. The Service Pack Level now displays 4. Note: If you select an existing instance of SQL Server that is not installed by Backup Exec, you must upgrade the SQL Server to SQL 2008 R2 SP2. When you upgrade from previous versions, Backup Exec automatically converts your existing definitions, configurations, and jobs to the current version. Some of your jobs may be combined or moved. After the migration completes, Backup Exec displays the Migration Report that you must review and acknowledge before Backup Exec continues the upgrade process. In this report, you can see how your jobs were migrated. Veritas recommends that you review the Migration Report thoroughly to determine how your existing jobs have changed and how you may need to adjust your jobs manually. The Migration Report is available for viewing from the Backup Exec Administration Console or the Home tab at any time after the migration completes. The Migration Report is stored in the following path: \Program Files\Veritas\Backup Exec\Data\MigrationReportFiles\Data-Migration-Report.html. References Upgrade Bacup Exec 2010 R3 to BE 15 Veritas Backup Exec 16 Version Upgrade Process Upgrading Backup Exec 15 to 16
Yashashree
8 years ago Place Backup Exec
8.8KViews
3likes
0Comments