#CLOUD DATA BACKUP BEST PRACTICES MANUAL#
#CLOUD DATA BACKUP BEST PRACTICES VERIFICATION#

#CLOUD DATA BACKUP BEST PRACTICES MANUAL#

Take a look at your TLG file – is it bigger than the company file itself? It’s probably time to instate a regular manual QuickBooks cloud backup as part of your company’s standard accounting procedures. It sure felt good to drag that monster to the Recycle Bin! We moved that monstrous TLG file to the desktop, and were then able to successfully Verify the file, and backup it up. Once this has been done successfully, you can delete the old TLG file.

#CLOUD DATA BACKUP BEST PRACTICES VERIFICATION#

This will allow you to proceed with the Complete Verification and backup of your file.

In this case, the best thing to do is to move or rename the. If you haven’t been doing this however, and you have a really big TLG file, it will actually prevent QuickBooks from being able to Verify and Backup the file. This must be done manually, the automated backup routine within QuickBooks does not reset the TLG file. Its as if QuickBooks is saying, “okay, we don’t need all this excess insurance, lets lose it.” If you do this on a monthly basis, not only will you have a nice archival copy of your month for historical purposes, but you will be ensuring that your QuickBooks cloud backup company file is healthy, and stays that way. This process ensures that the data file is healthy and QuickBooks then resets the TLG file. Note: This will need to be done in single user mode if you are in multiuser mode the ‘complete verification’ choice will be grayed out. On a routine basis, run the Backup routine from the File menu in QuickBooks and make sure to choose ‘Complete Verification.’ So how do we prevent this ancillary TLG QuickBooks cloud backup growth? It’s really quite simple. (Even some Intuit support agents don’t know about this issue) In the case above, the company wasn’t able to make a backup and called Intuit support during off-hours, and was erroneously told that they’d have to send their file in for a repair. This causes errors and unexpected shutdowns in QuickBooks. The problem comes because the automated QuickBooks cloud backup is trying to write to this huge TLG file in addition to doing its real work, and if it gets too big, the server just runs out of memory. Here’s one really egregious example the company file is 479MB, but the. TLG file grows exponentially faster than the actual QBW file, leading to some really, really big files, much larger than the actual QBW file. Theoretically Intuit Data services can use this to recover corrupted data should it occur. All the transactions created in your company file are duplicated in the TLG file, as a kind of QuickBooks cloud backup.

QBW.TLG file stands for Transaction LoG it’s there to help recover data in case your main file gets corrupted somehow. QBW.ND file which helps the QuickBooks Database Server manage access to the file. TLG file is one of several files that QuickBooks creates every time you open your company file in a new place. The reason for it are three little letters – TLG. Not using the actual QuickBooks Cloud Backup process can lead to trouble with your data file down the road. So now you never need to use the backup routine in QuickBooks for making periodic backups – Right? Wrong!īest practices in maintaining a healthy QuickBooks file on Cloud9 still dictates performing a manual QuickBooks Cloud Backup on a regular basis. One of the best parts of Cloud9’s hosted QuickBooks service is that your data is always backed up, painlessly, every night.

Cloud data backup best practices