Home Forums Discussions General Discussion Version 5.0

The AC backup is nice, but sometimes a 3rd party program like Acronis or Backup Assist can be much faster.

I stopped using AC backup and use carbonite. It only costs $55.00 per year. Go to www.carbonite.com.

Splurge? I have no money to splurge. That's why I'm backing it up to the other PC.

I have been using SmartSync Pro but I was hoping the new AC facility would let me get rid of it.

Well, then I suppose the answer is it will always take 1.5 hours or longer, but you will have 12 hours or so each night.

But, the only caveat would be that backing up to another computer would probably be the worst option. But, I guess you have to do what you have to do.

Well, the worst option is not bothering to back up at all. But I know what you mean. But, just so I know, what it it I can get to do the backup faster?

It will always be the same speed unless you don't back up the imported items.

The way to go in my opinion, would be the WD 500GB Caviar Green eSATA hard drive.

http://www.shoplinksys.com/viewprod...de=cii_9324560&cpncode=24-68845285-2

coupled with the Voyager Q to dock it:

http://www.newertech.com/products/voyagerq.php

Now, you have spent around $150, and you still may need to add an eSATA card or hope you have an eSATA connection on your motherboard.

But, you get two huge advantages:

1. It is smoking fast. It's the fastest you can transfer data there is at this time.
2. You can continue to add eSATA drives. So, if you bought a second one (HIGHLY RECOMMENDED!), you could take one home every weekend.

I would have to agree with Bert on the above post. That would be the way to go. Not only would you be able to take it home with you, but the other benefit to having this is your not over loading a computer in your office with all of your data, but if you are not looking to spend money on extra equipment what I would suggest is to exclude your imported items in your backup. This will speed up your backup time significantly. Your database itself is not that large and it is already compressed. The imported items are not and the backup utility has to compress it, this can take a very long time if your imported items folder is, for example, 10+ gbs in size. However, not backing up your imported items would not be wise. What I recommend you do is to backup your imported items at an interval that you feel is appropriate. You don't even have to include it in your backup. Just make a copy of the folder and place it somewhere. The imported items folder is not part of your SQL database, therefore you can just copy and paste it without disturbing SQL.

Joe

Tlelio or Tech Support:
how would / does carbonite deal with AC's SQL database? Or are you suggesting to let carbonite "backup" the backup, so to speak?

And, I as well, competely agree with Joe. Do your local backups. Take home one when you feel you should. If you truly feel the need to do offsite backups, back up your data only through AC. Just back up your imported items locally.

Newer beta is on same site as before - now 5.0.23 and this has fixed some of the errors particularly related to immunizations.

I had a few computers which did not like the upgrade and gave errors. See below

Windows Server 2003 - worked fine.

Windows XP Pro machine gave error - I uninstalled previous version of AC and ran installer, worked without a hitch.

Windows XP home machine - gave an error on install and did above also without hitch.

It seems that one of my installs was given a glitch and said the files were in use because one of my other machines was logged into AC - I closed it and it ran fine.

I did fresh install on Windows 7 Home Premium 64 bit machine - installed, gave errors of "may not have installed correctly" in a few places, ignored and in the end it worked fine.

Upgrade wss from 5.0.22 - all in all it was okay and up and running now.

see my note under iV5 - injections being mported?? but I had major problems upgrading. It took over 4 hours and had to uninstall, but completely, not by the AC uninstaller.

This was the most time consuming upgrade since probably V4 initial.

The joys of beta testing

I don't have the knowledge to answer this question, sorry.

So far the biggest bug in V5 is when you order a lab/imaging, if you print the order, then close the print box, you have to re-size the minimized lab/imaging area to click save order (since I do not send orders for tracking I just want them saved to plan). The computer 50% shuts AC down as a object not found error comes up. Could tech please let me know if they are working on a fix. 50% of the time I can save the order, the other 50% AC shuts down and I have to restart and recover the note.
Jack

I am having V5.0.22 shut down maybe 3 to 5 times per day ( so maybe 10% or less of the charts I am working on).... off the top of my head seems like this is occurring when I am in the plan section trying to send orders or in the prescription window. I have not mentioned this to technical support partially because I had this happen a lot when I was a new user of V4 back in April 2009 and it gradually happened less and less frequently back then, disappearing after a month or two. It was so unpredictable and sporadic that tech support could not pin it down/reproduce it. AC always opens back up quickly and lets me resurrect the open chart that I was working on, so I have not been too stressed out about it.

True, just annoying, but I can pinpoint when it is happening so hopefully we can fix the glitch

Dumb answer, but have you tried running Amazing Utilities to clean up the database? Maybe after everything is up and running, it just needs a tweak or two.

That's not dumb, I am trying right now!

Sorry for being slightly off-topic here. Could someone give me the link to Version 5 download please? We want to play with the version 5 and get bit more comfortable with it. I dont think we are ready to take the plunge quite yet with version 5.

Thanks
Sekhar

http://www.amazingcharts.com/5beta

Here you go.

Looks like one has to upgrade all the workstations to V5. I was hoping the new DB would be backward compatible with V4 clients so that I wont have to do all the workstations.

No, you pretty much always have to update the database each time.

Why would you want v4 on clients anyway. Wouldn't that defeat the whole purpose of upgrading to v5

Well I did not want the staff to freakout over on monday with something different. But i went ahead and upgrade everyone over the weekend ( 7 stations).