Perform the mode switch, which will now go through.ĥ. Start the program from the command line with "-c Q:\Temp\Bvckup2" option.Ĥ. Move (by copying) %LocalAppData%\Bvckup2 folder to a temporary place on the %ProgramData%'s volume. The workaround for this case is as follows:Ģ. This means that the mode cannot be switched if the interactive user profile and %ProgramData% folder are located on different volumes. That is, mode switching expects to be able to _move_ the engine folder.
Silently falling back to the copying caused the switch to suddenly take minutes instead of seconds and this led to all sorts of usability problems. This was done because the file block-hashes generated by delta copying are stored in the engine folder and these may grow to a substantial total size. If this too fails, the mode switch will be aborted.Įarlier versions of the program fell back to _copying_ the folder, but this behavior was deprecated. If it fails, it tries moving the folder with a conventional move operation. When moving the engine folder, the program first attempts to move it using transactional NTFS rename operation. Exact failure codes are TBD, please get in touch if you need help interpreting them. The result of the switch is indicated with a process exit code. Which is meant for switching newly installed app instances that haven't been run yet.Īs of release 81.15 there's also a shortcut command for rolling the program back to the desktop mode:īvckup2 -force -console %LocalAppData%\Bvckup2 just-service - installs bvckup2 service, but skips the config move atomically - limits the switch to atomic NTFS move onlyĪlso, when switching to the service mode: force - forces skipping over certain errors Several additional parameters are supported by -set-mode command: To ensure this you can shut down the app from the command line using "terminate" command. The app must NOT be running when the switch is made to the service mode. Whereby points at app's configuration directory in desktop mode.
Bvckup 2 block options password#
The benefit of the second option is that the share access password is not getting stored in Bvckup 2 configuration, so it provides for a better security if one is required.Īs of Release 76 it's also possible to switch the mode from command line using the following command: Grant this account required access rights on the share end. Switch service to run under this account, using Service Manager.Īdd this new account to the Backup Operators group. ⦁ Create a separate user account for the "bvckup2" service. ⦁ Configure share access credentials in Bvckup 2 itself Second, if said remote share requires authentication, then you have two options: It will also most certainly will not have the access to any of the user's mapped network drives as these are a per-account property.įirst, if you are backing up to- or from a remote share, you *must* use explicit network paths, such as \\server\share\path. Keep in mind that in a service mode the engine part runs under a different user account and as such it will not generally have the access to any shares that might be accessible to the (desktop) user account. See Menu > Help > "Upgrade to Pro" for details.
Bvckup 2 block options upgrade#
If you are on a Personal license and require support for using the program in service mode, you will need to upgrade to the new Pro license.
Bvckup 2 block options windows#
The other two - no support for running on Windows Servers and, the main one, the unconditional restriction for any sort of work-related use. This was one of 3 differences between two legacy license types - no tech support for running in the service mode. Under Personal licenses the program may be used in service mode, but doing so voids all access to the tech support. In this mode, logging out of Windows closes the user interface, but leaved the engine running, so Bvckup2 continues to make backups even if no one is logged in.Ĭompatibility with (legacy) Personal licenses The user interface continues to run as a regular desktop program and it can be started and stopped at will.
The backup engine is installed as a Windows system service and it in the background, at all times. In service mode, the program splits the engine and user interface into two separate processes. Exiting the program stops both the engine and the UI, meaning that you need to be logged into Windows *and* to be running the program for the backups to run. In desktop mode, which is the default, program's user interface and its backup engine share the same process, so you see a single instance of bvckup2.exe on your Task Manager list. Bvckup 2 can be run in one of two principal modes.
0 kommentar(er)
