Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

My Information

  • Agent Count

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Simple, change the password on the firewall, don't give it to vendors.
  2. Kurt, I think this is a legacy monitor from the old B&R plugin. I think it used to update the dll's and the such so all the other monitors would work.
  3. @myohnk Sorry I dont log in often, but am usually in the slack. Those SQL files are generalized versions of what I built out. Not for direct importing unfortunately. You have to edit the SQL to update the %computerid% to be a known computerid.
  4. You could write a secondary script called from this script to close the ticket, just writing the ticketid to the scriptstate or a similar table, or using SQL to pull the appropriate ticketid. Interested in what you have so far.
  5. @tbasehore You could change the alert action to run script, then write a script that checks for the successful condition after an hour or two and if it exists closes the ticket.
  6. @Vitaliy S. you should join the slack!
  7. @Vitaliy S. We are currently evaluating both products.
  8. @Vitaliy S. Is there a guide for setting up the integration and the best practices for Veeam in Labtech? We are currently evaluating your products.
  9. I am also going to build out a list of services that I want to check so I can get the 'query-service' thing worked out for that.
  10. We are considering switching over to Veeam as I have only heard good things. However, in my trail period I am trying to sort through our best practice/process for using veeam. So how are you doing it? So far I like the monitors provided for B&R, in my testing. I basically have all the noob questions about any piece of software: integrations, automation, process. My end goal is to setup a Veeam B&R at each client site correctly to include SureBackup validation and verification for Hyper-V. Goals: Troubleshoot VSS prior to the backup commencing to reset anything that would cause the backup to fail (host and guest I created a powershell script for this that works for powershell 1 by the old method of registering the dlls. For powershell 2+ it restarts vss (had some machines that wouldn't even list writers), and then restarts the service for any writer that isnt in a stable/no error state. I am just not sure how to test it. Any ideas? Ticket\Email\Report on successful 'SureBackup' jobs per VM with a screenshot of the VM (I know it should just be a login screen) I know how to take a screenshot of the machine with powershell, just not how to save it to the 'active' machine so the ticketing system/email server could see it. Monitor for failures to create tickets (builtin to the B&R plugin as far as i can tell). I would like to add the backup log for that job to the ticket (the part in the GUI that tells you exactly where it failed, i.e. if you check the box for SQL Server on a non-SQL server it shows backup with errors, what error?) @Vitaliy S. I thought you might have some input.
  11. Copy and modify the server offline monitor to target your probe machines?
  12. Have you considered monitoring it through powershell in a remote monitor? Get-Eventlog -LogName Application -After (Get-Date).AddDays(-1)| Where {($_.EventID -eq 'X' -or $_.E ventID -eq 'Y')} And then running a script that takes the appropriate action based on what events have been detected?
  13. It is installed and runs as SYSTEM. If you specify credentials in the location, those can be used in the 'asadmin' script steps.
  • Create New...