Sunday, May 29, 2011
Saturday, May 28, 2011
Emc Legato networker MMINFO usefull TIPS
Here some of use full combinations of mminfo
Generally mminfo resides in /usr/sbin in unix, c:\programfiles\legato\nsr\bin in windows .
To query a client backup info for past 120 Hours:
/usr/sbin/mminfo -avot -c axx.domain.com -t "-120 hours"
some times we can use grep effectively with networker command :
for example above command we can use in alternative way:
/usr/sbin/mminfo -avot -t "-120 hours" | grep -i axx.domain.com
To Query a client backup info with ssid , size of saveset, tape info
mminfo -q "client= axx.domain.com" -r "ssid,name,totalsize,savetime,volume" -t '60 hours ago'
Generally mminfo resides in /usr/sbin in unix, c:\programfiles\legato\nsr\bin in windows .
To query a client backup info for past 120 Hours:
/usr/sbin/mminfo -avot -c axx.domain.com -t "-120 hours"
some times we can use grep effectively with networker command :
for example above command we can use in alternative way:
/usr/sbin/mminfo -avot -t "-120 hours" | grep -i axx.domain.com
To Query a client backup info with ssid , size of saveset, tape info
mminfo -q "client= axx.domain.com" -r "ssid,name,totalsize,savetime,volume" -t '60 hours ago'
Basic Trouble shooting in EMC Legato Networker
If a client backup failed in EMC legato networker these setups helps you.
# /usr/sbin/ping xxx.abc.com
xxx.abc.com is alive
It is confirms that client is ping able so we can move for second step.
# /usr/bin/rpcinfo -p xxx.abc.com
program vers proto port service
100000 2 tcp 7938 rpcbind
100000 2 udp 7938 rpcbind
390436 1 tcp 9101
390435 1 tcp 8920
390113 1 tcp 7937 nsrexec
By this out put it is confirm that nsrexec running on client.
# /usr/sbin/nsradmin -s xxx.abc.com -p 390113
nsradmin> print nsrla
type: NSRLA;
name: xxx.abc.com;
NW instance info operations: ;
NW instance info file: ;
installed products: NetWorker 7.4.3.Build.569;
version: "EMC NetWorker 7.4.3.Build.569 ";
servers: backup.abc.com;
auth methods: "0.0.0.0/0,nsrauth/oldauth";
administrator: No privilege to view administrator list;
kernel arch: AMD_X8664;
machine type: server;
OS: Windows Server 2003 5.2;
NetWorker version: 7.4.3.Build.569;
client OS type: Windows NT Server on Intel;
CPUs: 8;
MB used: 23525;
IP address: 10.206.1.24, 192.168.41.12;
Above out put may gives the clue about the ip interface and client version which helps you out in trouble shooting.
# /usr/sbin/ping xxx.abc.com
xxx.abc.com is alive
It is confirms that client is ping able so we can move for second step.
# /usr/bin/rpcinfo -p xxx.abc.com
program vers proto port service
100000 2 tcp 7938 rpcbind
100000 2 udp 7938 rpcbind
390436 1 tcp 9101
390435 1 tcp 8920
390113 1 tcp 7937 nsrexec
By this out put it is confirm that nsrexec running on client.
# /usr/sbin/nsradmin -s xxx.abc.com -p 390113
nsradmin> print nsrla
type: NSRLA;
name: xxx.abc.com;
NW instance info operations: ;
NW instance info file: ;
installed products: NetWorker 7.4.3.Build.569;
version: "EMC NetWorker 7.4.3.Build.569 ";
servers: backup.abc.com;
auth methods: "0.0.0.0/0,nsrauth/oldauth";
administrator: No privilege to view administrator list;
kernel arch: AMD_X8664;
machine type: server;
OS: Windows Server 2003 5.2;
NetWorker version: 7.4.3.Build.569;
client OS type: Windows NT Server on Intel;
CPUs: 8;
MB used: 23525;
IP address: 10.206.1.24, 192.168.41.12;
Above out put may gives the clue about the ip interface and client version which helps you out in trouble shooting.
HP Data Protector CRS Service Errors.
Can not start "crs" service, system error: [1053] 1053 Unknown Error Can not start "uiproxy" service, system error: [1053] 1053 Unknown Error.
Above error happens in Linux , if you miss glib packages. it is known issue with Data protector.
Crs account may not started due to one more reason:
If installation user account password changed it will not start .
Above error happens in Linux , if you miss glib packages. it is known issue with Data protector.
Crs account may not started due to one more reason:
If installation user account password changed it will not start .
Friday, February 18, 2011
PUBLIC & PRIVATE option in backup sepecfication.
If you want to give restore permission other than backup owner or owner group or any user.
we must select PUBLIC option in bakcup specification, this allows permitter user /admin group member to restore backup data.
we must select PUBLIC option in bakcup specification, this allows permitter user /admin group member to restore backup data.
Saturday, February 12, 2011
HP Data Protector CRS Cell Request Service How it works
Hi
Who is the owner of backup ?
CRS (Cell Request Service ) is the owner for all backups in HP data protector. because CRS is the intiator for all backup specifications (Except Some of BAR applications )
Why we add DBA system user in backup admin group ?
Bacause this account acts as CRS for this accounts.
What happens if CRS account is changed and it is not update in Data protector user list ?
No backu will initiated :(
Who is the owner of backup ?
CRS (Cell Request Service ) is the owner for all backups in HP data protector. because CRS is the intiator for all backup specifications (Except Some of BAR applications )
Why we add DBA system user in backup admin group ?
Bacause this account acts as CRS for this accounts.
What happens if CRS account is changed and it is not update in Data protector user list ?
No backu will initiated :(
Monday, January 3, 2011
Wish You a Happy New Year
SHARE YOUR KNOWLEDGE.....................................
Please send me an email who want share some knowledge on my blog. i will add them as my team so you can directly write the post on my blog.
Please send me an email who want share some knowledge on my blog. i will add them as my team so you can directly write the post on my blog.
Subscribe to:
Posts (Atom)