When backing up SQL databases using the incremental option the backup job fails with “The statement BACKUP LOG is not allowed while the recovery model is SIMPLE” This is because the recovery model of the database being backed up is currently set to “Simple”. To resolve this error you must either change the database backup type to full, or change the database recovery model in SQL to either “BulkLogged or Full”.
The new EMC Avamar 6.1 Microsoft SQL plugin feature actually detects the recovery model of the database and skips the incremental backup, places a message in the log and automatically promotes the backup from an incremental to a full backup. So you can also upgrade Avamar to version 6.1 to resolve this error as well.
Tag: emc avamar
I’m going back over some of the new differences in Avamar 6.1 and am very impressed with the enhancements that Avamar now has with VMware image based backups. Before version 6.1 you needed a seperate image proxy for Linux and a seperate proxy for Windows, now with the new proxy design both Operating Systems have been integrated into one proxy. Not only does the proxy support both OS’s but now it also supports File Level Recovery to both OS’s where as Windows was only supported previously. To be more specific; the Unified Proxy now supports Windows NTFS, and Linux ext2, ext3, and LVM. The proxy does NOT support the following: Windows GPT Partitions, Windows Dynamic disks, Extended Partitions, Encypted Partitions, Compressed Partitions, or XFS.
Very Cool integration:
I noticed a recent NDMP backup failed with error code 10007, here is the job log information:
2010-12-01 08:00:45 avndmp Error : Snapup of “ndmp-volume-name” aborted due to ‘Error during NDMP session’.
2010-12-01 08:00:45 avndmp Info : NDMP session result: avtar returned:176 ‘Fatal signal’ ndmp returned:157 ‘Miscellaneous error’
2010-12-01 08:00:45 avndmp Info : Final summary generated subwork 1, cancelled/aborted 1, snapview 0, exitcode 157
2010-12-01 08:00:45 avndmp FATAL : Fatal signal 11 in pid 21946
2010/12/01-08:00:45.23164 [avndmp_ctl_sup] FATAL ERROR: Fatal signal 11
[sociallocker id=”759″]I’m still investigating and will update the post when i find out the root cause. [/sociallocker]
Below are the minimum required vCenter User Account Permissions for an Avamar account in order to setup image level backups. EMC recommends as a best practice to setup a separate account for Avamar to use during the image-level backups. This is to assist with troubleshooting any problems with backups and to also help maintain a secure vCenter environment. In high-security environments, you can restrict the vCenter user account permissions required to configure and administer the Avamar VMware image backup and restore feature to all of the following: