Bricklevel backup index file description - Revision history

Admin at 15:29, 21 May 2012

2012-05-21T15:29:23Z

← Older revision		Revision as of 15:29, 21 May 2012
Line 44:		Line 44:
	M:96:000000001F92E5D97FB841959DDD6A81FFE899CE010000000300000098F281AA92DE462CA18DF8034149890700000000:8:006C4100:1326788002:IPM.Appointment:1292954015:0:1327658400:1327662000:Meeting		M:96:000000001F92E5D97FB841959DDD6A81FFE899CE010000000300000098F281AA92DE462CA18DF8034149890700000000:8:006C4100:1326788002:IPM.Appointment:1292954015:0:1327658400:1327662000:Meeting

-	In ~~this case~~ the restorekey of the ~~items~~ is '''006C4100'''.	+	In the above example the restorekey of the appointment is '''006C4100'''.

Admin at 15:28, 21 May 2012

2012-05-21T15:28:50Z

← Older revision		Revision as of 15:28, 21 May 2012
Line 40:		Line 40:
	# data offset: The offset into the data file where the message begins.		# data offset: The offset into the data file where the message begins.
	# subject: This is the subject of the message.		# subject: This is the subject of the message.
		+
		+
		+	M:96:000000001F92E5D97FB841959DDD6A81FFE899CE010000000300000098F281AA92DE462CA18DF8034149890700000000:8:006C4100:1326788002:IPM.Appointment:1292954015:0:1327658400:1327662000:Meeting
		+
		+	In this case the restorekey of the items is '''006C4100'''.

Admin at 16:20, 19 March 2010

2010-03-19T16:20:35Z

← Older revision		Revision as of 16:20, 19 March 2010
Line 12:		Line 12:

	M <parent <length <entryid>> <rc <lengths> <bin>> <lmt> <ipc-type> <filepos> <subject>		M <parent <length <entryid>> <rc <lengths> <bin>> <lmt> <ipc-type> <filepos> <subject>
		+

	Container details in the index file, sorted on field number:		Container details in the index file, sorted on field number:

Admin at 16:20, 19 March 2010

2010-03-19T16:20:28Z

← Older revision		Revision as of 16:20, 19 March 2010
Line 8:		Line 8:

	C <parent <length <entryid>> <self <length> <entryid>> <rc <length> <hex>> <#msg> <lmt> <ipc-type> <dn>		C <parent <length <entryid>> <self <length> <entryid>> <rc <length> <hex>> <#msg> <lmt> <ipc-type> <dn>
-

	The format for a message is as follows:		The format for a message is as follows:

Admin at 16:20, 19 March 2010

2010-03-19T16:20:19Z

← Older revision		Revision as of 16:20, 19 March 2010
Line 3:		Line 3:

	R <self <length> <entryid>> <username>		R <self <length> <entryid>> <username>
-

	Where <self> is the identifier for the root container. This number can be present in the parent field for C and M entries. The self data is first represented by the data length, and then the data itself. The last field in this line is the username the backup was made for.		Where <self> is the identifier for the root container. This number can be present in the parent field for C and M entries. The self data is first represented by the data length, and then the data itself. The last field in this line is the username the backup was made for.

Admin: New page: Every line in the indexfile represents one item. An item can represent either a container (C), or a message (M). There are 2 extra lines at the beginning of the index. It starts with V:2. ...

2010-03-19T16:19:55Z

New page: Every line in the indexfile represents one item. An item can represent either a container (C), or a message (M). There are 2 extra lines at the beginning of the index. It starts with V:2. ...

New page

Every line in the indexfile represents one item. An item can represent either a container (C), or a message (M). There are 2 extra lines at the beginning of the index. It starts with V:2. This indicates the version of the index file, currently version 2.
The second line is always the root container, indicated by the letter R. The format for this line is:

R <self <length> <entryid>> <username>

Where <self> is the identifier for the root container. This number can be present in the parent field for C and M entries. The self data is first represented by the data length, and then the data itself. The last field in this line is the username the backup was made for.
The format for a container is as follows:

C <parent <length <entryid>> <self <length> <entryid>> <rc <length> <hex>> <#msg> <lmt> <ipc-type> <dn>

The format for a message is as follows:

M <parent <length <entryid>> <rc <lengths> <bin>> <lmt> <ipc-type> <filepos> <subject>

Container details in the index file, sorted on field number:

# C: Indicates the following information denotes a container.
# parent key string length: The length in characters of the following parent key.
# parent key: The key of the parent.
# own key string length: The length in characters of the following key.
# own key: The key of this container. Other containers and items may have this in the parent key field.
# restore key length: The length in characters of the following restore key.
#restore key: Use this key with the restore tool to restore this folder and it contents.
# number of items in this container: An indicator of how many items there are in this folder.
# last modification timestamp: The date of when this container was last modified, (eg it's name changed).
# container type: The MAPI type of the container.
# container name: The name of the container.

The message details in the index file, sorted on field number:

# M: Indicates the following information denotes a message.
# parent key string length: The length in characters of the following parent key.
# parent key: The key of the parent container
# restore key length: The length in characters of the following restore key.
# restore key: Use this key with the restore tool to restore this message.
# last modification timestamp: The date of when this message was last modified, (eg the date of a calendar item because it was moved).
# message type: The MAPI type of the message (eg mail, calendar item, contact, etc.)
# data offset: The offset into the data file where the message begins.
# subject: This is the subject of the message.