Search results

Jump to navigation Jump to search
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)
  • Thanks for the contribution! I'm going to move your article to the [[Troubleshooting]] section. Also, note that this only ...
    225 bytes (32 words) - 15:32, 10 July 2009
  • ...are encountering this error on upgrade, the easiest solution is to simply move the file from <tt>/etc</tt> to the specified directory. Otherwise: ...
    686 bytes (106 words) - 15:35, 4 April 2008
  • 2. on client move dir1/ to dir2/ ...
    278 bytes (42 words) - 12:07, 13 January 2012
  • This will move fairly rapidly and does not require double storage on the client. ...
    944 bytes (159 words) - 00:42, 21 June 2010
  • == Move the Data == ...
    5 KB (787 words) - 18:59, 12 April 2010
  • to move the debugging information into the relevant subdirectory. ...
    3 KB (389 words) - 14:10, 15 August 2008
  • To avoid accidents like these, restore into a temporary directory, and move the files to the correct location after inspection. ...
    2 KB (391 words) - 21:18, 30 June 2008
  • ...andates'', which is <tt>/var/amanda/amandates</tt> by default. You should move an existing ''/etc/amandates'' in the Amanda client when you upgrade Amanda ...
    2 KB (319 words) - 21:02, 30 June 2008
  • ...itecture arises from a simple observation about Amanda: its core job is to move data around. Amanda has the [[Application API]], which handles getting dat ...
    2 KB (267 words) - 19:52, 18 January 2010
  • * It is preferable to extract them to a temporary directory and then move them to the correct locations. ...
    2 KB (244 words) - 01:38, 9 January 2010
  • * [[Transfer_Architecture|Xfer API]]: generic library to move and filter data with maximal efficiency ...
    2 KB (247 words) - 14:05, 26 November 2010
  • BackupPC supports five protocols to move data from clients to the BackupPC server: Samba, rsync, rsyncd, tar, and FT ...
    3 KB (452 words) - 20:23, 13 November 2008
  • ...with the distribution. So, extract the files in a temporary directory and move them to correct directory location. For locations where files are installed ...
    5 KB (711 words) - 19:07, 1 June 2007
  • ** --export option tries to move tertiary volumes to import/export slots when completed ...
    2 KB (337 words) - 13:58, 26 November 2010
  • ...rely "remembers" that the tape came from slot 6. The user could certainly move another tape to slot 6 in the interim, which would leave chg-zd-mtx at a lo ...
    5 KB (738 words) - 20:07, 1 January 2011
  • You need to move the contents of the <code>data</code> directory to an appropriate location. ...
    6 KB (891 words) - 15:32, 1 June 2011
  • ...of backing up them all separately. For example, create /usr/home/.bkp1 and move `foo' and `bar' into it, then create links so that the original pathnames r ...
    9 KB (1,393 words) - 21:23, 23 February 2009
  • ...model sits at the core of the application. Its purpose is fairly simple: move data between a backup client and archival storage. However, it is subject ...
    11 KB (1,792 words) - 20:29, 11 May 2009
  • ...cked up files to a temporary directory. Verify the restored files and then move them to correct location. [[amrecover]] command can ''erase'' files. See [[ ...e, directory name, dump level and dump date of the backup. Now you have to move this file to the client somehow: you may use NFS, rcp, ftp. Suppose you ren ...
    21 KB (3,436 words) - 14:37, 21 April 2011
  • ** Move the cryptographic scripts into <tt>common-src/</tt>, so they can be used by ...
    12 KB (1,759 words) - 17:12, 12 June 2007
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)