Store attachment outside of the database - Revision history

Admin at 13:05, 23 February 2011

2011-02-23T13:05:57Z

← Older revision		Revision as of 13:05, 23 February 2011
Line 6:		Line 6:

	== Migrating database storage to files ==		== Migrating database storage to files ==
-	Existing installations that already have the attachments in the database have the possibility to migrated to the file storage. In the ''/usr/share/zarafa'' directory there is a script available called ''db-convert-attachments-to-files''. This perl script will directly login to MySQL and dump the attachments to the specified directory. You have the run the script with the following options:	+	Existing installations that already have the attachments in the database have the possibility to migrated to the file storage. In the ''/usr/share/doc/zarafa'' directory there is a script available called ''db-convert-attachments-to-files''. This perl script will directly login to MySQL and dump the attachments to the specified directory. You have the run the script with the following options:

Admin: Protected "Store attachment outside of the database" [edit=sysop:move=sysop]

2008-11-27T15:40:17Z

Protected "Store attachment outside of the database" [edit=sysop:move=sysop]

← Older revision

Revision as of 15:40, 27 November 2008

Admin: /* Migrating database storage to files */

2008-10-03T12:58:36Z

Migrating database storage to files

← Older revision		Revision as of 12:58, 3 October 2008
Line 14:		Line 14:
	The last delete option is optional. This option will delete the attachments from the database.		The last delete option is optional. This option will delete the attachments from the database.
	The script can ran multiple times after each other, without having the attachments duplicated.		The script can ran multiple times after each other, without having the attachments duplicated.
		+
		+	To enable this settings you have to restart your Zarafa-server one time with the option --ignore-attachment-storage-conflict.
		+
		+	'''zarafa-server --ignore-attachment-storage-conflict'''

	== Storage layout ==		== Storage layout ==

Admin: /* Storage layout */

2008-09-19T09:11:54Z

Storage layout

← Older revision		Revision as of 09:11, 19 September 2008
Line 22:		Line 22:

	[[Category:Installation]]		[[Category:Installation]]
-	The attachment is in one of the directories with the id as filename. The stored attachment is the same as the attachment you will see in your email. With the ''file'' command you can see the ~~extension~~ of the attachment.	+	The attachment is in one of the directories with the id as filename. The stored attachment is the same as the attachment you will see in your email. With the ''file'' command you can see the probable type of the attachment.

Admin at 09:11, 19 September 2008

2008-09-19T09:11:20Z

← Older revision		Revision as of 09:11, 19 September 2008
Line 17:		Line 17:
	== Storage layout ==		== Storage layout ==
	The attachments are not all stored in a single directory, but spread over 200 directories.		The attachments are not all stored in a single directory, but spread over 200 directories.
-	Below the specified attachment_path there are 10 ~~directory~~ (0 - 9). Each directory has 20 subdirectories (0 -19).	+	Below the specified attachment_path there are 10 directories (0 - 9). Each directory has 20 subdirectories (0 - 19).
-	~~Via~~ the attachment id in the database, the exact location can be calculated via a fast algorithm.	+	Through the attachment id in the database, the exact location can be calculated via a fast algorithm.


	[[Category:Installation]]		[[Category:Installation]]
-	The attachment is in one of the ~~directory~~ with the id as filename. The stored attachment is the same as the attachment you will see in your email. ~~So via~~ the ''file'' command you can see the extension of the attachment.	+	The attachment is in one of the directories with the id as filename. The stored attachment is the same as the attachment you will see in your email. With the ''file'' command you can see the extension of the attachment.

Admin at 10:15, 7 September 2008

2008-09-07T10:15:09Z

← Older revision		Revision as of 10:15, 7 September 2008
Line 20:		Line 20:
	Via the attachment id in the database, the exact location can be calculated via a fast algorithm.		Via the attachment id in the database, the exact location can be calculated via a fast algorithm.

		+
		+	[[Category:Installation]]
	The attachment is in one of the directory with the id as filename. The stored attachment is the same as the attachment you will see in your email. So via the ''file'' command you can see the extension of the attachment.		The attachment is in one of the directory with the id as filename. The stored attachment is the same as the attachment you will see in your email. So via the ''file'' command you can see the extension of the attachment.

Admin: /* Migrating database storage to files */

2008-09-06T18:41:51Z

Migrating database storage to files

← Older revision		Revision as of 18:41, 6 September 2008
Line 7:		Line 7:
	== Migrating database storage to files ==		== Migrating database storage to files ==
	Existing installations that already have the attachments in the database have the possibility to migrated to the file storage. In the ''/usr/share/zarafa'' directory there is a script available called ''db-convert-attachments-to-files''. This perl script will directly login to MySQL and dump the attachments to the specified directory. You have the run the script with the following options:		Existing installations that already have the attachments in the database have the possibility to migrated to the file storage. In the ''/usr/share/zarafa'' directory there is a script available called ''db-convert-attachments-to-files''. This perl script will directly login to MySQL and dump the attachments to the specified directory. You have the run the script with the following options:
		+

	'''perl db-convert-attachments-to-files mysqluser mysqlpassword mysqldatabase path_to_filesystem [delete]'''		'''perl db-convert-attachments-to-files mysqluser mysqlpassword mysqldatabase path_to_filesystem [delete]'''
		+

	The last delete option is optional. This option will delete the attachments from the database.		The last delete option is optional. This option will delete the attachments from the database.
-	The script can ran multiple times after each other, without having the attachments duplicated.	+	The script can ran multiple times after each other, without having the attachments duplicated.

	== Storage layout ==		== Storage layout ==

Admin at 18:41, 6 September 2008

2008-09-06T18:41:38Z

← Older revision		Revision as of 18:41, 6 September 2008
Line 1:		Line 1:
-	~~== Storing attachments outside of the database ==~~
-
	From Zarafa version 6 you will have the possibility to store all attachments outside of the MySQL database. The architecture change is made to get a more efficient MySQL caching system and get a smaller database.		From Zarafa version 6 you will have the possibility to store all attachments outside of the MySQL database. The architecture change is made to get a more efficient MySQL caching system and get a smaller database.

Admin at 18:40, 6 September 2008

2008-09-06T18:40:49Z

← Older revision		Revision as of 18:40, 6 September 2008
Line 3:		Line 3:
	From Zarafa version 6 you will have the possibility to store all attachments outside of the MySQL database. The architecture change is made to get a more efficient MySQL caching system and get a smaller database.		From Zarafa version 6 you will have the possibility to store all attachments outside of the MySQL database. The architecture change is made to get a more efficient MySQL caching system and get a smaller database.

-	=== Configuring storage method ===	+	== Configuring storage method ==
-	The attachment storage can be configured in the server.cfg file via the option attachment_storage. When using the install script the default value is set to database, so the attachments are stored in the database.	+	The attachment storage can be configured in the server.cfg file via the option ''attachment_storage''. When using the install script the default value is set to database, so the attachments are stored in the database.
-	To store the attachment outside of the database, set this option to files and configure the attachment_path. Make sure that there is enough space on this partition ~~or filesystem~~.	+	To store the attachment outside of the database, set this option to ''files'' and configure the ''attachment_path''. Make sure that there is enough space on this partition.
		+
		+	== Migrating database storage to files ==
		+	Existing installations that already have the attachments in the database have the possibility to migrated to the file storage. In the ''/usr/share/zarafa'' directory there is a script available called ''db-convert-attachments-to-files''. This perl script will directly login to MySQL and dump the attachments to the specified directory. You have the run the script with the following options:
		+
		+	'''perl db-convert-attachments-to-files mysqluser mysqlpassword mysqldatabase path_to_filesystem [delete]'''
		+
		+	The last delete option is optional. This option will delete the attachments from the database.
		+	The script can ran multiple times after each other, without having the attachments duplicated.
		+
		+	== Storage layout ==
		+	The attachments are not all stored in a single directory, but spread over 200 directories.
		+	Below the specified attachment_path there are 10 directory (0 - 9). Each directory has 20 subdirectories (0 -19).
		+	Via the attachment id in the database, the exact location can be calculated via a fast algorithm.
		+
		+	The attachment is in one of the directory with the id as filename. The stored attachment is the same as the attachment you will see in your email. So via the ''file'' command you can see the extension of the attachment.

Admin: New page: == Storing attachments outside of the database == From Zarafa version 6 you will have the possibility to store all attachments outside of the MySQL database. The architecture change is ma...

2008-09-06T18:21:54Z

New page: == Storing attachments outside of the database == From Zarafa version 6 you will have the possibility to store all attachments outside of the MySQL database. The architecture change is ma...

New page

== Storing attachments outside of the database ==

From Zarafa version 6 you will have the possibility to store all attachments outside of the MySQL database. The architecture change is made to get a more efficient MySQL caching system and get a smaller database.

=== Configuring storage method ===
The attachment storage can be configured in the server.cfg file via the option attachment_storage. When using the install script the default value is set to database, so the attachments are stored in the database.
To store the attachment outside of the database, set this option to files and configure the attachment_path. Make sure that there is enough space on this partition or filesystem.