avmaint nodelist|grep "fs-percent-full"
Wednesday, March 7, 2012
Tuesday, February 21, 2012
Avamar: to activate clients from client side
unix:
/client_pkg_installed/etc/avagent.d register avamar_gridname domain_name
ex:
/usr/local/avamar/etc/avagent.d register avamar01 /clients/unix
windows:
right click on Avamar icon and activate:
fillup avamar grid name and domain name.
Monday, February 13, 2012
Avamar provides fault tolerance at several different levels:
RAID and RAIN protects the data loss.
- RAID: Avamar ensures protection from disk and data corruption through the use of RAID (redundant array of independent disks). The type of RAID depends on the particular node type. The first thing you must know is that all storage nodes have 6 physical disks. Beginning with Avamar release 4.0, two sizes are supported: nodes with 1TB of licensable capacity or 2TB of licensable capacity. Single-node servers with a capacity of 1TB actually have higher performance disks than the 2TB flavor. The 1TB storage nodes are 6 300GB 15k SAS drives setup in RAID-5, configured into 4 Luns (virtual disks). If you opt for the 2TB capacity, the storage node will have 6 SATA disks configured with 3 RAID-1 Luns. Just FYI, the Utility node and NDMP accelerator nodes both only have 2 146GB physical disks configured with RAID-1.
- RAIN: In an multi-node system (1 utility node & 3 storage nodes or more), Avamar provides failover and fault tolerance across all nodes usingRAIN (redundant array of independent nodes). If a node failure occurs, the Avamar Server continues to function, during this time, backup data for recovery will be reconstructed on the remaining nodes using parity. Once the failed node is replaced (a spare node is always included in a RAIN configuration), the capacity across all disks can be rebalanced using a very simple process.
Wednesday, January 25, 2012
Avamar windows open files VSS bug.
<http://powerlink.emc.com/km/appmanager/km/secureDesktop?_nfpb=true&_pageLabel=homePgSecureContentBk >
EMC Solutions
EMC Solutions
Solution ID:
esg122338<http://solutions.emc.com/EMCSolutionView.asp?id=esg122338 >
Product(s):
Avamar Client for Windows
Date Created:
06/14/2011
Category(ies):
Bug or Defect
Date Modified:
06/21/2011
Status:
Approved
Use Count:
0
Related Bugs:
26904
Subject:
ETA esg122338: Avamar Client for Windows: During Windows NTFS backups, the Avamar client software might fail to back up files, folders, and/or volumes and not report the exceptions
Solution:
EMC Technical Advisory
ETA esg122338: Avamar Client for Windows: During Windows NTFS backups, the Avamar client software might fail to back up files, folders, and/or volumes and not report the exceptions
Symptoms
If the Microsoft Volume Shadow Copy Service (VSS) fails during an NTFS backups of Windows clients running Windows 2003 SP1 or more recent Windows versions, then the Avamar Windows file system client software might fail to backup files, folders, and/or volumes without reporting errors for all the files, folders, and/or volumes that did not get backed up.
In some cases the backup might report a "completed" status, which means that no errors were reported during the backup, but might fail to back up an entire volume.
In other cases, the backup might report a "completed with exceptions" status, but entire folders might not be backed up, and not all the relevant exceptions are reported. As a result, the size of the folders that were not backed up is reported in the restore window to be 0 bytes.
In these cases, the Windows system "Event Viewer" will log one or more of the following VSS related errors or warnings during the backup (using volume C: as an example):
=================================
Event Type: Error
Event Source: VolSnap
Event Category: None
Event ID: 35
Date: 4/11/2011
Time: 1:00:21 AM
User: N/A
Computer: CORP-AVAMAR1
Description:
The shadow copies of volume C: were aborted because the shadow copy storage failed to grow.
=================================
Event Type: Error
Event Source: VolSnap
Event Category: None
Event ID: 13
Date: 4/11/2011
Time: 12:59:44 AM
User: N/A
Computer: CORP-AVAMAR1
Description:
The shadow copy of volume C: could not grow its shadow copy storage on volume F:.
=================================
Event Type: Error
Event Source: VolSnap
Event Category: None
Event ID: 25
Date: 4/7/2011
Time: 1:55:22 AM
User: N/A
Computer: CORP-AVAMAR1
Description:
The shadow copies of volume C: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.
=================================
Event Type: Warning
Event Source: VolSnap
Event Category: None
Event ID: 24
Date: 4/13/2011
Time: 4:05:24 PM
User: N/A
Computer: CORP-AVAMAR1
Description:
There was insufficient disk space on volume C: to grow the shadow copy storage for shadow copies of C:. As a result of this failure all shadow copies of volume C: are at risk of being deleted.
Affected Environments
All supported Avamar Windows file system plug-in versions up to, and including, v5.0.106-28 are affected.
Impact
Files, folders, and/or volumes on the Windows client's file system might not be backed up due to this issue and there might not be errors reported for files, folders, and/or volumes that are not backed up.
Cause
The Avamar backup software invokes VSS to create a snapshot ("shadow copy") of the data on each NTFS volume being backed up. The Avamar client software will then back up the files and folders on each snapshot. If VSS encounters an issue on a volume, then the files and folders on the snapshot of the volume will no longer be available to be backed up. If the Avamar client software had not yet started to process a folder when the snapshot disappears, then the folder might fail to be backed up without an error message ("exception") noting that the folder was not backed up. If, while backing up one volume, VSS encounters an issue on another volume, then the Avamar client software will not back up any files or folders on the affected volume because the snapshot of that volume disappears, and no error message is generated to note that the volume did not get backed up.
NOTE: If VSS fails at the beginning of the backup, then no snapshot is created, and the Avamar client software will attempt to back up the files/folders on each volume. Any files that are "locked" by another process will not be backed up, and the Avamar software will report an error for each file that could not be backed up.
Resolution
1. Upgrade to Windows file system client plug-in version 5.0.106-28 and then apply Hotfix 26904.
Or
2. Upgrade to Windows file system client plug-in version 6.0.100-592 or later.
These upgraded versions will provide improved visibility to the files, folders, and/or volumes that are not backed up when the snapshot disappears.
ETAs are Knowledgebase solutions that address:
*
Critical problems that cannot be prevented or controlled through proactive tools and processes.
* Product defect that might cause unexpected behavior or any kind of data loss.
Use the information in this EMC Advisory to avoid any situation that might arise from the problems described in the Knowledgebase solution. Knowledgebase solutions are updated as new information becomes available until a permanent solution exists. For questions regarding this advisory, contact EMC CSS Remote at .
Back<http://solutions.emc.com/emcsolutionview.asp?id=esg122338 >
EMC Solutions
EMC Solutions
Solution ID:
esg122338<http://solutions.
Product(s):
Avamar Client for Windows
Date Created:
06/14/2011
Category(ies):
Bug or Defect
Date Modified:
06/21/2011
Status:
Approved
Use Count:
0
Related Bugs:
26904
Subject:
ETA esg122338: Avamar Client for Windows: During Windows NTFS backups, the Avamar client software might fail to back up files, folders, and/or volumes and not report the exceptions
Solution:
EMC Technical Advisory
ETA esg122338: Avamar Client for Windows: During Windows NTFS backups, the Avamar client software might fail to back up files, folders, and/or volumes and not report the exceptions
Symptoms
If the Microsoft Volume Shadow Copy Service (VSS) fails during an NTFS backups of Windows clients running Windows 2003 SP1 or more recent Windows versions, then the Avamar Windows file system client software might fail to backup files, folders, and/or volumes without reporting errors for all the files, folders, and/or volumes that did not get backed up.
In some cases the backup might report a "completed" status, which means that no errors were reported during the backup, but might fail to back up an entire volume.
In other cases, the backup might report a "completed with exceptions" status, but entire folders might not be backed up, and not all the relevant exceptions are reported. As a result, the size of the folders that were not backed up is reported in the restore window to be 0 bytes.
In these cases, the Windows system "Event Viewer" will log one or more of the following VSS related errors or warnings during the backup (using volume C: as an example):
==============================
Event Type: Error
Event Source: VolSnap
Event Category: None
Event ID: 35
Date: 4/11/2011
Time: 1:00:21 AM
User: N/A
Computer: CORP-AVAMAR1
Description:
The shadow copies of volume C: were aborted because the shadow copy storage failed to grow.
==============================
Event Type: Error
Event Source: VolSnap
Event Category: None
Event ID: 13
Date: 4/11/2011
Time: 12:59:44 AM
User: N/A
Computer: CORP-AVAMAR1
Description:
The shadow copy of volume C: could not grow its shadow copy storage on volume F:.
==============================
Event Type: Error
Event Source: VolSnap
Event Category: None
Event ID: 25
Date: 4/7/2011
Time: 1:55:22 AM
User: N/A
Computer: CORP-AVAMAR1
Description:
The shadow copies of volume C: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.
==============================
Event Type: Warning
Event Source: VolSnap
Event Category: None
Event ID: 24
Date: 4/13/2011
Time: 4:05:24 PM
User: N/A
Computer: CORP-AVAMAR1
Description:
There was insufficient disk space on volume C: to grow the shadow copy storage for shadow copies of C:. As a result of this failure all shadow copies of volume C: are at risk of being deleted.
Affected Environments
All supported Avamar Windows file system plug-in versions up to, and including, v5.0.106-28 are affected.
Impact
Files, folders, and/or volumes on the Windows client's file system might not be backed up due to this issue and there might not be errors reported for files, folders, and/or volumes that are not backed up.
Cause
The Avamar backup software invokes VSS to create a snapshot ("shadow copy") of the data on each NTFS volume being backed up. The Avamar client software will then back up the files and folders on each snapshot. If VSS encounters an issue on a volume, then the files and folders on the snapshot of the volume will no longer be available to be backed up. If the Avamar client software had not yet started to process a folder when the snapshot disappears, then the folder might fail to be backed up without an error message ("exception") noting that the folder was not backed up. If, while backing up one volume, VSS encounters an issue on another volume, then the Avamar client software will not back up any files or folders on the affected volume because the snapshot of that volume disappears, and no error message is generated to note that the volume did not get backed up.
NOTE: If VSS fails at the beginning of the backup, then no snapshot is created, and the Avamar client software will attempt to back up the files/folders on each volume. Any files that are "locked" by another process will not be backed up, and the Avamar software will report an error for each file that could not be backed up.
Resolution
1. Upgrade to Windows file system client plug-in version 5.0.106-28 and then apply Hotfix 26904.
Or
2. Upgrade to Windows file system client plug-in version 6.0.100-592 or later.
These upgraded versions will provide improved visibility to the files, folders, and/or volumes that are not backed up when the snapshot disappears.
ETAs are Knowledgebase solutions that address:
*
Critical problems that cannot be prevented or controlled through proactive tools and processes.
* Product defect that might cause unexpected behavior or any kind of data loss.
Use the information in this EMC Advisory to avoid any situation that might arise from the problems described in the Knowledgebase solution. Knowledgebase solutions are updated as new information becomes available until a permanent solution exists. For questions regarding this advisory, contact EMC CSS Remote at .
Back<http://solutions.emc.com/
Avamar deduplication.
Introduced at our client location since 2009. and its one of the best dedup and efficient backups for structured and remote backups.
Monday, May 31, 2010
Avamar is the best deduplication in the current backup platforms
Every backup is the incremental, but every restore is full restore.
Data deduplication significantly reduces backup time by only storing unique daily changes, while always maintaining daily full backups for immediate single-step restore.
Subscribe to:
Posts (Atom)