Backup Media Drive over WiFi - Revision history

Xorg at 23:17, 14 April 2010

2010-04-14T23:17:23Z

Xorg at 01:11, 12 April 2010

2010-04-12T01:11:57Z

Xorg at 16:59, 7 April 2010

2010-04-07T16:59:42Z

Xorg: /* Troubleshooting */

2010-04-07T16:21:40Z

Troubleshooting

Xorg: /* Troubleshooting */

2010-04-07T16:20:58Z

Troubleshooting

Xorg: /* Alternate Methods/Other Platforms */

2010-02-26T21:46:23Z

Alternate Methods/Other Platforms

Xorg at 21:37, 26 February 2010

2010-02-26T21:37:34Z

Xorg at 15:59, 22 February 2010

2010-02-22T15:59:03Z

Xorg: /* How to Remove */

2010-02-08T16:28:10Z

How to Remove

Xorg: /* How to Remove */

2010-02-08T16:26:09Z

How to Remove

← Older revision		Revision as of 23:17, 14 April 2010
Line 74:		Line 74:

	The first backup may take hours. I was getting 2GB/hour, though it varies, so plan first run accordingly. You should run the first full backup while charging the phone. If this is successful, setup scheduling. If backup quits in middle, due to power timeouts, restart manual backup again while charging. If you cannot successfully get a backup started, check Troubleshooting section below. If overclocking phone, be careful as the first run may overheat phone. Monitor temp or put phone in front of fan on first run. I have not had overheating problems but it is possible.		The first backup may take hours. I was getting 2GB/hour, though it varies, so plan first run accordingly. You should run the first full backup while charging the phone. If this is successful, setup scheduling. If backup quits in middle, due to power timeouts, restart manual backup again while charging. If you cannot successfully get a backup started, check Troubleshooting section below. If overclocking phone, be careful as the first run may overheat phone. Monitor temp or put phone in front of fan on first run. I have not had overheating problems but it is possible.
		+
		+	By default, full backup does not backup /media/internal/.palm as it is also in /media/cryptofs.
		+
		+	You will see these errors after every backup. Not sure what the deal is but everything pertinent should be backed up. I believe it has issues with . (current dir). Confirm by checking file count (minus /media/internal/.palm).
		+
		+	rsync: failed to set times on "/mnt/fullbackup/.": Permission denied (13)
		+	rsync error: some files could not be transferred (code 23) at main.c(977) [sender=2.6.9]
		+

	'''Scheduling'''		'''Scheduling'''

@@ Line 8: / Line 8: @@
 - This will backup the USB drive but not the cryptofs apps or PreWare data.
-) Full Media Backup of /media '''(coming soon)''' (mbk)
+) Full Media Backup of /media '''(now available)''' (fbk)
 - This will backup the USB drive as well as cryptofs and PreWare data.
@@ Line 58: / Line 58: @@
 - bck) partial media backup menu - backup /media/internal only<br>
 '''or'''<br>
-- mbk) full media backup menu - backup all of /media<br>
+- fbk) full media backup menu - backup all of /media<br>
 Perform initial setup...<br>
@@ Line 71: / Line 71: @@
 From backup menu...
-- pbn) perform backup sync now
+- pbn) perform backup sync now (manual backup)
-The first backup may take hours.  I was getting 2GB/hour, though it varies, so plan first run accordingly.  You should run the first full backup while charging the phone. If this is successful, setup scheduling.   If not successful, check Troubleshooting section below.  If overclocking phone, be careful as the first run may overheat phone.  Monitor temp or put phone in front of fan on first run.  I have not had overheating problems but it is possible.
+The first backup may take hours.  I was getting 2GB/hour, though it varies, so plan first run accordingly.  You should run the first full backup while charging the phone. If this is successful, setup scheduling.  If backup quits in middle, due to power timeouts, restart manual backup again while charging.  If you cannot successfully get a backup started, check Troubleshooting section below.  If overclocking phone, be careful as the first run may overheat phone.  Monitor temp or put phone in front of fan on first run.  I have not had overheating problems but it is possible.
 '''Scheduling'''
@@ Line 91: / Line 91: @@
 - Future backup runs with few changes may only take about 2-5 minutes to run, depending on total number of files and size of changed/new files.
-- Overclockers should monitor temp on the first backup.  Might want to place phone in front of fan or remove the overclock temporarily for first run.
+- Overclockers should monitor temp on the first backup.  Might want to place phone in front of fan or remove the overclock temporarily for first run.  Followup differential backups should not be an issue.
 - If you delete a file on media drive, it will NOT delete on the Windows backup folder.  Future versions may allow you to control this.
-- If you quit a backup or if disrupted in the middle, no problem.  Just run again and it will pickup where it left off.
+- If you quit a backup or if disrupted in the middle, no problem.  Just run again (scheduled or manual) and it will pickup where it left off.
 - If a backup is running on local WiFi at home and you leave with phone in pocket and it switches to EVDO, no problem.  The backup will timeout (2 minutes) and cleanly exit.  It will pickup where it left off on the next scheduled (or manual) run.
-- Backup skips encrypted .palm directory (partical backup method), so does not backup the applications. It's not likely a restore would work, so not going there.  For full backup, it's not guaranteed a full restore of /media/cryptofs will work, but it will allow for partial restores on a file basis.  Great for restoring game saves, etc.
+- Backup skips encrypted .palm directory (partial backup method), so does not backup the applications. It's not likely a restore would work, so not going there.  For full backup, it's not guaranteed a full restore of /media/cryptofs will work, but it will allow for partial restores on a file basis.  Great for restoring game saves, etc.
 - A backup runs at lowest priority so doesn't impact performance of other apps.  Was running Need For Speed during full backup and not one skip in NFS, very smooth.  Assassins Creed ran great.  Backups may impact load times however since it impacts IO more than CPU, but even load times were acceptable.  There doesn't appear to be any noticeable performance impact to other webOS usage due to this.  Even cron runs at a lower priority.

@@ Line 1: / Line 1: @@
 == Overview ==
-This tool creates scheduled backups of /media/internal (usb media drive) to a Windows computer over WiFi.  It could also work with NAS drive/Linux/Mac that are setup for cifs/samba access.
+This tool creates scheduled backups of /media/internal (usb media drive) or all of /media to a Windows computer over WiFi.  It could also work with NAS drive/Linux/Mac that are setup for cifs/samba access.
-As with all webos-internals solutions, this function comes with no warranty.
+There are two methods:<br>
 == How this method works ==
@@ Line 14: / Line 24: @@
 You need the following tools/knowledge to use this service...
-- A Windows PC (or other cifs/samba server) with at least 7GB storage available<br>
+- A Windows PC (or other cifs/samba server) with enough storage available for /media data<br>
 - Terminal access to phone, Terminal app in Preware, or webOS Quick Install<br>
 - Need to know the local IP address of the backup PC<br>
 - Helps to know how to setup Windows print/filesharing<br>
 -- though the xt wizard walks you through setup
 == How to install ==
@@ Line 42: / Line 54: @@
 - adv) advanced menu<br>
 - bck) backup menu<br>
 - bis) backup initial setup
@@ Line 51: / Line 69: @@
 '''Manual Sync'''
-- adv) advanced menu<br>
+From backup menu...
-- bck) backup menu<br>
 - pbn) perform backup sync now
-The first backup may take hours.  I was getting 2GB/hour, though it varies, so plan first run accordingly.  You should run the first full backup while charging the phone. If this is successful, setup scheduling.   If not successful, check Troubleshooting section below.
+The first backup may take hours.  I was getting 2GB/hour, though it varies, so plan first run accordingly.  You should run the first full backup while charging the phone. If this is successful, setup scheduling.   If not successful, check Troubleshooting section below.  If overclocking phone, be careful as the first run may overheat phone.  Monitor temp or put phone in front of fan on first run.  I have not had overheating problems but it is possible.
 '''Scheduling'''
-- adv) advanced menu<br>
+From backup menu...
-- bck) backup menu<br>
 - sbk) schedule backup
-There is an issue with cron that it doesn't run some jobs when phone is asleep.  It will consistently sync when you use your phone or if charging.  Am working on it.  If running nightly backups, may need to have your phone charging to run, which is likely for most.  You can confirm by checking the backup log in the morning.
+Make sure a full manual backup is complete before scheduling.  There is an issue with cron that it doesn't run some jobs when phone is asleep.  It will consistently sync when you use your phone or if charging.  Am working on it.  If running nightly backups, may need to have your phone charging to run, which is likely for most.  You can confirm by checking the backup log in the morning.
 For now the scheduler only allows to pick one backup hour of the day.  After midnight is recommended as you're likely home and in local WiFi segment.  Be careful not to schedule near time of a scheduled reboot, if that is scheduled.  You can manually edit the cron table to meet your needs.  See details at end of page.
@@ Line 72: / Line 90: @@
 - Future backup runs with few changes may only take about 2-5 minutes to run, depending on total number of files and size of changed/new files.
 - If you delete a file on media drive, it will NOT delete on the Windows backup folder.  Future versions may allow you to control this.
@@ Line 79: / Line 99: @@
 - If a backup is running on local WiFi at home and you leave with phone in pocket and it switches to EVDO, no problem.  The backup will timeout (2 minutes) and cleanly exit.  It will pickup where it left off on the next scheduled (or manual) run.
-- Backup skips encrypted .palm directory, so does not backup the applications. It's not likely a restore would work, so not going there.
+- Backup skips encrypted .palm directory (partical backup method), so does not backup the applications. It's not likely a restore would work, so not going there.  For full backup, it's not guaranteed a full restore of /media/cryptofs will work, but it will allow for partial restores on a file basis.  Great for restoring game saves, etc.
 - A backup runs at lowest priority so doesn't impact performance of other apps.  Was running Need For Speed during full backup and not one skip in NFS, very smooth.  Assassins Creed ran great.  Backups may impact load times however since it impacts IO more than CPU, but even load times were acceptable.  There doesn't appear to be any noticeable performance impact to other webOS usage due to this.  Even cron runs at a lower priority.
@@ Line 111: / Line 131: @@
 - In Vista/Win7, go to Advance Settings in Share tab to create a new sharename.<br>
 - The Windows user account cannot have a space in the name or password.  If so, create a new Windows user/password with no spaces and re-run "backup initial setup".  <br>
-- First setup over local WiFi segment before attempting to backup over EVDO or external segment.<br>
+- First setup over local WiFi segment before attempting to backup over EVDO or external segment.  You'll need to understand port forwarding and router setup to get to work outside of local segment.<br>
 - If you have firewall software, you may need to open ports: 137-139, 445
@@ Line 141: / Line 161: @@
 Remove the backup setup...<br>
-- adv) advanced menu<br>
-- bck) backup menu<br>
+From backup menu...
 - rbk) remove all backup setup <br>

@@ Line 111: / Line 111: @@
 - In Vista/Win7, go to Advance Settings in Share tab to create a new sharename.<br>
 - The Windows user account cannot have a space in the name or password.  If so, create a new Windows user/password with no spaces and re-run "backup initial setup".  <br>
-- First setup over local WiFi segment before attempting to backup over EVDO or external segment.
+- First setup over local WiFi segment before attempting to backup over EVDO or external segment.<br>
 - If you have firewall software, you may need to open ports: 137-139, 445

@@ Line 111: / Line 111: @@
 - In Vista/Win7, go to Advance Settings in Share tab to create a new sharename.<br>
 - The Windows user account cannot have a space in the name or password.  If so, create a new Windows user/password with no spaces and re-run "backup initial setup".  <br>
 - If you have firewall software, you may need to open ports: 137-139, 445

@@ Line 166: / Line 166: @@
 I chose to do Windows/cifs because that is what most have available and most systems can be configured to use it.  This could be easily modified to use Mac/Linux rysnc by just using rsync daemon (cifs not necessary).  The sync scripts in /media/internal/xorgtools/plugins can be altered by likely just stripping out the cifs mounting and change the rsync command to talk to rsyncd on backup computer.  See [http://www.webos-internals.org/wiki/Xorg_Tools_-_Power_Tools_for_Power_Users Xorg Tools] page on how to modify plugins.
 == Credits ==
 Thanks much to testers... Vincent Law, navinaq, Kyusaku, rlanza1054

@@ Line 5: / Line 5: @@
 == How this method works ==
-This uses Xorg Tools to setup the configuration.
+This uses [http://www.webos-internals.org/wiki/Xorg_Tools_-_Power_Tools_for_Power_Users Xorg Tools] to setup the configuration.
-It uses webOS existing cifs filesharing and rsync to perform the backup.
+It uses existing webOS cifs filesharing and rsync functions to perform the backup.
 In a nutshell, it mounts a Windows fileshare onto webOS device and uses rsync to sync.  Cron scheduling is used to automatically run at specified times.
@@ Line 15: / Line 15: @@
 - A Windows PC (or other cifs/samba server) with at least 7GB storage available<br>
-- Terminal access to phone, or webOS Quick Install<br>
+- Terminal access to phone, Terminal app in Preware, or webOS Quick Install<br>
 - Need to know the local IP address of the backup PC<br>
 - Helps to know how to setup Windows print/filesharing<br>
@@ Line 31: / Line 31: @@
-In Terminal app or in a Terminal session...
+In Terminal app (available on Preare) or in a Terminal session...
 - Run 'xt' from linux
 Find the IP address of the backup computer before continuing.  If you don't know how to find the local IP address on your computer, this is not for you.  Use the local IP address, not the WAN address.  Best to start with local segment and then once working, tinker with router port forwarding to maybe use over EVDO and external WiFi.
@@ Line 45: / Line 47: @@
 Follow all instructions very carefully. Re-run bis if you need to change anything.
-Once installed, run a manual sync.
+After setup, run a manual sync.
 '''Manual Sync'''
-- adv) advancedmenu<br>
+- adv) advanced menu<br>
 - bck) backup menu<br>
 - pbn) perform backup sync now
@@ Line 63: / Line 65: @@
 There is an issue with cron that it doesn't run some jobs when phone is asleep.  It will consistently sync when you use your phone or if charging.  Am working on it.  If running nightly backups, may need to have your phone charging to run, which is likely for most.  You can confirm by checking the backup log in the morning.
-For now the scheduler only allows to pick one backup hour of the day.  Late night after midnight is recommended as you're likely home and in local WiFi segment.  Be careful not to schedule near time of a scheduled reboot, if that is scheduled.  You can manually edit the cron table to meet your needs.  See details at end of page.
+For now the scheduler only allows to pick one backup hour of the day.  After midnight is recommended as you're likely home and in local WiFi segment.  Be careful not to schedule near time of a scheduled reboot, if that is scheduled.  You can manually edit the cron table to meet your needs.  See details at end of page.
 == Usage Info ==
@@ Line 69: / Line 71: @@
 - The first run may take hours depending on amount of data.  Best to charge phone while doing the first full backup.  I was getting about 2GB/hour.
-- Future backup runs with few changes only take about 2-5 minutes to run, depending on total number of files and size of changed/new files.
+- Future backup runs with few changes may only take about 2-5 minutes to run, depending on total number of files and size of changed/new files.
-- If you delete a file on media drive, it will NOT delete on the Windows backup folder.  Future versions will allow you to control this.
+- If you delete a file on media drive, it will NOT delete on the Windows backup folder.  Future versions may allow you to control this.
 - If you quit a backup or if disrupted in the middle, no problem.  Just run again and it will pickup where it left off.
@@ Line 86: / Line 88: @@
 - This will also work with NAS drives that support cifs, as well as Linux/Mac/Unix setup as a cifs/samba server.  Just create a backup folder with sharename 'mediabackup' with full read/write permissions.
 == Excluding Files from Backup ==
@@ Line 150: / Line 154: @@
 You can re-install with 'backup initial setup' menu item.
 == ToDos/Requests/Updates ==
@@ Line 159: / Line 165: @@
 == Alternate Methods/Other Platforms ==
-I chose to do Windows/cifs because that is what most people have available.  This could be easily ported to Mac/Linux by just using rsync daemon (cifs not necessary).  The sync scripts in /media/internal/xorgtools/plugins can be altered by likely just stripping out the cifs mounting and change the rsync command to talk to rsyncd on backup computer.
+I chose to do Windows/cifs because that is what most have available and most systems can be configured to use it.  This could be easily modified to use Mac/Linux rysnc by just using rsync daemon (cifs not necessary).  The sync scripts in /media/internal/xorgtools/plugins can be altered by likely just stripping out the cifs mounting and change the rsync command to talk to rsyncd on backup computer.  See [http://www.webos-internals.org/wiki/Xorg_Tools_-_Power_Tools_for_Power_Users Xorg Tools] page on how to modify plugins.
 == Credits ==
 Thanks much to testers... Vincent Law, navinaq, Kyusaku, rlanza1054

@@ Line 140: / Line 140: @@
 - rbk) remove all backup setup <br>
-This remove the backup related entries in...<br>
+This removes the backup related entries...<br>
 /etc/fstab  (for older versions of xt)<br>
 /etc/hosts  (for older versions of xt)<br>
 You can re-install with 'backup initial setup' menu item.

@@ Line 141: / Line 141: @@
 This remove the backup related entries in...<br>
-/etc/fstab<br>
+/etc/fstab  (for older versions of xt)<br>
-/etc/hosts<br>
+/etc/hosts  (for older versions of xt)<br>
 /var/spool/cron/crontabs/root