Acronis Backup Best Practices - Revision history

Nyz at 15:45, 13 August 2015

2015-08-13T15:45:50Z

← Older revision		Revision as of 15:45, 13 August 2015
Line 2:		Line 2:

	This is a collection of AN! documentation for standardizing operations. All data in contained articles should be sanitized for company/personal data and credentials. These are kept on the Wiki for transparency and on the chance the public finds the operations contained herein useful.		This is a collection of AN! documentation for standardizing operations. All data in contained articles should be sanitized for company/personal data and credentials. These are kept on the Wiki for transparency and on the chance the public finds the operations contained herein useful.

	~~{{footer}}~~

	The purpose of offering BaaS to Alteeve! clients is to provide a AN! supported backup method that is tested and known on Anvil! platforms. While there are many data retention solutions available, Acronis was chosen for it's ease-of-use by the end user and simple management while still retaining robust local and cloud-based backup options. Acronis software is intended to be installed on the client's virtual machines, and only interacts with the Anvil! when a full OS recovery is required. The Anvil! ensures it's own data retention innately via it's Highly Available construction, and does not require Acronis provisioning.		The purpose of offering BaaS to Alteeve! clients is to provide a AN! supported backup method that is tested and known on Anvil! platforms. While there are many data retention solutions available, Acronis was chosen for it's ease-of-use by the end user and simple management while still retaining robust local and cloud-based backup options. Acronis software is intended to be installed on the client's virtual machines, and only interacts with the Anvil! when a full OS recovery is required. The Anvil! ensures it's own data retention innately via it's Highly Available construction, and does not require Acronis provisioning.

Nyz at 15:44, 13 August 2015

2015-08-13T15:44:37Z

← Older revision		Revision as of 15:44, 13 August 2015
Line 1:		Line 1:
	{{~~subst::best practices~~}}		{{header}}

			This is a collection of AN! documentation for standardizing operations. All data in contained articles should be sanitized for company/personal data and credentials. These are kept on the Wiki for transparency and on the chance the public finds the operations contained herein useful.

			{{footer}}

	The purpose of offering BaaS to Alteeve! clients is to provide a AN! supported backup method that is tested and known on Anvil! platforms. While there are many data retention solutions available, Acronis was chosen for it's ease-of-use by the end user and simple management while still retaining robust local and cloud-based backup options. Acronis software is intended to be installed on the client's virtual machines, and only interacts with the Anvil! when a full OS recovery is required. The Anvil! ensures it's own data retention innately via it's Highly Available construction, and does not require Acronis provisioning.		The purpose of offering BaaS to Alteeve! clients is to provide a AN! supported backup method that is tested and known on Anvil! platforms. While there are many data retention solutions available, Acronis was chosen for it's ease-of-use by the end user and simple management while still retaining robust local and cloud-based backup options. Acronis software is intended to be installed on the client's virtual machines, and only interacts with the Anvil! when a full OS recovery is required. The Anvil! ensures it's own data retention innately via it's Highly Available construction, and does not require Acronis provisioning.

Nyz at 15:44, 13 August 2015

2015-08-13T15:44:16Z

← Older revision		Revision as of 15:44, 13 August 2015
Line 1:		Line 1:
	{{subst:best practices}}		{{subst::best practices}}

	The purpose of offering BaaS to Alteeve! clients is to provide a AN! supported backup method that is tested and known on Anvil! platforms. While there are many data retention solutions available, Acronis was chosen for it's ease-of-use by the end user and simple management while still retaining robust local and cloud-based backup options. Acronis software is intended to be installed on the client's virtual machines, and only interacts with the Anvil! when a full OS recovery is required. The Anvil! ensures it's own data retention innately via it's Highly Available construction, and does not require Acronis provisioning.		The purpose of offering BaaS to Alteeve! clients is to provide a AN! supported backup method that is tested and known on Anvil! platforms. While there are many data retention solutions available, Acronis was chosen for it's ease-of-use by the end user and simple management while still retaining robust local and cloud-based backup options. Acronis software is intended to be installed on the client's virtual machines, and only interacts with the Anvil! when a full OS recovery is required. The Anvil! ensures it's own data retention innately via it's Highly Available construction, and does not require Acronis provisioning.

Nyz at 15:43, 13 August 2015

2015-08-13T15:43:49Z

← Older revision		Revision as of 15:43, 13 August 2015
Line 1:		Line 1:
	{{subst:best ~~practices_header~~}}		{{subst:best practices}}

	The purpose of offering BaaS to Alteeve! clients is to provide a AN! supported backup method that is tested and known on Anvil! platforms. While there are many data retention solutions available, Acronis was chosen for it's ease-of-use by the end user and simple management while still retaining robust local and cloud-based backup options. Acronis software is intended to be installed on the client's virtual machines, and only interacts with the Anvil! when a full OS recovery is required. The Anvil! ensures it's own data retention innately via it's Highly Available construction, and does not require Acronis provisioning.		The purpose of offering BaaS to Alteeve! clients is to provide a AN! supported backup method that is tested and known on Anvil! platforms. While there are many data retention solutions available, Acronis was chosen for it's ease-of-use by the end user and simple management while still retaining robust local and cloud-based backup options. Acronis software is intended to be installed on the client's virtual machines, and only interacts with the Anvil! when a full OS recovery is required. The Anvil! ensures it's own data retention innately via it's Highly Available construction, and does not require Acronis provisioning.

Nyz at 15:43, 13 August 2015

2015-08-13T15:43:31Z

← Older revision		Revision as of 15:43, 13 August 2015
Line 1:		Line 1:
	{{best practices_header}}		{{subst:best practices_header}}

	The purpose of offering BaaS to Alteeve! clients is to provide a AN! supported backup method that is tested and known on Anvil! platforms. While there are many data retention solutions available, Acronis was chosen for it's ease-of-use by the end user and simple management while still retaining robust local and cloud-based backup options. Acronis software is intended to be installed on the client's virtual machines, and only interacts with the Anvil! when a full OS recovery is required. The Anvil! ensures it's own data retention innately via it's Highly Available construction, and does not require Acronis provisioning.		The purpose of offering BaaS to Alteeve! clients is to provide a AN! supported backup method that is tested and known on Anvil! platforms. While there are many data retention solutions available, Acronis was chosen for it's ease-of-use by the end user and simple management while still retaining robust local and cloud-based backup options. Acronis software is intended to be installed on the client's virtual machines, and only interacts with the Anvil! when a full OS recovery is required. The Anvil! ensures it's own data retention innately via it's Highly Available construction, and does not require Acronis provisioning.

Nyz at 15:42, 13 August 2015

2015-08-13T15:42:08Z

← Older revision		Revision as of 15:42, 13 August 2015
Line 1:		Line 1:
	{{best practices_header}}		{{best practices_header}}

	This article is intended as Best Practices for AN! personel in deploying and maintaining the Acronis BaaS product on virtual machines running on an Anvil! platform. All rights, etc, of proprietary products are held by their respective owners.

	The purpose of offering BaaS to Alteeve! clients is to provide a AN! supported backup method that is tested and known on Anvil! platforms. While there are many data retention solutions available, Acronis was chosen for it's ease-of-use by the end user and simple management while still retaining robust local and cloud-based backup options. Acronis software is intended to be installed on the client's virtual machines, and only interacts with the Anvil! when a full OS recovery is required. The Anvil! ensures it's own data retention innately via it's Highly Available construction, and does not require Acronis provisioning.		The purpose of offering BaaS to Alteeve! clients is to provide a AN! supported backup method that is tested and known on Anvil! platforms. While there are many data retention solutions available, Acronis was chosen for it's ease-of-use by the end user and simple management while still retaining robust local and cloud-based backup options. Acronis software is intended to be installed on the client's virtual machines, and only interacts with the Anvil! when a full OS recovery is required. The Anvil! ensures it's own data retention innately via it's Highly Available construction, and does not require Acronis provisioning.

Nyz: /* Method */

2015-08-13T15:31:28Z

Method

← Older revision		Revision as of 15:31, 13 August 2015
Line 33:		Line 33:
	&&TO TEST&& Can autofs mount an nfs share when requested by an acronis backup job?		&&TO TEST&& Can autofs mount an nfs share when requested by an acronis backup job?

	= Method =		= Method =

			Full Acronis documentation can be found at https://us-bc-baas.acronis.com/api/links/admin_guide?language=en. These instructions will not be replicated here, only a method by which they should be implemented, and any specific installation notes we might have in addition to the documentation.

	= The Management Console =		= The Management Console =

Nyz: /* The Management Console */

2015-08-13T15:30:20Z

The Management Console

← Older revision		Revision as of 15:30, 13 August 2015
Line 35:		Line 35:
	= Method =		= Method =

	= The Management Console =		= The Management Console =

			The main advantage to Acronis' offerings is their very coherent Web-based management platform. The Backup Management Console allows us to easily create and manage client accounts, monitor backup failures, and fully recover data when required by the client.

			The Backup Console can be found at https://baas.acronis.com. Login credentials are bestowed on AN! employees as needed, ask Digimer.

	= Creating Client Usergroups =		= Creating Client Usergroups =

Nyz at 15:03, 13 August 2015

2015-08-13T15:03:07Z

@@ Line 29: / Line 29: @@
 A Local destination may be any file or device connected to the Acronis client machine. As Acronis runs best as a scheduled backup, a removable storage device is not reccomended unless the client can ensure it will be available and connected at the scheduled times. CD or Removable media is not inherently supported, and must be burned or written manually.
-A Network Location includes Samba (Windows Shared Directories) or NFS shares mounted on the client machine.
+A Network Location includes Samba (Windows Shared Directories) or NFS shares mounted on the client machine. Installation and configuration of those services can be found on their respective pages.
   &&TO TEST&& Can autofs mount an nfs share when requested by an acronis backup job?

Nyz at 14:55, 13 August 2015

2015-08-13T14:55:22Z

← Older revision		Revision as of 14:55, 13 August 2015
Line 1:		Line 1:
	{{~~howto_header~~}}		{{best practices_header}}

	This article is intended as Best Practices for AN! personel in deploying and maintaining the Acronis BaaS product on virtual machines running on an Anvil! platform. All rights, etc, of proprietary products are held by their respective owners.		This article is intended as Best Practices for AN! personel in deploying and maintaining the Acronis BaaS product on virtual machines running on an Anvil! platform. All rights, etc, of proprietary products are held by their respective owners.