- How does the security work?
LiveStor doesn't store files with their native file name. They are stored with a unique identifier. The filename is related back to the database. For an intruder to access the files for the purpose of hacking, the person must have access to both the file and the database. The System Administrator is the only person with this accessibility. The only time the data is accessible is via the Internet during the upload. This doesn't pose a problem because the FTP site is locked by username and password so the accessibility there is controlled, too. The LiveStor director takes the files off the secure FTP site and stores it on the non-Internet addressable LiveStor storage server.
- What about viruses? Are there safeguards to prevent transferring them?
The application doesn't do virus scanning. But, there is no danger of transferring viruses. During the transfer, LiveStor doesn't open or view the files. This means, if your files have viruses, LiveStor will store them. You should take precautions for viruses at the local level.
- Can LiveStor run as a Windows Service?
LiveStor does not run as a Windows Service. A LiveStor user must be logged in, the machine must be up for the job to run, and the application must be left in the task tray.
- How much data can I keep on the remote server?
You determine how much data you want to store. Factors that affect the amount of storage include how much data is initially uploaded from the local machine, how much data is added, changed, or deleted on the local machine in the folders that you are backing up, and how long you want to keep changed or deleted data on the LiveStor server. You specify the duration to keep changed or deleted data when you create your LiveStor jobs. The duration is also called the time-to-store. (For more on this topic, review the other questions pertaining to LiveStor functionality and file storage.)
- Can you tell me more about the LiveStor functionality?
Initially, you upload your data with a LiveStor job in which you set how many days (duration) to keep changed or deleted data. The minimum time-to-store is 3 days and the maximum is 365 days (this may be increased later on after everyone is comfortable with LiveStor usage). When the job runs and files are stored, the individual files are flagged in the LiveStor database with the time-to-store set by that job. In this process, the initial upload is your only full backup. After that point, when subsequent LiveStor jobs run, files are handled as follows:
- New Files added to the local machine are uploaded. If these files are never changed or deleted on the local machine, LiveStor will store them indefinitely.
- Changed files on the local machine are uploaded and the previous file is flagged so that it will be deleted off the LiveStor server AFTER the Time-to-Store expires and NOT BEFORE).
- Files that have been deleted off the local machine are flagged so that they will be deleted off the LiveStor server AFTER their time-to-store expires and NOT BEFORE.
- What happens to files stored on the LiveStor server that are never changed or deleted on my local machine?
Files that have been uploaded to the LiveStor server that are never changed or deleted on the local machine will be stored indefinitely on the LiveStor server regardless of their time-to-store. The reason for this is because the time-to-store defines the duration to keep changed or deleted data.
- If I edit my job and change the time-to-store, what affect will that have on my stored files?
If the job is edited and the time-to-store is changed, the time-to-store on files previously stored is not re-flagged. In other words, previously stored files are not affected. The change only applies to files backed up after the job modification.
Let's look at a scenario:
- April 25 - Create a job named BACKUP1 that keeps changed or deleted data for 10 days. In this job, backup a file named File1.txt which is flagged with a time-to-store of 10 days. File1.txt changes each day.
- May 1 - Edit job BACKUP1 and modify the duration to keep changed or deleted data for 3 days. Backup file named File1.txt, a changed file since the original backup, which is flagged with a time-to-store of 3 days.
- In this example, versions of File1.txt which were backed up with the original BACKUP1 job are retained as necessary to meet the time-to-store of 10 days. After the job modification, versions of File1.txt have two different time-to-store values: some stored by the original job with 10 days; and some stored by the revised job with 3 days.
- How does LiveStor handle files that may be included in multiple backup jobs?
Files that are included in multiple LiveStor backup jobs are only backed up once as long as the filename (including folder path) is identical to that which was previously stored. LiveStor recognizes that files are already stored regardless of the job used to store them. If the exact file is included in multiple jobs that have different durations, LiveStor uses the duration attached to the job that actually uploads the file. In other words, the exact file will never have different times-to-store in the LiveStor database.
- How does LiveStor work with the ACS Backups?
A complete and supported automated backup feature is scheduled with ACS for Windows v7.0. This feature will allow you to schedule your ACS backups to run at a time that you prefer. The utility backs up all ACS data (with the exception of picture files), including multiple datasets, into one backup file on the local computer.
Once the ACS Auto backup job is completed, the LiveStor job copies the file to an FTP site and then to the LiveStor server. LiveStor must be installed on a machine that can access the ACS backup file. LiveStor backs up the backup file, not the individual ACS files.
- Can users be in ACS when the ACS Auto Backup runs?
The program will still run if users are accessing the ACS tables. However, the locked tables will not be backed up and a partial backup will result. It is a good idea to have users out of the program.
- Will LiveStor backup open files?
No, LiveStor will not backup open files.