The Avamar 7 VMware user guide is available on support.emc.com (login required).

It doesn't look like much has changed.  Here are the limitations:

The following limitations apply to file-level restore as described in “Restoring specific folders or files to the original virtual machine” on page 82 or “Restoring specific folders or files to a different virtual machine” on page 85: ◆ File-level restore requires that all proxies in the vCenter environment be version 6.1 or later. If any 6.1 or older proxies are detected in the vCenter environment, “Restoring specific folders or files to the original virtual machine” on page 82 will not be available. ◆ VMware Tools must be installed on the target virtual machine. For best results, ensure that all virtual machines are running the latest available version of VMware Tools. Older versions are known to cause failures when browsing during the file-level restore operation. ◆ The following virtual disk configurations are not supported: • Unformatted disks • Dynamic disks • GUID Partition Table (GPT) disks • Ext4 file systems • FAT16 file systems • FAT32 file systems • Extended partitions (Types: 05h, 0Fh, 85h, C5h, D5h) • Two or more virtual disks mapped to single partition • Encrypted partitions • Compressed partitions Note: In some cases (most notably extended partitions), it may be possible to restore the entire backup image to a temporary virtual machine as described in“Restoring the full image or selected drives to a different (existing) virtual machine” on page 79 or “Restoring the full image or selected drives to a new virtual machine” on page 81, then selectively copy the folders or files you need. ◆ ACLs are not restored. ◆ Symbolic links cannot be restored or browsed. ◆ You cannot restore more than 5,000 folders or files in the same file-level restore operation. ◆ You cannot browse more than 14,498 folders or files in the same file-level restore operation. ◆ The following limitations apply to logical volumes managed by Logical Volume Manager (LVM): • One physical volume (.vmdk) must be mapped to only one logical volume • Only ext2 and ext3 formatting is supported ◆ When partitions are created, the lower ordered indices must be filled first. That is, you cannot create a single partition and place it in the partition index 2, 3, or 4. That single partition must be at partition index 1. ◆ When performing file-level restores of Windows 8 and Windows Server 2012 virtual machines, the following file systems are not supported: • Deduplicated NTFS • Resilient File System (ReFS) • EFI bootloader ◆ When restoring files or folders to the original virtual machone (sic), only SCSI disks are supported; IDE disks are not supported. ◆ In vCenter 5.x, zero-byte files cannot be restored. Attempting to do so might cause the restore to fail. ◆ Encrypted folders or files cannot be restored. Attempting to do so might cause the restore to fail.

Unthrottled is the default network behavior so you shouldn't have to do anything to set unlimited bandwidth.

Unthrottled is the default network behavior so you shouldn't have to do anything to set unlimited bandwidth.

As fdxpilot said, unthrottled is the default. If you need to apply a throttle, you can configure this in the dataset. Please have a look at the following thread:

Re: Throttle Avamar Backups

The "plug-in" syntax is the one you have to use for VMware Image backups.

Unthrottled is the default network behaviour so you shouldn't have to do anything to set unlimited bandwidth.

I asked that because I've a WAN 100mb/s and restoring a full VM (400GB) the line consumption is about 20-25mb/s  and I want force it to 80/90 mb/s, but if it's not possible, it doesn't matters. I only asked.

By other hand, File Level Recovery limitations are not useful, now EXT4 file system are very extended in hundreds  systems and extended partitions and LVM as well. For me it's a big problem that these types of FS are not supported.

I was expecting this version to validate all little issues but I think I'm going to have to wait the following release ...  it's a pity.

Ivan.-

Hi All,

Can someone please send me the link for Avamar 7 user guide and also does avamar 7 supports Exchange 2013 and SQL 2012 AAG feature.

thanks

Here you are.

Avamar 7.0 AdminGuide

https://support.emc.com/docu48216_Avamar-7.0-Administration-Guide.pdf?language=en_US

Avamar 7.0 SQL UserGuide

https://support.emc.com/docu48236_Avamar-7.0-for-SQL-Server-User-Guide.pdf?language=en_US

Avamar 7.0 VSS Exchange

https://support.emc.com/docu48235_Avamar-7.0-for-Exchange-VSS-User-Guide.pdf?language=en_US

You must be registered to download documents.

Ivan.-

To igarcia's point, SQL 2012 AAG and Exchange 2013 will be supported by Avamar 7.

I asked that because I've a WAN 100mb/s and restoring a full VM (400GB) the line consumption is about 20-25mb/s  and I want force it to 80/90 mb/s, but if it's not possible, it doesn't matters. I only asked.

For restores, you may want to try setting the "allnodes" passthrough flag (i.e. [avtar]allnodes => true). This should be enough to allow avtar to fill the pipe if the bandwidth delay product divided by the number of nodes is less than than 60KB. If you do this, keep in mind that the allnodes flag consumes one GSAN connection per node instead of the usual one per backup. There is a limit of 40 GSAN connections per node in Avamar 6.1 so the flag should be used sparingly, otherwise you'll run out of connections and backups can fail.

By other hand, File Level Recovery limitations are not useful, now EXT4 file system are very extended in hundreds  systems and extended partitions and LVM as well. For me it's a big problem that these types of FS are not supported. I was expecting this version to validate all little issues but I think I'm going to have to wait the following release ...  it's a pity.

I just got some breaking news from PM -- assuming all goes according to plan, ext4 support and support for some LVM configurations will be available in the General Availability release of Avamar 7. That said, consider this the standard disclaimer that features and release dates are subject to change and there are never any guarantees until release day.