Skip to content

Commit de67a38

Browse files
docs(s3): add troubleshooting to veeam tutorial MTA-4808b (#3447)
* docs(s3): add troubleshooting to veeam tutorial MTA-4808b * docs(s3): update * docs(s3): update * Update tutorials/veeam-backup-replication-s3/index.mdx Co-authored-by: Jessica <[email protected]> --------- Co-authored-by: Jessica <[email protected]>
1 parent 05550e0 commit de67a38

File tree

1 file changed

+79
-1
lines changed
  • tutorials/veeam-backup-replication-s3

1 file changed

+79
-1
lines changed

tutorials/veeam-backup-replication-s3/index.mdx

Lines changed: 79 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -158,4 +158,82 @@ The following schema represents the functionality of Veeam Backup and Restore wh
158158

159159
Veeam proceeds with the backup and stores data on Object Storage. To verify it, log yourself into the [Scaleway console](https://console.scaleway.com), enter the Object Storage section, and choose the Bucket used for Veeam. Several files and folders created by the application are visible:
160160

161-
<Lightbox src="scaleway-veeam-backup-files.webp" alt="" />
161+
<Lightbox src="scaleway-veeam-backup-files.webp" alt="" />
162+
163+
## Troubleshooting
164+
165+
This section is designed to help you solve common issues encountered while performing the actions described in the procedure.
166+
167+
### Bucket access errors
168+
169+
#### Error messages
170+
171+
- `Failed to preprocess target Error: S3 error: Access Denied`
172+
- `Error: Shared memory connection was closed.`
173+
- `Failed to upload disk 'shadowSpec>'`
174+
- `Agent failed to process method {DataTransfer.SyncDisk}.`
175+
176+
#### Cause
177+
178+
The application cannot access the S3 resource.
179+
180+
#### Solution
181+
182+
If you encounter one or several of the error messages above:
183+
184+
- make sure that you have the `ObjectStorageFullAccess` [IAM permission](/identity-and-access-management/iam/concepts/#permission).
185+
186+
- make sure that there is no [bucket policy](/storage/object/api-cli/bucket-policy/) preventing the application to access your bucket.
187+
188+
### Too many requests error
189+
190+
#### Error messages
191+
192+
- `Error: S3 error: Too Many Requests`
193+
- `Code: Too Many Requests`
194+
- `Shared memory connection was closed.`
195+
- `Agent failed to process method {DataTransfer.SyncDisk}.`
196+
197+
#### Cause
198+
199+
Scaleway Object Storage applies a rate limit on PUT operations for safety reasons.
200+
201+
#### Solution
202+
203+
You can limit the number of concurrent tasks and update the timeout duration of S3 requests on the Veeam Backup & Replication server managing the backup copy operation by adding the elements below:
204+
205+
```
206+
HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
207+
208+
S3ConcurrentTaskLimit
209+
Type: REG_DWORD
210+
Value: 8
211+
212+
Type: DWORD
213+
Name: S3RequestTimeoutSec
214+
Value: 900
215+
216+
Type: DWORD
217+
Name: S3RequestRetryTotalTimeoutSec
218+
Value: 9000
219+
```
220+
221+
Then, restart every Veeam service, or restart the Veeam server.
222+
223+
<Message type="note">
224+
You may experience reduced throughput due to the limitation.
225+
</Message>
226+
227+
### Going further
228+
229+
If you did not manage to identify the error and solve it by yourself, [open a support ticket](/console/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below:
230+
231+
- S3 Endpoint (e.g. `s3.fr-par.scw.cloud`)
232+
- Bucket name
233+
- Object name (if the request concerns an object)
234+
- Request type (PUT, GET, etc.)
235+
- HTTP status code
236+
- Date and time (timestamp)
237+
- User-agent (SDK, client, console, etc.)
238+
- Transaction ID (if possible)
239+
- Log / trace of the error (if possible)

0 commit comments

Comments
 (0)