Home Forums Discussions Problems Back up to network drive

I have an odd problem for which I'm sure there is a very simple solution. I back up AC to a "server" in my office. This is essentially a home server and I only use it for back-ups and not a true server. It is networked. AC will back-up to the chose file location on this server if I do a manual backup under the backup utility. But when I have it set for auto backup, it will never write to the file location claiming lack of access.

I thought this may be do to some log on issues but if that was the case, the manual backup shouldn't work either. Correct?

Any ideas?

What version are you using, Travis? Did you recently upgrade?

Hi Travis,

We are running into the same situation. It started with the first v6 upgrade (6.0.9), but there was so much else going on at that time it was low low priority, and since then we have just lived with it. It has persisted through 6.1.1 and 6.1.2.

We use AC to back up to an internal D drive, an external F drive, another PCs D drive, and AC offsite.

When I manually run backup, which I do just before leaving each day, all write successfully.

When the AC automated process runs overnight, it generates an error email "Backup failed", and it writes to all EXCEPT the other PC.

My (lazy) response to this: Live with it.

Gene

It could be a permissions issue. Maybe AC is trying to use the local system account to authenticate against the network server.

Try mapping a network drive and then backing up to that.
Win 7: http://i278.photobucket.com/albums/kk94/sandeepluthra/Tutorials/3b11f13f.png

Win XP: http://s278.photobucket.com/albums/...ls/?action=view&current=1782cb11.png

Interesting Gene. Now that I think about it, it has happened every since the 6.1 upgrade. We're apparently having the exact same issue. I'm obviously living with it and have been manually backing it up to the server weekly. It has no problem automatically backing up to a USB drive automatically so I have a daily back-up on the main computer and USB drive at least.

Sandeep, I actually did this and it failed as well. I mapped a network drive to z: and it still wouldn't back it up on the automatic back-up but had no problem when I clicked on manual backup.

I thought it was permissions issue as well but with a failure writing to a mapped drive and success with a "manual" back-up, I just don't understand it. I simply have my office set-up as a workgroup of computers without a domain so that should be fairly simple as well. I'm stumped a little and will continue to try different things.

Sandeep had it correct. I think it depends on the user account versus the local account. It even gives you the option for making the changes.

Bert and/or Sandeep,

Main computer is Win7Pro

Backup that is not working is WinXPPro.

Workgroup for WinXP is MSHOME (original, right?)

What do I use for Domain?

A really really basic question, I know.

Thanks. Gene

Use that computer's name and a user account on it. Not the user account on your main computer. Unless it's the same. Make the same user account with the same password on both computers. (P2P downside ha).

Yeah this is one of those times for being on a domain is helpful. All computers would be authenticated against the server and which service likely wouldn't matter. But, a small reason to go with a domain.

The backup program can be on any computer as it uses the .xml file to know where the databases are. However, if you still have trouble, I would at least try using the backup program on the main computer.

As far as workgroup names, there are only a few limitations. They generally have to be less than 15 characters. They can't have spaces. They can't match any computer name but must match all of the other workgroup names. MSHOME and WORKGROUP are just default workgroups with MSHOME being newer. But, you could have Amazing or Snowman, doesn't matter. Just play around with it, you'll get it, just get off the local service.

MSHOME is older. From the XP days. Windows 7 default is WORKGROUP.

That seems right. I read it the other way around online, but it hasn't been my experience. Not a big deal really.

Yep, Microsoft tried to simplify things with the HomeGroups in Win 7. People were often surprised when shares weren't popping for computers on the same network. That will put on the same workgroup assuming everyone is using Win 7.

So Travis (and Gene): this happened to us and others with the 6 upgrade (which is why I asked about your version), and hopefully it explains your issue.
True confessions... when it happened, we called support and they fixed it right away (I know...who would ever call them when you have Bert and Sandeep?).

Why go to Sandeep, me or support, when the answer seems to be right on the program. I do think you need to change the settings on the main computer. Can't hurt to do both.

So at the risk of identifying myself as an old curmudgeon (which may well be accurate):

1) This issue arose during "The Dark Times" (v6.0.9, when we had close to a nonfunctional system for 2 weeks, bought a new laptop, video cards, etc) so initially it was VERY low priority.

2) I have become accustomed to running a manual backup daily, which works fine. This obviously is also a safeguard against the automated backup not running at all.

3) ***Curmudgeon alert**** I have a functioning system now, I have a perhaps irrational, perhaps not, fear of messing things up.

So, as irrational as this sounds to those of you who are really good at networking, I think I will leave ours alone!

Gene

Gene, I also do manual backups, and you seem to be the only one who also does.

But, changing the way your backup is identifies the system won't screw up your network.

Plus, I think you owe it to us who have spent a good deal of time coming up with ideas.

Bert,

I owe you, and Sandeep, and many other board contributors lots and lots and lots.

Lets not confuse this with irrationality and laziness!!

Gene

And I thought real men never stopped to ask for directions, and never ever called tech support.

Curmudgeon

Dear curmudgeon: For months, I couldn't figure out how to save a chart. But, then John showed me where the "Sign-off" button was. But, try as I might, other users kept telling me to call tech support. I did, and they told me you can't save a chart on Windows Server 2008.

PS: I back up manually every night, and I probably forget about five times a year.

Lol this is exactly how I got started. Hatred of the Geek Squad is good motivation.

I couldn't get my RDC to securely connect to all of my computers. I kept entering billing in the destination. Then Sandeep told me "billing" isn't routable and to use the FQDN. But, I found it easier to call Microsoft and pay them $259. They told me to use my FQDN.

So, I entered billing.pediatrics.local and I connected right away.

Please no offense to anyone. I just find it interesting to ask a question on the board, get perfectly good answers, yet someone would find it necessary to go to tech support. Why not just go to tech support.

Bert,

I like to work on our vehicles. If I am on a Subaru forum and I ask a question, and the answer comes back, "Check the resistance of the MAF sensor and, if out of specs, replace it," I will get out the ohmmeter and wrenches and go to it.

Someone else may get that response and say "Time for a trip to the dealer."

Some of the stuff that is second nature to you is not so obvious to some of us!

On the other hand, if I just go to the dealer, I may have a fixed vehicle, but I did not learn anything in the process.

Even if I (or anyone else) do not take your advice, I certainly learn from it. And it is always appreciated.

Gene

Fair enough. First, I wouldn't even be posting if Jon hadn't whispered.

OK, I would understand if I said, "To install active directory and create the first domain controller in a new Windows Server 2008 forest, you must keep the following considerations in mind...

You must make forest and domain functional level decisions that determine whether your forest and domain can contain domain controllers ....

But, this is a solution that AMAZING CHARTS put in. You simply put in your username and password unless it also needs the workgroup which I doubt. Part of my suggestions and recommendations are that they are guaranteed NOT to break your network. It is almost impossible to break a workgroup. Domains yes, as you are interacting with Active Directory, using DNS, DHCP, Group policy, Internet Information Services and much more. Not trying to brag about domains, but it is very easy to break DNS or IIS. (Not to completely contradict Sandeep's and my statements about how easy client/server is.

But, I understand. I would be interested in seeing what tech support says.

And, yes, in the hierarchy of server OS, there are forests.

Gene, don't you love it when he is kind enough to prove your point?

But I think you just did!

But I can't see the forest for the trees!

Gene

Well, I actually had already tried entering the UserName Password but AC would never authenticate the username/password and would always say it couldn't verify the username/password. So I never have been able to change that. I'll keep trying different usernames/passwords but without a Domain, it may just not work.

I may end up having to contact tech support which would only be the first time in 3 years.

I was just confused why you could do a manual backup but if the auto backup needed a username/password? Just a bit odd.

I never trust myself to do a manual backup routinely. I'm not in the office all day every day to remember that.

Right JBS. We are just smarter, lol.

By the way, I just now read the first post. It says lack of access. Is that the ACTUAL error message? Is there a number or a longer error message?

Try using the same username and password on both computers. Also, do what Bert said above with the User Accounts. (http://amazingcharts.com/ub/ubbthreads.php/topics/44904/Re_Back_up_to_network_drive#Post44904)

I keep getting this error as well when trying to change username/password.

I'm also getting a different error message during auto-backup now that I changed it to a mapped drive. I can't recall the exact message but something to the effect of "could not find part of the path specified".

Again, manual backup works like a charm.

Travis, may I remote in and take a look? It's got me curious.