userid@avamar_grid> avmaint gcstatus
Sunday, September 16, 2012
To kill Garbage collection manually through command line
user@avamar_gridname> avmaint -ava gckill
if the avamar has Datadomain then kill this process after gckill ran and gc still running.
user@avamar_gridname> ps -ef|grep ddrmaint
and "kill -9 process_id"
-9 is to kill forcibly.
if the avamar has Datadomain then kill this process after gckill ran and gc still running.
user@avamar_gridname> ps -ef|grep ddrmaint
and "kill -9 process_id"
-9 is to kill forcibly.
Avamar passwords
To find out Avamar passwords, goto
more /usr/local/avamar/var/mc/server_data/prefs/mcserver.xml and grep for userid's like MCUser/root/dpn
more /usr/local/avamar/var/mc/server_data/prefs/mcserver.xml and grep for userid's like MCUser/root/dpn
Monday, July 2, 2012
Wednesday, June 6, 2012
replicating client level from command line
nohup replicate --flagfile=/usr/local/avamar/etc/repl_cron.cfg --timeout=0 --include=/clients/client_name --logfile=/tmp/replication3.log >> /tmp/replication3.log
Wednesday, May 30, 2012
To know the grids configuration about GC, CP, Readonly
admin@avamar_grid01:~/>: avmaint --ava config | grep disk
disknocreate="90"
disknocp="96"
disknogc="87"
disknoflush="94"
diskwarning="50"
diskreadonly="65"
disknormaldelta="2"
diskfull="30"
diskfulldelta="5"
balancelocaldisks="false"
admin@avamar_grid01:~/>
disknocreate="90"
disknocp="96"
disknogc="87"
disknoflush="94"
diskwarning="50"
diskreadonly="65"
disknormaldelta="2"
diskfull="30"
diskfulldelta="5"
balancelocaldisks="false"
admin@avamar_grid01:~/>
Monday, April 23, 2012
Avamar windows system state backup failure.
One of the work around for system state backups. First install the New 6.0.1-66 client - AvamarClientWindows-x86_x64-6.0.101-66._HF34148.msi or later versions on the windows client.
Symptom
System state backup failed with the following error message:
"System writer is not found"
In addition, when you run the “Vssadmin list writers” command to display VSS writers on the system, the System Writer is missing.
Cause
The system writer fails due to the fact that the trusted installer & system accounts are missing permissions to files in the directory %windir%\winsxs\filemaps\.
Resolution
To resolve this issue, please run the following commands from an administrative elevated Command Window:
CD c:\windows\system32
Takeown /f %windir%\winsxs\filemaps\* /a
icacls %windir%\winsxs\filemaps\*.* /grant "NT AUTHORITY\SYSTEM:(RX)"
icacls %windir%\winsxs\filemaps\*.* /grant "NT Service\trustedinstaller:(F)"
icacls %windir%\winsxs\filemaps\*.* /grant "BUILTIN\Users:(RX)"
Applies to
Windows Server 2003, Windows Server 2008
Symptom
System state backup failed with the following error message:
"System writer is not found"
In addition, when you run the “Vssadmin list writers” command to display VSS writers on the system, the System Writer is missing.
Cause
The system writer fails due to the fact that the trusted installer & system accounts are missing permissions to files in the directory %windir%\winsxs\filemaps\.
Resolution
To resolve this issue, please run the following commands from an administrative elevated Command Window:
CD c:\windows\system32
Takeown /f %windir%\winsxs\filemaps\* /a
icacls %windir%\winsxs\filemaps\*.* /grant "NT AUTHORITY\SYSTEM:(RX)"
icacls %windir%\winsxs\filemaps\*.* /grant "NT Service\trustedinstaller:(F)"
icacls %windir%\winsxs\filemaps\*.* /grant "BUILTIN\Users:(RX)"
Applies to
Windows Server 2003, Windows Server 2008
Subscribe to:
Posts (Atom)