Category Archives: Backups

SQL Exceptions: Recovery Model change needed KB1039209

KB1039209

SQL Exceptions: Recovery Model change needed

When dealing with Symantec Backup Exec you will come across SQL Exceptions like this one below. (This exception is for Reliable Property Services, the database names are different per company.)

Backup- DB.RELIABLEINC.LOCALMSSQLSERVER
V-79-40960-37914 – Database SMIowaJulyTest is configured to maintain transaction logs.  Transaction log backups are not being performed.  This will result in the log growing to fill all available disk space.  Regular log backups should be scheduled or the database should be changed to the simple recovery mode.

To fix this follow these steps:

  1. After connecting to the appropriate instance of the SQL Server Database Engine, in Object Explorer, click the server name to expand the server tree.
  2. Expand Databases, and, depending on the database, either select a user database or expand System Databases and select a system database.
  3. Right-click the database, and then click Properties, which opens the Database Properties dialog box.
  4. In the Select a page pane, click Options.
  5. The current recovery model is displayed in the Recovery model list box.
  6. Optionally, to change the recovery model select a different model list. The choices are FullBulk-logged, or Simple.
  7. Click OK.

This will clear the exception for the next backup. If there are any issues or you have questions please feel free to ask.

Checkpoint Restart Error in Backup Exec 2012 KB1039201

KB1039201

Checkpoint Restart Error in Backup Exec 2012

When a backup fails and the error message is as follows (this applies to Backup Exec 2012):

Checkpoint restart cannot be applied to the restarted backup job. The backup job will not run.
Checkpoint restart cannot be applied to the following resource:
Description:
SERVERNAME.domain.comC:, SERVERNAME.domain.com E:, SERVERNAME.domain.com System?StateBackup Exec will not follow mount points, junction points, and symbolic links when the Simplified Disaster Recovery indicator is ON.

To address this please follow the steps below:

      1. Click on the Backup Exec button

1

      1. Click on the Configuration and Settings option as shown below”

2

      1. Then click on error handling rules as shown below:

3

      1. In the Error Handling Rules screen click on Checkpoint Restart (1), then Edit (2)

4

      1. Uncheck the box at the top for Enable error-handling rule as shown below.

5

      1. Press ok at the bottom of the screen
      2. As long as the Checkpoint Restart is set to no in the Enabled column you can close the box and be done:

6

Error: V-79-10000-11217 – AOFO KB1039195

KB1039195

Error: V-79-10000-11217 – AOFO: Initialization failure on: “ServerMicrosoft Information StoreDatabase”. Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). VSS Snapshot Error. The Microsoft Volume Shadow Copy Service (VSS) snapshot failed. Make sure that all provider services and tasks are running. Check the Windows Event Viewer for details.

This error has a couple of common solutions and reasons for it appearing.  Sometimes is can appear when trying to backup a database for Exchange or backup a C: drive.

First thing to look for is if Volume Shadow Copy is running on the server by opening the Task Scheduler from the Start button then click on Administrative Tools.

  1. If there is a task scheduled for the Volume Shadow Copy to run, make sure it doesn’t run the same time Backup Exec is trying to run. (Change the time accordingly)
  2. If Volume Shadow Copy is not running, Open Backup Exec.
  3. Click on the Job Monitor tab at the top.
  4. Locate the job that failed and right click on the job and select Properties
  5. It will bring up a window that will look similar if not like the photo. (Figure 1)

Figure 1

1

  1. Click on the option on the left that says Advanced Open File. (Figure 2)

Figure 2

2

  1. If the box is checked that says Use Advanced Open File Option make sure the option under that for Automatically select open file technology is marked. (Figure 3)

Figure 3

3

  1. Press Submit and let the job run and see what happens. If it fails again then re-open the properties as you did earlier and instead of the bullet that is marked for Automatically select open file technology, mark the option for Microsoft Volume Shadow Copy Service, make sure the provider is left at Automatic and Submit the job again. (Figure 4)

Figure 4

4

  1. If the job fails a second time, open the properties again and uncheck the Use Advanced Open File Option and press Submit

(This should stop the errors for coming back and if it doesn’t might have to contact Symantec Partner Support at 1-888-780-7962, press option 2 the option 1 and you should be able to reach a tech quickly.)

Symantec Backup Exec error V-79-57344-33928 “Access denied” or “Access is denied” KB1039188

KB1039188

Symantec Backup Exec error V-79-57344-33928 “Access denied” or “Access is denied”

 **(Before creating an account in Backup Exec please create a copy of the administrator in Active Directory User and Computers called beadmin or backup exec. You will use this account username and password in creating the logon account in Backup Exec)** -valid for all version of Backup Exec.

To create a new login account:

  1. Open the Logon Account Manager from the Network drop-down menu by selecting Network | Logon Accounts
  2. Click New to create a new logon account (Figure 1)

Figure 1

1

 

  1. Specify the user name and password for an account with at least local administrative rights to the target backup selections. You will use the account you’ve just created in Active Directory for this username and password. (Figure 2)

Figure 2

2

 

  1. Specify a description for this login account. The description should indicate the purpose of the login account i.e. DomainUsername as shown in Active Directory, this makes a difference with how you can use this account.
  2. The Notes field is optional and may be used to further describe the login account, but it is not needed.
  3. Deselect the Restricted Logon Account check box, as that option can cause more problems than fixes. If the account is restricted and we do not have the password, it can create another issue and might have to re-create a new user.

 

  1. Select Default Logon Account to make this account the default account for all newly selected resources.

Symantec Backup Exec error V-79-57344-33928 “Access denied” or “Access is denied” KB1039182

KB1039182

Symantec Backup Exec error V-79-57344-33928 “Access denied” or “Access is denied”

**Before trying this troubleshooting, please try logging in as the user that might be beadmin or BackupExec. Please try logging into the server the credentials, if provided.**

 

To change the logon account for a resource:

1.  Go to the Job Monitor tab, right click, select properties and open the job which contains the resource to which credentials are to be changed.

2.  Select Resource Credentials from the job properties located on the left.

3.  Select the resource to be modified and click the Change button to open the Logon Account Selection screen (Figure 1)

Figure1

1

4.  Select the logon account to be assigned to the resource and click OK to finalize the selection. (Figure 2)

Figure 2

2

5.  Select Test All from the job properties and confirm the credentials have succeeded with the tests. Job will not work/run without valid credentials. For all resources the test should be successful. (Figure 3)

Figure 3

3

6.  After the test is successful, click Submit to save the job.

7.  Try running a job to make sure it will complete by right clicking on the job and click on Test Run. This will confirm it should be ok to run as scheduled. (Figure 4)

Figure 4

4

8.  The test run should complete. If it still fails you might have to recreate a new user with in Active Directory and Symantec Backup Exec.