Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| movecopy [2020_12_30 10:06] – [Copying files] jim | movecopy [2024_02_28 01:03] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ## Copying files | ## Copying files | ||
| - | Copying files from one folder or bucket to another or from one cloud provider to another can be performed in the File Fabric | + | Copying files from one folder or bucket to another or from one storage |
| The procedure for copying will be different dependent on the client used. | The procedure for copying will be different dependent on the client used. | ||
| Line 13: | Line 13: | ||
| Transfer of single files is generally synchronous. The client waits until the copy is completed. | Transfer of single files is generally synchronous. The client waits until the copy is completed. | ||
| - | If multiple files are copied then this may be delegated to the Task Manager and executed in the background asynchronously. Background asks can be monitored through the Task Manager when logged into the File Fabric | + | If multiple files are copied then this may be delegated to the Task Manager and executed in the background asynchronously. Background asks can be monitored through the Task Manager when logged into Access Anywhere |
| Line 25: | Line 25: | ||
| - Copy file to new location | - Copy file to new location | ||
| - | - Move existing file to trash (where possible) | + | - Move existing file to trash (where possible |
| As with copying files the procedure for moving files will be different dependent on the client application used. | As with copying files the procedure for moving files will be different dependent on the client application used. | ||
| Moving files are generally executed asynchronously | Moving files are generally executed asynchronously | ||
| + | |||
| ##Rename | ##Rename | ||
| Line 48: | Line 49: | ||
| ### Locking | ### Locking | ||
| - | When files are being copied or moved locks are put in place on the parent folder to prevent other actions creating data integrity issues. These locks are removed once the operations are complete, but if this is occurring on a team folder and other users attempt to process file operations that encompass delete, update or modify then they will be unable to do so until the processes are complete. | + | When files are being copied or moved locks are put in place on the parent folder to prevent other actions creating data integrity issues. These locks are removed once the operations are complete, but if this is occurring on a team folder and other users attempt to process file operations that encompass delete, update or modify then they will be **unable to do so until the processes are complete**. |
| ###Audit Logs | ###Audit Logs | ||