FAQ

Q: Can APBackUp save my archive to remote computer or to CD-RW

A: APBackup can copy archive via LAN to Remote computer, to FTP server or through E-mail. So APBackup can copy archive to CD-RW via Packet Writing interface. In this case you need to install one of followings packets (for example): Roxio DirectCD, Ahead InCD, Software Architects Write CD-RW.

Q: When error was occurred in the task, it became inactive and stopped executing according to the schedule. How can I tune the task to postpone the task if error is occurred?

A: You can do it on the “Schedule” tab in the Task edit window. You should choice one of three variants of behavior in “If error is occurred during the archivation” panel. They are: Deactivate (by default), Postpone the task according to the schedule, Repeat in N minutes.

Q: How can I save all of my tasks and copy to other computer?

A: All tasks are saved in ArhTasks.bpd file.

Q: How can I tune tasks to executing one after one?

A: APBackup allows you to build chains of tasks. To do it you should choice “After executing the task X” kind of schedule.

Q: I have very big size of data to backup and APBackup displays error in log file. What should I do?

A: You should setup “Archiver temporary folder” in program options. One more, make sure that there is enough space on the destination drive.

Q. When I choosing source folders, I can't see hidden files and folders. What can I do?

À. APBackup uses standard Microsoft Windows dialog to choice folders, so you should setup viewing of hidden files in Windows “My computer”.

Q: When I start APBackUp as normal windows application the task work via LAN without troubles. But if I star APBackup as service the task falls. Why?

A: That is from Microsoft Win32 SDK:

“The LocalSystem account is a predefined local account used by system processes. The name of the account is .\System. This account does not have a password. If you specify the LocalSystem account in a call to the CreateService function, any password information you supply is ignored.

A service that runs in the context of the LocalSystem account inherits the security context of the SCM. It is not associated with any logged-on user account and does not have credentials (domain name, user name, and password) to be used for verification. This has several implications:

·      · The service cannot open the registry key HKEY_CURRENT_USER.

·      · The service can open the registry key HKEY_LOCAL_MACHINE\SECURITY.

·      · The service has limited access to network resources, such as shares and pipes, because it has no credentials and must connect using a null session. The following registry key contains the NullSessionPipes and NullSessionShares values, which are used to specify the pipes and shares to which null sessions may connect:

·      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ LanmanServer\Parameters

·      Alternatively, you could add the REG_DWORD value RestrictNullSessAccess to the key and set it to 0 to allow all null sessions to access all pipes and shares created on that machine.

·      · The service cannot share objects with other applications, unless they are opened using a DACL which allows a user or group of users access or NULL DACL, which allows everyone access. Specifying a NULL DACL is not the same as specifying NULL, which means that access is only granted to applications with the same security context. For more information, see Allowing Access. · If the service opens a command window and runs a batch file, the user could hit CTRL+C to terminate the batch file and gain access to a command window with LocalSystem permissions“