This article is about the SIZE OF FILES. It sounds trivial, but at a
second glance it turns out to hold some surprises.
As an example, lets use a text file that resides on the desktop and
contains the text "Hello World". The file has 11 character, e...
A verify job, run immediately after an archive
or sometime later (through the P5 CLI), will honour the
ArchivePlan setup w.r.t the type of verify checking: at the
moment we offer checksum or file-comparisons verifies.
The checksum verify works as fol...
Very good article on ACLs and POSIX permissions:
http://arstechnica.com/apple/reviews/2005/04/macosx-10-4.ars/8 [1]
Links:
------
[1] http://arstechnica.com/apple/reviews/2005/04/macosx-10-4.ars/8
Customer reported EPIPE errors on multiple Backup2Go workstations.
Workstations were not being backed up.
B2Go Server:
...
[13/Feb/2015:11:32:55][1254.b02ab000][-conn:lexxsrv:1] Error: Start
backup 'MacMini-23-01.local' (10090): low space on
/Volumes/...
Great article by Mike Szumlinski on how to create previews in P4 and
P5 using qt_tools by David Van Brink
(http://www.omino.com/sw/qt_tools/).
http://www.xsanity.com/story/2011/generating-presstore-archive-proxies-qttools
[http://www.xsanity.com/story/2...
Turning on the 'Verify After Write' switch in the archive plan
configuration results in a post-archive task being launched that reads
all archived files from tape and verifies them. Presstore maintains a
table of all verified files during this step. The f...
Video walk-through of archiving data to a Backblaze Fireball, sending
the device back to Backblaze, Backblaze uploading the data into your
cloud bucket, and finally reconnecting P5 with the data in your cloud
bucket.
https://www.youtube.com/watch?v=kVNVF...
Customer attempted to import a LTFS tape into P5. The import failed.
The logs showed:
...
[16. Oct 2014 10:41][-thread:b0927000-] Error: awst0: label ltfs:
couldn't open "/usr/local/aw/temp/ltfs0096628517/.PresSTOREsVolumeID":
read-only file syst...
In the restore screen, as well in Backup as in Archive, the folders
are shown without size.
The reason for that is a technical one:
The size of the content of a folder is not constant, it changes for
instance dependeing on the index options.
A folder...
P5 indexes consist (among further info) of two parts:
* The file and folder structure and change thereof over time, and
* The media (tape) related tables with positions where the data is
stored.
Both parts are independent from each other. In case f...
Unix systems and Macs use the ctime, also called the inode change
time, to store the time a file's attributes were last changed. That
ctime stamp is updated each time when for instance the owner or the
posix access rights of a file change.
PresSTORE...
Question: Customer needs to restore a number of files, selects those
files and is being told which volumes will be needed. Required volumes
are being inserted into the jukebox and the restore job is being
started. Some time into the restore job, Presst...
For Synchronize, PresSTORE does not keep a permanent index. An index
of the folders and files of the source is built on the fly. This index
is sent over to the client where the target for the replication
resides. The client checks the target folders an...
Standard technical support is being provided through our support
website. Depending on the issue, we may require a phone call or a
remote control session with a customer. We use (and own a license for)
TEAMVIEWER (http://www.teamviewer.com [http://www.tea...
To restart the running P5 instance on the Unix-like host, perform the
following command as privileged user:
/usr/local/aw/stop-server
/usr/local/aw/start-server
You can also start the software with some other user by doing:
/usr/local/aw/start-server ...
Starting with version 6.1.2, P5 outputs statistic file info in Backup
Job logs.
This info gives an insight why files are saved, or saved again in
incremental backups.
FILE LOOKUP SUMMARY
This show the then number of files and folders that were found du...
When using include filters in Synchronize plans, it may appear that
files are copied with each sync job, even if these were not changed
The reason for behavior this is somewhat hidden:
Filters are applied on source and target in order to allow "other"...
UP UNTIL NOW:
A volume/tape will be reserved by a job to write when
* online, meaning it can be found in a library or drive -and-
* _"Appendable"_ -and-
* not _"Suspect"_.
A tape received "Recylable" status when
* not _"Suspect"_ -and-
* ...
