Jump to content

A+ Computers

  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by A+ Computers

  1. Which backup are you trying to run, files&folders, sql or exchange?


    The backup is semi intelligent, so if no files have changed,the backup will pass over them and not bother copying them again.


    Can you confirm that there are no files in the clients backup account? from the end point software, click restore, wait until it finishes calculating, then hit next. It will show you what is actually backed up. or from the cloud, go the client account, devices, find the device and expand it. Then click view files & folders.

  2. It is my understanding that the OLB software uses VSS in its operation.

    Recently, the servers that I administer for clients (a mix of SBS2008r2 and SBS2011) have begun running out of disk space on the drives where I set the OLB software to use for caching. It may be totally unrelated, but I'm 2 for 2 at the moment and the only server that I administer without OLB on it does not have any issues. That single unaffected server is using acronis for backups and is also not using the windows server backup service for bare metal recovery.

    The issue I found is a Shadow copy storage association set to use the cache drive is set as unbound. This means it will keep storing shadow copies until the end of time, or the drive runs out of room, which ever comes first....

    You can check you own shadow storage for any unbound associations by using this command from an elevated command prompt:

    vssadmin list shadowstorage

    If any of the storage associations show the maximum shadow copy storage space as UNBOUND, you will have problems

    To correct this, you can use the following command

    vssadmin resize shadowstorage /from=X /on=Y /maxsize=Z

    For example, if your shadow copy association looks like this:

    Shadow Copy Storage association
     For volume: (\\?\Volume{800d17e9-93ca-11e1-8b0a-bcaec53eb339}\)\\?\Volume{800d17e9-93ca-11e1-8b0a-bcaec53eb339}\
    Shadow Copy Storage volume: (D:)\\?\Volume{7bc6d95a-a9ee-4282-8f68-36095fc5dc9b}\
    Used Shadow Copy Storage space: 1.711 TB (94%)
    Allocated Shadow Copy Storage space: 1.711 TB (94%)
     Maximum Shadow Copy Storage space: UNBOUNDED (922107872%)

    Your command will look like this:

    vssadmin resize shadowstorage /for=<a>\\?\Volume{800d17e9-93ca-11e1-8b0a-bcaec53eb339}\</a>&nbsp;/on=d: /maxsize=10%

    This will limit that shadow copy association to only 10% of the drive. You can also use numerical values followed by MB, GB or TB. So for instance maxsize=10GB

    the For volume; listed a drive letter, you substitute the drive letter for the volume ID

    I'm curious if anyone else is seeing unbound shadowstorage on the drives setup to house the OLB cache as well. I'm hoping this is totally unrelated to the OLB software.

  3. I have a server that I can't reboot, because...reasons


    The backup software will launch as far as the endpoint configuration portion. It will not however launch the backup agent manually or automatically. Is there a service or services that I can restart to try and fix the issue?

  4. We have a client with a rather large exchange database and an horribly slow upload speed (100kbps). For this reason, backing up exchange via OLB is just not a viable option.


    The problem we are running into is there is no option to disable the exchange backup once it is setup. I can uncheck the mailbox database, but I have no way of saving the change.


    Apart from uninstalling the backup software then reinstalling it, setting up the files/folders backup and waiting a week while it sends his files/folders data, is there any way to simply "turn off" an exchange backup?


    I have noticed the same applies to SQL backups. There is no option to save your changes when you uncheck all of the sql databases.

  5. check your caching options on the endpoint under the advanced button. Caching should be set to either Use binary compression or Use AVG online backup intellicache.

    Binary compression caches each file locally and just transfers the changes you make to a file. Intellicache only caches some of the files to save on room.

    If you are running Intellicache already, try switching to binary and see if you get the results you are looking for. Bear in mind though that this option will cache all of you backup data locally before transferring it, so whatever you backup size is, you need that much free space for the cache. The cache will need to be left alone for it to work properly, so if you can't afford the space on the local hard drive, switch to retransfer entire file (no cache) or keep it on intellicache (partial cache)


  6. I have not personally played with shadow protect as of yet, but the OLB does have retention settings, just not for files and folders. Here are my finding on all things OLB related over the last few months of dealing with the lack of documentation.

    1.The retention settings are only available for the Exchange and SQL backups. It is labeled as "keep last X days"

    2. Exchange and SQL backups are exempt from the unlimited versioning policy that is in place for files and folders backups.

    3. If you uncheck the retention period (keep last X days option) it will keep the backup copies until manually deleted.

    4. Each copy of an exchange or SQL database counts against your storage total. (2 copies of a 10GB SQL DB = 20Gb used space)

    5. You can not only have 1 copy of Exchange or SQL DB's backed up as the minimum is keep last 1 days, so if you backup your DB daily, you will have todays copy and yesterdays copy.

    6. God help you if you have an exchange or SQL backup that manages to run twice in one day, you will now have 3 copies backed up. The two from today and the one from yesterday. Remember point 4? Yea....welcome to the next backup pool. Hopefully you don't have it set to auto increment the size.

    I have made a suggestions post asking for the retention periods for files and folders, among other things. You can find it here

  7. For anyone wondering, we got this figured out finally.


    For your files & folders backup, the backup size is based on the largest version of a file that has been backed up. This means that if you suddenly have a large file that either shrinks in size (like a pst file that you compacted or a video you deleted), the space used is still based on the largest retained copy of the file. There is currently no retention policy available (that I have found) for files & folders backup.


    For exchange and SQL, take whatever size your data set is and multiply it by the number of days you have set for the retention policy (basically). Every copy of the files counts against your allocated space. So, for example, if you have 10GB of exchange data with a 3 day retention policy and you have it set to do a full backup every day, plan of allocating 30GB for that exchange backup. Of course there are also the log files to deal with, but they get truncated at each full backup, so plan your space requirements accordingly.


    There is no real manual for setting up backups for exchange and SQL from the endpoint software , only files & Folders. Hopefully this will be rectified in short order.

  8. Another week has gone by of being left in the dark on this.


    My last email from support on the issue was received on Feb 18th.


    I spoke with the Infrascale
    support team and they advised that the numbers you see for the backup sizes are
    reflective of the amount of data that will be backed up. I am still looking
    into this, as I said before your client is a bit odd. I do apologize for the
    delay. We have been spending a majority of our time with the 3.1.0 update that
    went live on the 28th of January. I will keep looking into the issue


    So they still think there is something wrong with the client, but haven't had time to actually look into the case as they've been busy with more pressing matters.....wonderful


    I'm pretty much at the end of my rope with the OLB service here. I just checked on anther client whom the dashboard shows is getting close to the 75GB cap I set for them. The OLB client shows just under 60GB of data for backup, and at the same time it tells me the client is currently using a little over 69GB of storage space. There is no exchange backup taking place, this is simply a matter of versioning being counted towards the backup limit, which we were told would not be the case.

  9. Thanks Sean, I really appreciate it.


    I did get a message from James today to say he is still looking into this, but that my client is a bit odd. I find that strange as I have no control over which version gets installed. Was there an updated version of OLB released with 3.1 that he may be confused about?


    I guess since we are now coming up on the end of the trial with no resolution in sight I should contact my account rep and see if he can hold off the billing for these clients for another month until things get sorted.

  10. ??


    When I checked out the restore feature, I have check boxes that I can check off entire folders, drives or individual files for restore.


    Are you looking at the endpoint software on the machine or at the backup from within your portal?




    I have to agree though, the OLB needs some more time to mature. We do have a good starting point though.

  11. I was just checking up on one of the servers I have OLB deployed to and was cleaning up the exchange backup data from the AVG servers.

    I then ran the exchange backup, chose to view details and unchecked the close when finishes box. The details showed, in red, that the exchange information store writer was in a failed state and needed to be restarted. I then got the device successfully backed up alert in my inbox for this device....

    Correct me if I'm wrong, but if the backup is failing to run, for whatever reason, should it not send a backup failed alert instead of a success alert?

    I did restart the service and get the backup to run properly in the end.

  12. This is just using the OLB software on its own as offered. I have been having problems with clients going over their allotted space even though the backups should total much less than the allotted space according to the OLB software and a simple directory size listing in windows.


    For instance, I have one client who has just under 26GB of data marked for backup according to the OLB software. The Portal shows they are using 40.29GB of storage space. Clearly, if they were calculating based on the largest single version of a file, the usage should reflect numbers closer to what the OLB software shows it will be backing up.


    Its much worse for my clients who are backing up exchange and SQL as their backups go over the allotted space in about a week, causing me to log into their server, open the OLB software, go to restore and delete the multiple copies of exchange and SQL databases.


    AVG is looking into it for me, so hopefully I am the only one who is seeing this and I just need to change some of the default settings or something.

  13. According to this, only the largest version of the files should be counted, but this has not been my experience so far. My experience has shown that whatever data gets backup up daily is counted against your allotment


    Q: Upon the next backup will it drop the previous backed up file and replace, or only record the changes in order to reduce storage and bandwidth? How does that count towards the set limit of backup?
    A: AVG CloudCare Online Backup always uses differential backup. Files that have not changed are not backed up. If there is a change, the new version us uploaded. Usage is always calculated based on the largest single version of a file.
  • Create New...