|
Size: 3187
Comment:
|
Size: 3428
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 41: | Line 41: |
| => SQL> STARTUP NOMOUNT | {{{ => SQL> STARTUP NOMOUNT pfile='/u01/xxx.ora' |
| Line 45: | Line 46: |
| RMAN> restore controlfile from | RMAN> restore controlfile from '/tmp/xxx'; }}} |
| Line 47: | Line 49: |
| RMAN> mount database | {{{ RMAN> mount database SQL> SELECT NAME,FILE#,STATUS FROM V$DATAFILE; |
| Line 55: | Line 61: |
| set newname for datafile 1 to '/data/lsdb/datafile/system01.dbf' set newname for datafile 2 to '/data/lsdb/datafile/sysaux01.dbf' |
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
- Make sure you have installed Oracle with the same user as used on the original source client machine
Install NetBackup Client and Oracle agent
- Patch if needed
Touch the file on the master server: => /usr/openv/netbackup/db/altnames/No.Restrictions
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
- 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';
- Restore the database (in MOUNT mode)
RMAN> mount database SQL> SELECT NAME,FILE#,STATUS FROM V$DATAFILE; 8. Restore the database using the script in /usr/openv/netbackup/ext/db_ext/oracle/samples/rman/database_restore.sh {{{ 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; 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
