Jump to content

A+ Computers

Members
  • Content Count

    1,583
  • Joined

  • Last visited

  • Days Won

    205

Posts posted by A+ Computers


  1. glad you already found that information. 

     

    For the record, a restart of my affected server did not solve the issue. As it is backing up properly for the time being, I'm holding off contacting support until I have time to actually deal with this.

    If you get it working though, I'd be interested to know what steps you took.


  2. You should also check the OLB dashboard -> reporting to see if it is actually backing up, but just not generating an alert to say if it completed or not.

    You can view this dashboard by opening the device in the portal and hitting the "View files & folders" link for it. 

    As it turns out, I too have a server that is not reporting that it backing up each night, yet the report from the olb page shows it is running the backup and does show files being added.


  3. I have a customer that I need to reduce the # of assigned backup blocks from 5 to 4. When I go to the account services page, it takes forever for the page to say that it's saved my changes after reducing the block count by one. However, once I go back to the client dashboard, it still shows the assigned blocks as being 5. When I re-visit the services page, it once again shows the assigned blocks as being 5. 

    What gives?


  4. Hi Liz, 

    That is not the issue. The issue is after the backup has run, the TOTAL backup size for the device is showing at 1.4GB in several places. The total files backed up for the device was 26,357 on Oct 17th in the reports. After the next backup, on Oct 21st, the total files shows as 1963 in the reports. This is not the number of files backed up at that time, this is the total number of files stored online through OLB. 

    Again, this was confirmed by doing a restore to a test VM last night. After the restore, there were 26,357 files in the restore folder.

    After posting this thread, at 9:59AM CST, I received an alert for this client account telling me it was once again over 90% of its storage limit, and the display in the portal was once again showing as 98% usage. No other backups had been run, this was just the portal finally figuring things out and sending an alert.


  5. I've run into a strange one, so heads up to anyone else who might notice this.

    I've got a customer with a 75 GB backup pool. They are consistently at 98% usage across 2 devices. One of the devices has about 20GB of data backed up. 

    If I manually kick off a backup for the device with 20GB from the portal, as soon as the backup completes it shows the overall usage as 73% and that particular device only accounting for 1.4GB of space.

    I know this is a display issue as I ran a full restore for that device on a testing VM overnight and it restored 20GB of data. The issue shows up on the reseller level dashboard, the client level dashboard and even the OLB  dashboard for that device. It also shows the incorrect amount of files and total backup size in all related reports. The issue seems to correct itself as far as the dashboard views are concerned, after about 30 minutes. The reports however still show the incorrect sizes.

    This only began happening after Oct 17th.


  6. Something must be up. I'm seeing two customers in my portal that exceeded their backup limit last night, but no emails warning that they are over the limit. 

    one has been near the limit for a while and the other is a newish client showing an unusually large backup last night. I can't say that either is surprising, but the fact that I did not get a notification for either customer account is.


  7. No. As I said previously, we've given up on this issue being resolved and implemented another backup solution when Exchange data is present. The case  a year old with no working resolution and AVG stopped communicating with me shortly after the initial support incident.

    I suggest AVG setup a LAB on their own to test and resolve this issue.


  8. Unfortunately this did not solve the issue for me on the server I tested it with. I still get the same errors as before

     

    2016-06-22 21:51:56,939 [41] WARN    SysLog          - Cannot set application shortcut because file [C:\Users\Public\Desktop\AVG Online Backup.lnk] not found.
    2016-06-22 21:51:56,939 [41] DEBUG   WebBinding      - Init 'IClientMessagingService' channel
    2016-06-22 21:51:56,997 [41] INFO    Agent           - Authentication is successful.
    2016-06-22 21:51:56,999 [41] INFO    Agent           - Running Microsoft Exchange 2010 backup for AVG13905
    2016-06-22 21:51:57,013 [41] INFO    ExternalLibraryManager - BackupSessionBegin action is being performed
    2016-06-22 21:51:57,013 [41] DEBUG   AVGLibraryCommunicator - BackupSessionBegin: Exchange
    2016-06-22 21:51:57,024 [41] DEBUG   WebBinding      - Init 'ICentralManagementService' channel
    2016-06-22 21:51:57,169 [41] INFO    CM              - DoSendEvents=[True], PingInterval=[600sec]
    2016-06-22 21:51:57,169 [39] DEBUG   CM              - Send event to CM:
    AccountName...............[AVG13905];
    AccountType...............[BackupAccount];
    SystemName................[OAWSRV];
    SystemId..................[];
    EventType.................[BackupStarted];
    EventBackupType...........[Exchange];
    ClientDate................[6/22/2016 4:51:57 PM];
    IsScheduled...............[False];
    TotalFilesCount...........[0];
    TotalFilesSize............[0];
    ErrorFilesCount...........[0];
    ErrorFilesSize............[0];
    UploadedFilesCount........[0];
    UploadedFilesSize.........[0];
    UnchangedFilesCount.......[0];
    UnchangedFilesSize........[0];
    BackupId..................[4f69b16c-811a-496a-9f71-92edf0898b3c];
    BackupDuration............[0];
    ClientVersion.............[6.2.3.27];
    JobName...................[];
    BackupSummary.............[];
    Progress..................[0];
    FileLevelErrorsDetails....[];

    2016-06-22 21:51:57,169 [39] DEBUG   WebBinding      - Init 'ICentralManagementService' channel
    2016-06-22 21:51:57,175 [41] INFO    VssBackup       - Initializing for backup...
    2016-06-22 21:51:57,183 [41] INFO    VssBackup       - Gathering writer metadata...
    2016-06-22 21:51:58,393 [41] INFO    VssBackup       - Found VSS Writer=[Microsoft Exchange Writer], id=[76fe1ac4-15f7-4bcd-987e-8e1acb462fb7]
    2016-06-22 21:51:58,424 [41] INFO    VssBackup       - Disabling other [23] writers...
    2016-06-22 21:51:58,424 [41] INFO    VssBackup       - Ok
    2016-06-22 21:51:58,921 [41] INFO    VssBackup       - Getting Data for the Writer Microsoft Exchange Writer=[76fe1ac4-15f7-4bcd-987e-8e1acb462fb7]
    2016-06-22 21:51:58,922 [41] INFO    ServerManager   - Server name: [OAWSRV], Is Named: [True]
    2016-06-22 21:51:58,924 [41] DEBUG   ExchangeDatabaseHelper - PS disposed
    2016-06-22 21:51:58,926 [41] DEBUG   ExchangeDatabaseHelper - ConnectionUri........................[http://oawsrv.oawnet.local/powershell?serializationLevel=Full];
    ComputerName.........................[oawsrv.oawnet.local];
    Scheme...............................[http];
    Port.................................[80];
    AppName..............................[/powershell];
    Credential...........................[System.Management.Automation.PSCredential];
    ShellUri.............................[http://schemas.microsoft.com/powershell/Microsoft.Exchange];
    AuthenticationMechanism..............[Default];
    CertificateThumbprint................[];
    MaximumConnectionRedirectionCount....[0];
    MaximumReceivedDataSizePerCommand....[];
    MaximumReceivedObjectSize............[];
    UseCompression.......................[True];
    NoMachineProfile.....................[False];
    ProxyAccessType......................[None];
    ProxyAuthentication..................[Default];
    ProxyCredential......................[];
    SkipCACheck..........................[False];
    SkipCNCheck..........................[False];
    SkipRevocationCheck..................[False];
    NoEncryption.........................[False];
    UseUTF16.............................[False];
    Culture..............................[en-US];
    UICulture............................[en-US];
    OpenTimeout..........................[180000];
    CancelTimeout........................[60000];
    OperationTimeout.....................[180000];
    IdleTimeout..........................[240000];

    2016-06-22 21:51:58,952 [41] ERROR   ExchangeDatabaseHelper - Remote connection to exchange powershell failed
    System.Management.Automation.Remoting.PSRemotingTransportException: Connecting to remote server failed with the following error message : The WinRM client cannot process the request. The WinRM client tried to use Negotiate authentication mechanism, but the destination computer (OAWSRV.oawnet.local:80) returned an 'access denied' error. Change the configuration to allow Negotiate authentication mechanism to be used or specify one of the authentication mechanisms supported by the server. To use Kerberos, specify the local computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain. To use Basic, specify the local computer name as the remote destination, specify Basic authentication and provide user name and password. Possible authentication mechanisms reported by server: For more information, see the about_Remote_Troubleshooting Help topic.
       at System.Management.Automation.Runspaces.Internal.RunspacePoolInternal.EndOpen(IAsyncResult asyncResult)
       at System.Management.Automation.Runspaces.RunspacePool.Open()
       at System.Management.Automation.RemoteRunspace.Open()
       at SOSOnlineBackup.Client.Library.Core.ServerBackup.Exchange.ExchangeDatabaseHelper.#=qDcaueFPapR67fhnwc9MIrHmbYsusBUTfDXJU19e9bGo=(String #=qz0h0bKTTRPfIoMWGIl6YIA==, String #=q6bQBr_aChR6GxDX2YBEoLA==)
       at SOSOnlineBackup.Client.Library.Core.ServerBackup.Exchange.ExchangeDatabaseHelper.GetDatabaseStatus(String dbname, Nullable`1& mounted, Nullable`1& recovery)
    2016-06-22 21:51:58,953 [41] INFO    ServerManager   - Database name: [Mailbox Database], Database id: [d4487490-a982-43fb-b7f9-b5b7b4b4dd70]
    2016-06-22 21:51:58,953 [41] INFO    ServerManager   - Server name: [OAWSRV], Is Named: [True]
    2016-06-22 21:51:58,954 [41] DEBUG   ExchangeDatabaseHelper - PS disposed
    2016-06-22 21:51:58,956 [41] DEBUG   ExchangeDatabaseHelper - ConnectionUri........................[http://oawsrv.oawnet.local/powershell?serializationLevel=Full];
    ShellUri.............................[http://schemas.microsoft.com/powershell/Microsoft.Exchange];
    ComputerName.........................[oawsrv.oawnet.local];
    Scheme...............................[http];
    Port.................................[80];
    AppName..............................[/powershell];
    Credential...........................[System.Management.Automation.PSCredential];
    AuthenticationMechanism..............[Default];
    CertificateThumbprint................[];
    MaximumConnectionRedirectionCount....[0];
    MaximumReceivedDataSizePerCommand....[];
    MaximumReceivedObjectSize............[];
    UseCompression.......................[True];
    NoMachineProfile.....................[False];
    ProxyAccessType......................[None];
    ProxyAuthentication..................[Default];
    ProxyCredential......................[];
    SkipCACheck..........................[False];
    SkipCNCheck..........................[False];
    SkipRevocationCheck..................[False];
    NoEncryption.........................[False];
    UseUTF16.............................[False];
    Culture..............................[en-US];
    UICulture............................[en-US];
    OpenTimeout..........................[180000];
    CancelTimeout........................[60000];
    OperationTimeout.....................[180000];
    IdleTimeout..........................[240000];

    2016-06-22 21:51:58,982 [41] ERROR   ExchangeDatabaseHelper - Remote connection to exchange powershell failed
    System.Management.Automation.Remoting.PSRemotingTransportException: Connecting to remote server failed with the following error message : The WinRM client cannot process the request. The WinRM client tried to use Negotiate authentication mechanism, but the destination computer (OAWSRV.oawnet.local:80) returned an 'access denied' error. Change the configuration to allow Negotiate authentication mechanism to be used or specify one of the authentication mechanisms supported by the server. To use Kerberos, specify the local computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain. To use Basic, specify the local computer name as the remote destination, specify Basic authentication and provide user name and password. Possible authentication mechanisms reported by server: For more information, see the about_Remote_Troubleshooting Help topic.
       at System.Management.Automation.Runspaces.Internal.RunspacePoolInternal.EndOpen(IAsyncResult asyncResult)
       at System.Management.Automation.Runspaces.RunspacePool.Open()
       at System.Management.Automation.RemoteRunspace.Open()
       at SOSOnlineBackup.Client.Library.Core.ServerBackup.Exchange.ExchangeDatabaseHelper.#=qDcaueFPapR67fhnwc9MIrHmbYsusBUTfDXJU19e9bGo=(String #=qz0h0bKTTRPfIoMWGIl6YIA==, String #=q6bQBr_aChR6GxDX2YBEoLA==)
       at SOSOnlineBackup.Client.Library.Core.ServerBackup.Exchange.ExchangeDatabaseHelper.GetDatabaseStatus(String dbname, Nullable`1& mounted, Nullable`1& recovery)
    2016-06-22 21:51:58,983 [41] INFO    ServerManager   - Database name: [Public Folder Database 1391712490], Database id: [db5c4340-dce6-46f8-b990-34e88446d7a5]
    2016-06-22 21:51:58,983 [41] INFO    ServerManager   - Calculating size for: [Public Folder Database 1391712490], total calculated: [142671872]
    2016-06-22 21:51:58,983 [41] INFO    ServerManager   - Calculating size for: [Mailbox Database], total calculated: [5108727808]
    2016-06-22 21:51:58,984 [41] INFO    ServerManager   - Calculating size for: [Public Folder Database 1391712490], total calculated: [146874368]
    2016-06-22 21:51:58,985 [41] INFO    ServerManager   - Calculating size for: [Mailbox Database], total calculated: [5113323520]
    2016-06-22 21:51:58,987 [41] DEBUG   ExchangeDatabaseHelper - PS disposed
    2016-06-22 21:51:58,990 [41] DEBUG   ExchangeDatabaseHelper - ConnectionUri........................[http://oawsrv.oawnet.local/powershell?serializationLevel=Full];
    ComputerName.........................[oawsrv.oawnet.local];
    Scheme...............................[http];
    Port.................................[80];
    AppName..............................[/powershell];
    Credential...........................[System.Management.Automation.PSCredential];
    ShellUri.............................[http://schemas.microsoft.com/powershell/Microsoft.Exchange];
    AuthenticationMechanism..............[Default];
    CertificateThumbprint................[];
    MaximumConnectionRedirectionCount....[0];
    MaximumReceivedDataSizePerCommand....[];
    MaximumReceivedObjectSize............[];
    UseCompression.......................[True];
    NoMachineProfile.....................[False];
    ProxyAccessType......................[None];
    ProxyAuthentication..................[Default];
    ProxyCredential......................[];
    SkipCACheck..........................[False];
    SkipCNCheck..........................[False];
    SkipRevocationCheck..................[False];
    NoEncryption.........................[False];
    UseUTF16.............................[False];
    Culture..............................[en-US];
    UICulture............................[en-US];
    OpenTimeout..........................[180000];
    CancelTimeout........................[60000];
    OperationTimeout.....................[180000];
    IdleTimeout..........................[240000];

    2016-06-22 21:51:59,016 [41] ERROR   ExchangeDatabaseHelper - Remote connection to exchange powershell failed
    System.Management.Automation.Remoting.PSRemotingTransportException: Connecting to remote server failed with the following error message : The WinRM client cannot process the request. The WinRM client tried to use Negotiate authentication mechanism, but the destination computer (OAWSRV.oawnet.local:80) returned an 'access denied' error. Change the configuration to allow Negotiate authentication mechanism to be used or specify one of the authentication mechanisms supported by the server. To use Kerberos, specify the local computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain. To use Basic, specify the local computer name as the remote destination, specify Basic authentication and provide user name and password. Possible authentication mechanisms reported by server: For more information, see the about_Remote_Troubleshooting Help topic.
       at System.Management.Automation.Runspaces.Internal.RunspacePoolInternal.EndOpen(IAsyncResult asyncResult)
       at System.Management.Automation.Runspaces.RunspacePool.Open()
       at System.Management.Automation.RemoteRunspace.Open()
       at SOSOnlineBackup.Client.Library.Core.ServerBackup.Exchange.ExchangeDatabaseHelper.#=qDcaueFPapR67fhnwc9MIrHmbYsusBUTfDXJU19e9bGo=(String #=qz0h0bKTTRPfIoMWGIl6YIA==, String #=q6bQBr_aChR6GxDX2YBEoLA==)
       at SOSOnlineBackup.Client.Library.Core.ServerBackup.Exchange.ExchangeDatabaseHelper.SetActualBackupDates(IEnumerable`1 exchangeDatabases)
    2016-06-22 21:51:59,024 [41] INFO    ExternalLibraryManager - BackupSessionEnd action is being performed
    2016-06-22 21:51:59,026 [41] DEBUG   AVGLibraryCommunicator - BackupSessionEnd parameters:
                    exitCode = -2146233088, backupType = Exchange, isScheduled = False, isCancelled = False, isPolicyApplied = False,
                    duration = 2, nextRunTime = 1-1-1 0:0:0 0, pcVersion = 6.2.3.27, uploadedCount = 0, 
                    uploadedSize = 0, errorCount = 0, errorSize = 0, unchangedCount = 0, 
                    unchangedSize = 0, totalCount = 0, totalSize = 0
    2016-06-22 21:51:59,471 [41] ERROR   Agent           - System.Exception: Remote connection to exchange powershell failed ---> System.Management.Automation.Remoting.PSRemotingTransportException: Connecting to remote server failed with the following error message : The WinRM client cannot process the request. The WinRM client tried to use Negotiate authentication mechanism, but the destination computer (OAWSRV.oawnet.local:80) returned an 'access denied' error. Change the configuration to allow Negotiate authentication mechanism to be used or specify one of the authentication mechanisms supported by the server. To use Kerberos, specify the local computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain. To use Basic, specify the local computer name as the remote destination, specify Basic authentication and provide user name and password. Possible authentication mechanisms reported by server: For more information, see the about_Remote_Troubleshooting Help topic.
       at System.Management.Automation.Runspaces.Internal.RunspacePoolInternal.EndOpen(IAsyncResult asyncResult)
       at System.Management.Automation.Runspaces.RunspacePool.Open()
       at System.Management.Automation.RemoteRunspace.Open()
       at SOSOnlineBackup.Client.Library.Core.ServerBackup.Exchange.ExchangeDatabaseHelper.#=qDcaueFPapR67fhnwc9MIrHmbYsusBUTfDXJU19e9bGo=(String #=qz0h0bKTTRPfIoMWGIl6YIA==, String #=q6bQBr_aChR6GxDX2YBEoLA==)
       at SOSOnlineBackup.Client.Library.Core.ServerBackup.Exchange.ExchangeDatabaseHelper.SetActualBackupDates(IEnumerable`1 exchangeDatabases)
       --- End of inner exception stack trace ---
       at SOSOnlineBackup.Client.Library.Core.ServerBackup.Exchange.ExchangeDatabaseHelper.SetActualBackupDates(IEnumerable`1 exchangeDatabases)
       at SOSOnlineBackup.Client.Library.Core.ServerBackup.Exchange.ExchangeManager.SetActualBackupDates(IEnumerable`1 servers)
       at SOSOnlineBackup.Client.Library.Core.ServerBackup.Core.ServerManager.GetServers()
       at SOSOnlineBackup.Client.Library.Core.ServerBackup.Core.ServerManager.LoadDatabasesForBackup()
       at SOSOnlineBackup.SAgent.MSExchange.MSExchangeBackupPerformer.RunBackup()
       at SOSOnlineBackup.SAgent.Agent.#=qxGElIgIFm_VdVkfoIj4OyA==(IBackupSession #=q6C44gObgohoq9tBTYfCjtA==)
       at Microsoft.Win32.TaskScheduler.V2Interop.ITaskFolder.GetTask(String Path)
       at Microsoft.Win32.TaskScheduler.TaskService.GetTask(ITaskService iSvc, String name)
    2016-06-22 21:51:59,473 [41] ERROR   Agent           - Remote connection to exchange powershell failed Details: Connecting to remote server failed with the following error message : The WinRM client cannot process the request. The WinRM client tried to use Negotiate authentication mechanism, but the destination computer (OAWSRV.oawnet.local:80) returned an 'access denied' error. Change the configuration to allow Negotiate authentication mechanism to be used or specify one of the authentication mechanisms supported by the server. To use Kerberos, specify the local computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain. To use Basic, specify the local computer name as the remote destination, specify Basic authentication and provide user name and password. Possible authentication mechanisms reported by server: For more information, see the about_Remote_Troubleshooting Help topic.
     


  9. So support emailed me anyway and directed me to this: 

    https://support.avg.com/SupportArticleView?l=en_US&urlName=Managed-Workplace-How-to-Enable-Disable-WSMan-Monitoring-Capabilities-in-Onsite-Manager&q=wsman

    basically it shows how to disable monitoring via WSman and go back to using dcom. Problem being, the reason monitoring was switched to wmi over dcom was that dcom caused memory leaks and performance issues. 

    I'll give it a go if I find the time later and let you know if it works.


  10. I stopped hearing from AVG on ticket # 00359216 on October 9th of last year. The last thing they had me try before cutting off communication on this issue was updating exchange to the latest service pack and ensuring all updates were installed. Doing that made no difference and I have been forced to rely on a different backup solution for exchange backups.

×
×
  • Create New...