Dear PM's,
I'm having managed agents by B&R and they write backups to an object storage through a very "thin link". Now if the job doesn't finish in time, it's all for nothing. That's why it's most of the time even better when the client writes directly into its local cache and syncs the data later as the sync process allows interruptions - even multiple retries. Eventually, the data will be on the target.
To achive that, I guess the client has to be offline during the backup time, the cache has to have the needed free space, but there seem to be other reasons as well. For instance, if the client looses the network during backup, but I'm not sure about it. I guess if "something" finishes the connection between server and client, it's not the same as if the client just left the network (wifi e.g.).
So, the questions is, how could I "trigger" the local cache redirect manually by e.g. killing the sessions or similar for cases where I need it. Thanks!
-
- Veeam Legend
- Posts: 945
- Liked: 222 times
- Joined: Jul 19, 2016 8:39 am
- Full Name: Michael
- Location: Rheintal, Austria
- Contact:
-
- Product Manager
- Posts: 14785
- Liked: 1722 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: how to trigger write to local cache on purpose
Hello Michael,
Right now the only way to trigger it is to temporary disable the network and wait for the job to retry. Thanks!
Right now the only way to trigger it is to temporary disable the network and wait for the job to retry. Thanks!
-
- Veeam Legend
- Posts: 945
- Liked: 222 times
- Joined: Jul 19, 2016 8:39 am
- Full Name: Michael
- Location: Rheintal, Austria
- Contact:
Re: how to trigger write to local cache on purpose
Thanks Dmitry. So if I disconnect the network DURING the backup, it won't failover to the local cache at first?
-
- Product Manager
- Posts: 14785
- Liked: 1722 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: how to trigger write to local cache on purpose
Disconnect should:
1. Fail the job
2. Start the job retry
3. During the job retry determine that repository is not accessible
4. Failover to backup cache
Then you can connect the network again.
Thanks!
1. Fail the job
2. Start the job retry
3. During the job retry determine that repository is not accessible
4. Failover to backup cache
Then you can connect the network again.
Thanks!
Who is online
Users browsing this forum: johannesk and 12 guests