delete Veritas netbackup client

/usr/openv/netbackup/bin/bp.kill_all

Delete /usr/openv

Remove entries from /etc/services

Remove entries from /etc/inetd.conf

Step-by-step configuration of NetBackup for Microsoft SQL Server differential backups

https://www.veritas.com/support/en_US/article.000033118

Step-by-step procedure for using NetBackup to restore a Microsoft SQL Full Backup using a MOVE script

https://www.veritas.com/support/en_US/article.000033126

How to configure a NetBackup policy to protect Microsoft SQL databases?

http://www.settlersoman.com/how-to-configure-a-netbackup-policy-to-protect-microsoft-sql-databases/

NBU restore script

• recovery catalog (if used). At the rman command prompt, enter the following:

crosscheck backupset of database;

Use restore ... validate when you want RMAN to choose the backups to test.

NetBackup 7.7.1 AdministratorGuide => 131 to 138 pages

https://www.veritas.com/support/en_US/article.HOWTO64200

1. Make sure you have installed Oracle with the same user as used on the original source client machine

2. Install NetBackup Client and Oracle agent

3. Patch if needed

4. Touch the file on the master server: => /usr/openv/netbackup/db/altnames/No.Restrictions

5. Browse the Oracle backups by running /usr/openv/netbackup/bin/bplist -S <master server> - C <Oracle source client name> -t 4 -l -R /

   • => Make sure you can browse the backups

6. Restore the control file (in NOMOUNT mode) - See exact steps for this procedure in technote HOWTO63971

   •    => SQL> STARTUP NOMOUNT pfile='/u01/xxx.ora'
       rman nocatalog
        => RMAN> connect target 
        => RMAN> SET DBID=XXXXXX
           RMAN> restore controlfile from '/tmp/xxx';

7. Restore the database (in MOUNT mode)

    RMAN> mount database
    
   
    8. Restore the database using the script in /usr/openv/netbackup/ext/db_ext/oracle/samples/rman/database_restore.sh
   {{{
    SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE RESETLOGS;
    ALTER DATABASE RENAME FILE '/old/location' TO '/new/location';
   
    SQL> select log_mode from v$database;
    SQL> select name from v$datafile;
    SQL> select member from v$logfile;
    SQL> select name from v$tempfile;
    SQL> select name from v$controlfile;

8. SQL> SELECT NAME,FILE#,STATUS FROM V$DATAFILE;

RUN {
  ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
  ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
  SEND 'NB_ORA_SERV=<master server>, NB_ORA_CLIENT=<Oracle source client name>’;
  set newname for datafile 1 to '/data/lsdb/datafile/system01.dbf'
  set newname for datafile 2 to '/data/lsdb/datafile/sysaux01.dbf'
  RESTORE DATABASE;
  RECOVER DATABASE;
  sql 'alter database open resetlogs';
  RELEASE CHANNEL ch00;
  RELEASE CHANNEL ch01;
} 

Troubleshooting

NetBackup 7.7.1 AdministratorGuide => 208 pages

/usr/openv/netbackup/logs/user_ops

UNIX: /usr/openv/netbackup/logs/dbclient/log.mmddyy

The debug logs are located in /usr/openv/netbackup/logs .

To set the debug level on a UNIX client
Enter the following line in the bp.conf file.

VERBOSE = X

Where X is the debug level you want.

Modifying the maxjobs for "NBU_POLICY"

• Info nbrb (pid=3037) Limit has been reached for the logical resource <Master server>.NBU_POLICY.MAXJOBS.<Policy name>

you can chage that form your Policy attributes

but do make sure that it will not effect the other jobs... if you increase value there may be a possiblity that other polices run out of resources for backups..

its you need to make sure that ,chaning this value will not impact the other jobs to get the resources..

Select the Policy in the GUI and adjust Limit Jobs per Policy