This sounds too good to be true. I'd love to try this out and/or assist with this project. I'm evaluating backuppc for a similar setup, and if it seems to work as well as this sounds, would recommend it to be implemented more broadly across our whole campus.
Let me know how I can help, either by testing, by installing locally and giving feedback, etc. hjm On Wednesday 07 June 2006 14:01, Tom Glancy wrote: > We are testing a self-service approach that allows users to initiate their > own BackupPC back up services. The implementation uses PHP and some bash > shell scripts to create an install bundle for the client, and to make the > necessary server-side modifications (hosts file entry, back up directory, > custom config.pl.). So far, this is working very well. > > Purpose: > Allow users to easily sign up and install BackupPC service > > Assumptions: > Any user with the network account can sign up for BackupPC service > The user is using a Windows 2000 or Windows XP computer > The user is logged into and signing up from the computer to be backed up > rsyncd service is not running on the client computer > > Steps: > 1 - User visits Sign Up web page on a web server that explains install > process, with a link to sign up on BackupPC server 2 - User authenticates > to the BackupPC html server using network account (ldap authentication) 3 - > User is presented with a generic list of drives, checks the checkbox for > drives to back up, clicks "sign up" 4 - System uses nmblookup to look up > computer name from IP address 5 - System checks BackupPC hosts file and > adds user name (from Step 2) and computer (if not already there) 6 - System > creates the pc directory from the computer name, to hold back ups (if not > already there) 7 - System creates install directory in pc directory, to > hold install files 8 - System generates a random user name / password > combination for rsync to use, different from network user name / password 9 > - Using a template, system creates the client rsyncd.conf and > rsyncd.secrets files in the install directory 10 - Using a template, system > creates the user's custom config.pl file in the pc directory 11 - System > creates a self-extracting zip file containing rsyncd.conf, rsyncd.secrets, > cygwin1.dll, cygrunsrv.exe, README and an install.bat file (uses Filzip > SFX) 12 - System writes config.pl, rsyncd.conf, rsyncd.secrets to user's > LOG file 13 - System returns the self-extracting zip file to the user's > browser 14 - User saves, then executes the self-extracting zip file > 15 - On the user's computer, the self-extracting zip file creates a > \backuppc directory, extracts all the files to it, and runs install.bat 16 > - install.bat runs cygrunsrv.exe to install rsyncd as a service, configures > Windows XP filewall to allow BackupPC via rsync 17 - Finished - user is > prompted to browse to the BackupPC page > > > Regards, > Tom > > > > --------------------------------------- > Tom Glancy > Ecological Services Division IT Supervisor > > [EMAIL PROTECTED] > 651-259-5097 > > Minnesota Department of Natural Resources > 500 Lafayette Road - Box 25 > St. Paul, MN 55155-4025 > --------------------------------------- > > > > _______________________________________________ > BackupPC-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/backuppc-users > http://backuppc.sourceforge.net/ -- Harry Mangalam - NACS, E1127, Engineering Gateway, UC Irvine 92697 949 824 0084(o), 949 285 4487(c) [EMAIL PROTECTED] _______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
