Koozali.org: home of the SME Server

backup2ws no go to win2k3 server share?

Offline dilligaf

  • *
  • 266
  • +0/-0
    • http://www.willcraft.com
backup2ws no go to win2k3 server share?
« on: October 09, 2005, 12:07:07 AM »
I have an SME 6.01 (all updates)
And the Backup2ws contrib.
I can get ti to backup2ws to XPPro PC share no trouble, but no way to a Win2K3 Server share.
Have full read and write permissions etc on the share.
The Win2K3 server is a PDC, but shares other folders to other users on same network with same permissions no problem.
Any ideas what t look at?

gbaird

Permissions
« Reply #1 on: October 09, 2005, 05:59:52 PM »
Permissions for the user trying to create the backup file
on the windows box

also sometimes the location can give trouble

IE:  //HOSTNAME/backup not //hostname/backup

note the caps for hostname

maybe try to ftp to the backup folder with the username/password
see if lets you in

Offline dilligaf

  • *
  • 266
  • +0/-0
    • http://www.willcraft.com
backup2ws no go to win2k3 server share?
« Reply #2 on: October 09, 2005, 06:39:02 PM »
The permissions are all cool, same user from any pc, can create folders / files, delete, etc.

tandum

backup2ws no go to win2k3 server share?
« Reply #3 on: October 09, 2005, 07:08:22 PM »
I'm pretty sure that in a windows domain the domain server needs to have a machine registered with it before a user can access the domain from that PC. In windoze you join the domain from the Windoze PC. This adds the machine as a domain user and sets up a trust relationship on the network. I dunno how to get a samba box to enter a trust relationship with a windows domain unless you are using samba 3.x.

Offline Deamon

  • **
  • 22
  • +0/-0
backup2ws no go to win2k3 server share?
« Reply #4 on: October 26, 2005, 08:24:47 PM »
The problem is the NTLM authentication, for some reason you can't connect to a windows domain controller ( I assume that the windows 2k3 server is a DC) when you try to connect to a windows 2k3 member server it will work fine.

I've used the following work-around:
Create an information bay (e.g. sme-backup)
Create a backup job and use the network share on your SME server mentioned as above.
Exclude this information bay in the backup job.
Use NT backup or other backupsoftware on your Windows server and backup the network share on your SME server.

Why the exlusion?
Because u will create a backup from a backup from... etc, in no time (I mean several days!!!)a server which contains e.g. 2Gb of data will have a backup file of 20 Gb  :-o

Regards,
Ronald
......