Archive Type
- DarkLight
Archive Type
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Amazon S3 Bucket Archive Type
Go to the Settings tab and make sure that the Purge switch is set to On. Users cannot turn this OFF.
Activate the Archive switch OFF if you do not want the purged data to be archived.
Note:
If you turn the Archive switch OFF, the utility removes the purged data permanently from the database. You will not be able to access purged data.
Select the Archive Type as Amazon S3.
Enter the S3 URL that stores your archived data. Create a separate folder on the Amazon S3 bucket for the archived data and configure that folder in the S3 URL field.
Enter the AWS Region End Point. This is the region that your AWS S3 bucket is located in.
Enter the AWS Access Key. This is the key to access your AWS S3 bucket. Access Keys are used to sign the requests you send to Amazon S3. AWS validates this key and allows access. You use access keys to sign API requests that you make to AWS.
Enter the Amazon AWS KMS Encrypt (Key Management Service). You can set the value as true or false. If set as true, this encrypts data stored on the S3 bucket.
Enter the AWS Secret Key. This is the secret key (like the password) for the AWS Access Key configured in item 5 above. The combination of an access key ID and a secret access key is required for authentication.
Enter the Server-Side Encryption. This is the encrypt/decrypt key, defining that the purged data is encrypted using the AWS’ Key Management System (KMS) encryption.
Enter the KMS Key. This is the key to decrypt the data on S3 bucket.
Shared Drive Archive Type
Select the Archive Type as Shared Drive.
Enter the IP address or the Host Name of the device that stores your archived data.
Enter the User ID of the user that accesses the above drive to store the data. This should be a combination of domain and username. For example, <domain>\UserID.
Enter the Password for the user to access the shared drive.
Enter the Path on the shared drive where your data is to be archived.
Note:
When giving the path, do not include any slash/backslash at the beginning. For example, if you require your data to be archived in the Archive folder of the machine having IP address 172.20.3.74, give the IP address as 172.20.3.74 and the Path as Archive. If you are using a subfolder under Archive, specify the correct path - Archive\PurgeData.
Database Archive Type
Select the Archive Type as Database.
Select an authentication type from the following:
SQL Authentication: This is a typical authentication used for various database systems and comprises a username and a password. Obviously, an instance of SQL Server can have multiple user accounts (using SQL authentication) with different usernames and passwords. In shared servers where different users should have access to different databases, SQL authentication is preferred. SQL Authentication is also required when a client (remote computer) connects to an instance of SQL server on a computer other than the one on which the client is running.
Windows Authentication: When you are accessing SQL server from the same computer. it is installed on, you are normally not asked to type in a username and password. With Windows Authentication, the SQL server service already knows that someone is logged in to the operating system with the authenticated credentials. The SQL server service uses these credentials to allow the user into its databases. Of course, this works as long as the client resides on the same computer as the SQL server, or as long as the connecting client matches the Windows credentials of the server. Windows Authentication is often used as a more convenient way to log in to a SQL server instance without typing a username and a password. When more users are involved, or remote connections are being established with the SQL Server, SQL Authentication should be used.
Enter the IP Address of the device that has the database that stores your archived data.
Enter the Port Number that communicates with the database that stores the archived data.
Enter the Database name. Create a database via SQL Studio to archive the purged data. Enter the database name in this field.
Enter the User ID and the Password of the user that accesses the database.
Google Storage Type Archive Type
Select the Archive Type as Google Cloud Storage.
Select an authentication type from the following:
SQL Authentication: This is a typical authentication used for various database systems and comprises a username and a password. Obviously, an instance of SQL Server can have multiple user accounts (using SQL authentication) with different usernames and passwords. In shared servers where different users should have access to different databases, SQL authentication is preferred. SQL Authentication is also required when a client (remote computer) connects to an instance of SQL server on a computer other than the one on which the client is running.
Windows Authentication: When you are accessing SQL server from the same computer it is installed on, you are normally not asked to type in a username and password. With Windows Authentication, the SQL server service already knows that someone is logged in to the operating system with the authenticated credentials. The SQL server service uses these credentials to allow the user into its databases. Of course, this works as long as the client resides on the same computer as the SQL server, or as long as the connecting client matches the Windows credentials of the server. Windows Authentication is often used as a more convenient way to log in to a SQL server instance without typing a username and a password. When more users are involved, or remote connections are being established with the SQL Server, SQL Authentication should be used.
Enter the Archive Bucket Path. This is the path on Google Cloud Storage where the application stores the archived data.
Enter the Account Type. This is the account type used to access the Google Cloud Storage. Use service_account as the default account type.
Enter the Client Email. This is the Email address of the Google Cloud Platform client account used to access the Google Cloud Storage.
Enter the Private Key. This is the Private Key of the Google Account to access the Google Cloud Storage to place the archived data.
Fields
Fields | Description |
S3 URL | URL that stores your archived data |
AWS Region End Point | Region that your AWS S3 bucket is located in |
AWS Access Key | This is the key to access your AWS S3 bucket. Access Keys are used to sign the requests you send to Amazon S3. AWS validates this key and allows access. You use access keys to sign API requests that you make to AWS. |
Amazon AWS KMS Encrypt | Set this as true or false. If set as true, this encrypts data stored on the S3 bucket. |
AWS Secret Key | This is the secret key (like the password) for the AWS Access Key configured in item 5 above. The combination of an access key ID and a secret access key is required for authentication. |
Server Side Encryption | This is the encrypt/decrypt key, defining that the purged data is encrypted using the AWS’ Key Management System (KMS) encryption. |
KMS Key | This is the key to decrypt the data on S3 bucket |
Schedule | Defines schedule for the purge activity. |
Excluded Days | Using the Excluded Days field, you can configure the days of the week when you do not want the application to perform the Purge (or Purge and Archive) activity. This helps retain the data for purge-excluded days. This is an optional field; you can select multiple days. |
IP address or Host Name | IP address or the Host Name of the device that stores your archived data |
User ID | User ID of the user that accesses the above drive to store the data. This should be a combination of domain and username. |
Password | Password for user to access the shared drive |
Path | Path of shared drive where data needs to archive |
SQL Authentication | This is a typical authentication used for various database systems, and comprises a username and a password. Obviously, an instance of SQL Server can have multiple user accounts (using SQL authentication) with different usernames and passwords. In shared servers where different users should have access to different databases, SQL authentication is preferred. SQL Authentication is also required when a client (remote computer) connects to an instance of SQL server on a computer other than the one on which the client is running. |
Windows Authentication | When you are accessing SQL server from the same computer it is installed on, you are normally not asked to type in a username and password. With Windows Authentication, the SQL server service already knows that someone is logged in to the operating system with the authenticated credentials. The SQL server service uses these credentials to allow the user into its databases. Of course, this works as long as the client resides on the same computer as the SQL server, or as long as the connecting client matches the Windows credentials of the server. Windows Authentication is often used as a more convenient way to log in to a SQL server instance without typing a username and a password. When more users are involved, or remote connections are being established with the SQL Server, SQL Authentication should be used. |
Archive Bucket Path | This is the path on Google Cloud Storage where the application stores the archived data. |
Account Type | This is the account type used to access the Google Cloud Storage. Use service_account as the default account type. |
Client Email | This is the Email address of the Google Cloud Platform client account used to access the Google Cloud Storage. 8.Enter the Private Key. |
Private Key | This is the Private Key of the Google Account to access the Google Cloud Storage to place the archived data. |
Was this article helpful?