9 Replies Latest reply: Nov 24, 2010 11:11 AM by MichaelRansom RSS

New to Avamar and many questions.

fl

Hello all,

 

We just had an Avamar 5 grid installed last week and this is my first exposure to Avamar but not the backup world.  Less than 3 days into Avamar and we are getting the following errors or messages and we are not sure how to go about them as the docs we have are for agent installations and nothing about error messages or the likes.

 

Error message 1:

2010-06-26 03:00:06 avtar Info <6070>: Microsoft VSS is not available on this system; checking for OTM to freeze volumes.
2010-06-26 03:00:06 avtar Info <6077>: Freeze volumes attempting failover...
2010-06-26 03:00:07 avtar Error <5325>: No Open File Agent installed.  Some files may not be backed up.

2010-06-26 03:01:03 avtar Error <5139>: File access error "C:\Program Files\Common Files\Symantec Shared\SPBBC\LOGS\BBConfig.log" (code 32: The process cannot access the file because it is being used by another process).
2010-06-26 03:01:03 avtar Error <5139>: File access error "C:\Program Files\Common Files\Symantec Shared\SPBBC\LOGS\BBDebug.log" (code 32: The process cannot access the file because it is being used by another process).
2010-06-26 03:01:03 avtar Error <5139>: File access error "C:\Program Files\Common Files\Symantec Shared\SPBBC\LOGS\BBDetect.log" (code 32: The process cannot access the file because it is being used by another process).
2010-06-26 03:01:03 avtar Error <5139>: File access error "C:\Program Files\Common Files\Symantec Shared\SPBBC\LOGS\BBNotify.log" (code 32: The process cannot access the file because it is being used by another process).
.

.

.
I'm only getting on Windows 2000 servers so I am assuming it's because Windows 2000 does not have VSS like 2003 and 2008 so do I just ignore the error or is there a way to resolve it?

 

Error message 2:

2010-06-28 04:04:50 avsql Error <6452>: SQL command "declare @dbname as nvarchar(8); set @dbname=N'eshadata'; backup log @dbname to virtual_device='SQL-Server1_ESHA_eshadata_CSULB-OAT_SQL_Schedule-CSULB-OAT_SQL-1277719200177#8-3006-SQL'" failed with the following messages
2010-06-28 04:04:50 avsql Error <0000>: [Microsoft][ODBC SQL Server Driver][SQL Server]The statement BACKUP LOG is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.
2010-06-28 04:04:50 avsql Error <0000>: [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally.
2010-06-28 04:05:00 avsql Error <6478>: VDS::Getconfig failed with 'The api was waiting and the timeout interval had elapsed'
2010-06-28 04:05:00 avsql Error <6479>: Timed out. Was Microsoft SQLServer running?
2010-06-28 04:05:00 avsql Info <6802>: SQLDMO connect version Microsoft SQL Server  2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.2 (Build 3790: Service Pack 2)
.

I am not a SQL DBA nor the SQL admin but I do know that the SQLserver is up and running.  I am getting these error messages also on ALL of our servers with SQL server installed on it.  Again is there a solution to this or am I doing something wrong as all I did was just use the default installations and added the SQL plug-in to the dataset selection.

 

Error message 3:

2010-06-28 03:58:54 avtar Info <5069>: - Writing cache file C:\Program Files\avs\var\f_cache.dat
2010-06-28 03:58:55 avtar Info <5546>: - Cache update complete C:\Program Files\avs\var\f_cache.dat (22.0MB of 255MB max)
2010-06-28 04:00:06 avtar Info <5100>: Status 2010-06-28 04:00:06, 42,119 files, 4,781 folders, 10.20 GB (90 files, 10.80 MB, 0.10% new) 56MB 20% CPU  C:\Windows\System32\wbem\Logs\FrameWork.log
2010-06-28 04:15:06 avtar Info <5100>: Status 2010-06-28 04:15:06, 59,695 files, 5,302 folders, 11.45 GB (93 files, 13.43 MB, 0.11% new) 73MB 22% CPU  C:\Windows\winsxs\ManifestCache\6.0.6002.18005_001c11ba_blobs.bin
2010-06-28 04:30:06 avtar Info <5100>: Status 2010-06-28 04:30:06, 69,544 files, 10,433 folders, 15.55 GB (93 files, 13.43 MB, 0.08% new) 75MB 14% CPU  C:\Windows\winsxs\ManifestCache\6.0.6002.18005_001c11ba_blobs.bin
2010-06-28 04:45:06 avtar Info <5100>: Status 2010-06-28 04:45:06, 78,900 files, 14,066 folders, 18.10 GB (93 files, 13.43 MB, 0.07% new) 73MB 12% CPU  C:\Windows\winsxs\ManifestCache\6.0.6002.18005_001c11ba_blobs.bin
2010-06-28 05:00:06 avtar Info <5100>: Status 2010-06-28 05:00:06, 93,738 files, 15,091 folders, 20.10 GB (93 files, 13.43 MB, 0.07% new) 73MB 18% CPU  C:\Windows\winsxs\ManifestCache\6.0.6002.18005_001c11ba_blobs.bin
2010-06-28 05:15:05 avtar Info <5100>: Status 2010-06-28 05:15:05, 113,077 files, 16,720 folders, 26.20 GB (93 files, 13.43 MB, 0.05% new) 73MB 21% CPU  C:\Windows\winsxs\ManifestCache\6.0.6002.18005_001c11ba_blobs.bin
2010-06-28 05:30:06 avtar Info <5100>: Status 2010-06-28 05:30:06, 141,951 files, 16,780 folders, 27.32 GB (93 files, 13.43 MB, 0.05% new) 73MB 35% CPU  C:\Windows\winsxs\ManifestCache\6.0.6002.18005_001c11ba_blobs.bin
2010-06-28 05:45:05 avtar Info <5100>: Status 2010-06-28 05:45:05, 168,882 files, 18,069 folders, 37.25 GB (93 files, 13.43 MB, 0.04% new) 73MB 30% CPU  C:\Windows\winsxs\ManifestCache\6.0.6002.18005_001c11ba_blobs.bin
2010-06-28 06:00:01 avtar Info <8708>: Cancelled - exiting...
2010-06-28 06:00:02 avtar Info <7163>: Backup CANCELLED, wrapping-up session with Server
.

This is not so an error but more that the system takes more time than the backup window available but it shouldn't because this server is pretty static and after the first complete backup all the rest should be fairly quick but it's not and the new bytes for the server as indicated by Avamar is <0.05% but yet it seems to take more that 5 hours and total data size of the server is 72GB, first backup took 18 hours.

 

 

On to another question I can't seem to figure out is how do I specify an exclusion ONLY for one client that uses the same group, dataset, schedule, retention policies that all the other Windows servers uses?  I've tried clicking on the override dataset checkbox for the client but that only lets me choose another defined dataset and the exclusion fields are greyed out.  Do I have to create a whole new dataset just for that one client because of the exclusion I want to implement on it?

 

One other thing our NDMP filer backups seems to take a very very very long time.  The NDMP accelerator is located at the same location as the Avamar grid but the SAN/NAS filers are located at a remote location connected via a VPN tunnel but I don't know the speed of the tunnel but was told it's a T1 connection.

 

Thanks in advance.

  • 1. Re: New to Avamar and many questions.
    alias23122

    I can answer a few questions:

     

     

     

    1)       “No Open File Agent installed.  Some files may not be backed up.” You need the Windows 2000 OTM agent installed to backup open files.  If you don’t have it, then you will have to ask EMC support to provide it for you. 

     

    2)      “The statement BACKUP LOG is not allowed while the recovery model is SIMPLE” Look at the following link  http://social.msdn.microsoft.com/forums/en-US/sqldisasterrecovery/thread/0494d213-e1f1-451e-9d46-25f0ff51d40f

     

    3)      Error message #3:  If Avamar is going through those files even after the first full backup, then those files are changing.  I think you can exclude those files from the backup since they are not required for a restore.  http://blogs.msdn.com/b/jonwis/archive/2009/01/13/what-s-winsxs-manifestcache-lt-something-gt-blobs-bin.aspx

     

    4)      To exclude files on one client you have to do exactly what you said.  You have to create another dataset and override the dataset that is being applied via the policy.

     

    5)      I don’t know the answer to the NDMP question.

  • 2. Re: New to Avamar and many questions.
    fl

    Thanks for the reply and suggestion as I been able to fix most of the problems with the exception of my NDMP issue which our VAR whom install and setup Avamar is working on it.

     

    On one of my 2000 server client I am getting "avtar Error <5328>: Open File Agent timeout: Waited 300 seconds for system to stabilize for 4 seconds.  Some files may not be backed up." and it's only on this one system.  Now 300 seconds (5 minutes) is a long time and I'm 99% sure there is nothing going on with this server at 3:15am when it's schedule to run.  Should I adjust the freezewait time or the freezetimeout time or is there somewhere else I need to look for problems?

  • 3. Re: New to Avamar and many questions.
    David Wilches Becerra

    Some times I have changed the parameters: "to stabilize for 4 seconds"  and config as 3 or sometines 2, but as I read is not the best practices. But if someone can explain us, in detail what exactly means this parametrs, it will be helpfully.

  • 4. Re: New to Avamar and many questions.
    fl

    David,

    I had seen the "to stablize for" parameter but like you said there isn't much info on this parameter nor most of the parameters in Avamar.  I changed the parameter to 3 seconds and that seems to fix the issue.  Thanks.

  • 5. Re: New to Avamar and many questions.
    OKlier

    For your Windows 2000 server you may need to use the older agent. I got this from the:

     

    EMC® AVAMAR®
    FOR WINDOWS SERVERS
    5.0

     

    USER GUIDE
    P/N 300-010-672
    REV A02

     

    NOTE: The Avamar 5.0 Windows Client does not support
    backup and recovery of Windows 2000. For Windows 2000,
    use the Avamar 4.1 Windows Client.

     

    Hope this helps!

  • 6. Re: New to Avamar and many questions.
    fl

    Oklier,

    I am already using the older 4.1 agent. This agent works fine for my other Windows 2000 servers but it's just this one it seems to have problems with.  I'm not going to worry about it as it's slated to be decommission in a few months away.

  • 7. Re: New to Avamar and many questions.
    Tim.A

    One other thing our NDMP filer backups seems to take a very very very long time.  The NDMP accelerator is located at the same location as the Avamar grid but the SAN/NAS filers are located at a remote location connected via a VPN tunnel but I don't know the speed of the tunnel but was told it's a T1 connection.

     

     

    Ok the way this works is an NDMP dump full bandwidth to the accelerator the Accelerator does the dedup then sends the data back to the grid.

    so the solution is to move the NDMP accelerator closer to the NAS layer 2 network.

    I would think even if you do that recovery over a T1 would not meet most SLA requirements.

     

    The better solution is to have a grid in each location, with the Accelerator on the same layer 2 switch and replicate deduped copies of the NAS volumes offsite.

  • 8. Re: New to Avamar and many questions.
    fl

    Tim,

     

    Our original plan was to have 2 grids, 1 local and 1 remote where we would replicate to but due to budget cuts we could only get 1 grid but to meet the offsite requirement it was decided to put the grid remote and both our VAR and EMC Avamar engineer confirmed that it would not be an issue. We did also move the NDMP accelerator to the local site where the filers are thinking that was the problem but that wasn't in this case as it turned out we were given incorrect info on the way NDMP datasets are suppose to be setup in where only one filesystem to one dataset, this in it self creates another management headache when you have hundreds of filesystems.  I talked to EMC engineers and it has something to do with the way their NDMP engine handles level 1 dumps, I just hope they can rework their engine to allow multiple filesystems in one dataset in future releases.

  • 9. Re: New to Avamar and many questions.
    MichaelRansom

    In regards to the question  about specific excludes for a client you actually have two options.

     

    1) You can set up a specific Data set for the client, possibly the easiest way to deal with it.

     

    However,

     

    2) you can create an avtar.cmd file on the server in question.  There are flags that you can include in this file to exclude ceratin files or directories, the backup will utilize the dataset and then apply the avtar.cmd file flags along with it.

     

    This file needs to be placed in \<install location>\var

     

    Typically C:\Program Files\avs\var  in Windows, or \opt\AVMRclnt\var on Solaris clients.