|
|
| (8 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | <source lang="text">
| |
| − | /bpimagelist -U -client client1 -d 12/01/2011 -e 12/25/2011
| |
| − | bpdbjobs -report
| |
| − | bplist -R 99 -C womble -l -k womble_disk -t 5 -s 11/29/2010 09:00:00 -e 11/29/2010 09:45 -I "/" ( t 5 worked for Windows )
| |
| − | bplist -R 1 -C haries -I "/"
| |
| − | bpplclients -allunique -l
| |
| − | ## From web examples
| |
| − | I would like to propose a set of "golden rules" for bplist command:
| |
| − | 1. Always specify policy type (-t).
| |
| − | 2. Always provide relevand data range (-s, -d).
| |
| − | 3. Mind the listing recursiveness (-R) as it may be too verbose when you just put the "/" or it may not show anything for non-file like backup types.
| |
| − | 4. Provide as many other details as possible to speed up the search.
| |
| − | Template for good examples:
| |
| − | bplist -C <ClientName> -S <MasterServer> -t <PolicyType> -k <PolicyName> -s MM/DD/YYYY HH:MM:SS -e MM/DD/YYYY HH:MM:SS -R /
| |
| − | That may result in something like:
| |
| − | bplist -C MyClient -S MyMaster -t 4 -k OraclePolicyName -s 08/08/2014 08:00:00 -e 09/09/2014 08:00:00 -R /
| |
| − | >> bpclimagelist -U -client server1-bak
| |
| | | | |
| − | </source>
| |
| − | '''Some good stuff here :''' http://nixguru.wordpress.com/2012/11/21/netbackup-important-commands-and-explanations/<br>
| |
| − | nbemmcmd -listmedia -mediaid AAA030<br>
| |
| − | bppllist ( lists the policies ) <br>
| |
| − | bpimagelist -d 10/01/2014 -e 10/30/2014 -policy haries_UR3_4<br>
| |
| − | bperror<br>
| |
| − | bperrror –U –problems –hoursago 1<br>
| |
| − | bperror –U –backstat -by_statcode -hoursago 1<br>
| |
