rdiff-backup can be limited by the CPU, disk IO, or available bandwidth, and the length of a session can be affected by the amount of data, how much the data changed, and how many files are present. That said, in the typical case the number/size of changed files is relatively small compared to that of unchanged files, and rdiff-backup is often either CPU or bandwidth bound, and takes time proportional to the total number of files.

In general, rdiff-backup does not strive to make newer clients compatible with older servers (or vice versa). However, there is no intention to purposefully make different versions incompatible across the network -- changes are introduced primarily to fix bugs or introduce new features that cannot be implemented without breaking the network protocol. Furthermore, rdiff-backup does try to make it possible to read older archives.

The amount of memory rdiff-backup uses should not depend much on the size of directories being processed. Keeping track of hard links may use up memory, so if you have, say, hundreds of thousands of files hard linked together, rdiff-backup may need tens of MB. If rdiff-backup seems to be leaking memory, it is probably because it is using an early version of librsync. librsync 0.9.5 leaks lots of memory. Later versions should not leak and are available from the librsync homepage.

There is no internal rdiff-backup option to do this. However, external utilities such as cstream can be used to monitor bandwidth explicitly. trevor@tecnopolis.ca writes: rdiff-backup --remote-schema 'cstream -v 1 -t 10000 | ssh %s '\''rdiff-backup --server'\'' | cstream -t 20000' 'netbak@foo.bar.com::/mnt/backup' localbakdir (must run from a bsh-type shell, not a csh type) That would apply a limit in both directions [10000 bytes/sec outgoing, 20000 bytes/sec incoming].

Many of our files are served as binary files. This is due to the fact that support for binary raster files is relatively standard across platforms and image processing packages. Usually one will need the pixels and lines and relevant georeferencing information. This may be found in the metadata file issued with all data downloaded from one's Workspace. If the data was served from a project-specific page, the metadata is either included in the download or is listed on the page itself.

Yes. Web-based survey data is collected/stored and compiled into an encrypted data file. There are virtually no limitations in terms of the number of cases our systems can handle in terms of the volume of survey traffic, and/or in the management/analysis of data files. On more than one occasion, we have managed data sets as large as 1,000,000 records comprised of over 500 variables.

Lots of data from the US national data centers (NOAA, USGS, NGDC, NEIC) can be used with GMT, and they are all freely available from these centers and individuals via the internet. For Unix/Windows CD-R compilations of several Gb of Earth and Ocean science data, see Geoware's GMT Companion CD-R and DVD-R products.

The files you want to backup is race.db and race.log. You won't be able to copy these files if the database is open, so you'll have to close the application first. You'll want to keep these two files in sync and not mix them with previous backups. You can also backup your results during the race. But in the current version, there is no way to restore them. But should you have a problem during the race, contact us and we'll see what we can do to restore what you have already saved.

We recommend at least a 500mhz machine...the faster the better. Atmosphere will run with slower computers, but once you've heard the sounds, you will want to run as many Atmospheres as possible at the same time! Of course...faster is always better.

Yes. Our software uses In-file Delta Technology which means that only the changes to the files are backed up. This means that if you have a large file that changes often then only the changes to that file are transferred to the backup server, not the entire file itself. The data is automatically compressed before it is transferred to the server.

If you are looking for a particular character string you think might be unique in the document, like a geographic area name or a NAICS code, use your browser's "Find" feature (hit Control-F or select Edit | Find in this page). Adobe Acrobat also has a "Find" that works in PDFs (Control-F or click on the binoculars icon). In PDFs with many tables, use the table of contents (frequently starting on page 5).

Yes, you will need a minimum data plan from your operator. A backup and restore of 100 contacts will require approximately 16K of data. Remember that after the first backup, the application sends new changes only, so the data used is much less.

In order to automatically run your backup when no user is logged on, then you need to install the program "as a service" and add an event in the Schedule tab in order to have your backup start automatically. If the program is already installed you need to install it again as a service. When the program is running as a service under Windows 2003 / XP / 2000 / NT you will get the Service Options enabled in the Backup tab.

You can restore files from 30 prior backup sets. You may also restore up to 30 individual file versions.

Note first that the program saves daily backup of its database file automatically to "My Documents\Active Desktop Calendar Backup" folder. Backup and Restore options are available in the Data menu. You can also make backup copies of the program's database file by yourself. The file is named "Active Desktop Calendar.