Advertisements

Uncategorized

  • August 8, 2012

    Spotify Review

    Advertisements
  • STATUS CODE 2: Microsoft SQL backups fail with a NetBackup Status Code 2 “none of the requested files were backed up” SQL Client Configuration: 1. Configure the NetBackup client service (Admin ToolsServices) to run as the account that you are logged in as and then restart the service (Figure 1). Figure 1 2. Open the NetBackup MS SQL GUI a prompt to ‘set your DBMS Login Parameters‘ will appear.  Reenter the same account info that the NetBackup client service is running as (Figure 2). Figure 2 3. Choose ActionsBackupDatabase and select the database(s) to be backed up, enter the policy name (this is optional) and select ‘save for later execution‘ and then click on OK.  Enter a file name and then save.  If the script is saved in the default location, only the script name is necessary to be referenced in the policy. 4. Client configuration portion is now completed, please perform the next steps from the NetBackup Administration Console. MS-SQL-Server Policy Configuration: 1. OpenCreate a MS-SQL-Server policy.  Verify that the Default-Application-Backup schedule is set to 24 x 7 and add a new schedule type ‘automatic backup‘ and set the start window to the desired schedule in which SQL backups are to be run. 2. On the Clients tab addverify that the client name is entered correctly. 3. On the Backup Selections tab, enter the name of the backup script that was created on the client (i.e. backup.bch).  NetBackup will look for this script in the default location on the client to run it. NOTE:  If backing up multiple clients with a single policy then there must be a common script name on each of the clients listed!  The contents of each script will be unique for each client. For example: a policy exists on one SQL client with a script named DailyFull.bch in the default directory of ‘C:Program FilesVERITASNetBackupDbExtMsSql‘.  A month...