Veeam V12 is finally released on Feb 2023 with brunch of new features. YAY! I haven’t digested all the new features, however, one hidden feature I am interested in this release is the Veeam integration with HPE StoreOnce Cloud Bank.
Veeam SOBR Offload job is a storage management job to offload the backup from performance tier to capacity tier in SOBR. By default, this job will be kicked off every 4 hour by Veeam server.
There is a “Hidden” feature to manually kick off the offload job as below.
Continue readingIn Veeam backup management, it is supported to offload the GFS backup copy from performance tier repository to capacity tier repository. Normally the capaticyt tier will be configured on object storage (Azure Blob, AWS S3 and etc.) to reduce the storage cost.
However, when retrieve(download) the backup from capacity tier repository, there is only one option to download the backup for entire backup job which mighy includes multiple virtual machines. This short powershell script is crafted to download the monthly GFS bakcup for selected VM.
Continue readingHPE StoreOnce is a deduplication storage system providing efficient data compression and deduplication capability and suitable for data backup and long-term retention. HPE StoreOnce can be also be integrated with major backup vendors as the backup target storage.
This post is a quick introduction and demonstration of the HPE StoreOnce Catalyst Store for quick reference.
HPE StoreOnce is a deduplication storage system providing efficient data compression and deduplication capability and suitable for data backup and long-term retention. HPE StoreOnce can be integrated with major backup vendors as the backup target storage.
In Azure, there is virtual edition of HPE StoreOnce in Azure Marketplace. Deploying and initializing the HPE StoreOnce VSA is a very pleasant process with a straightforward outcome.
Since the HPE StoreOnce supports the data replication between appliances, the Azure based StoreOne VSA could be a good candidate of remote DR data copy by replicating the data from on-premise StoreOnce system.
It is noted that the VSA deployed in Azure will come with a trail license: “One time instant-on license for up to 90 days with a maximum 500TB capacity. No support provided by HPE.”
This post is to outline the deploying steps for quick reference.
Continue readingVeeam backup software family includes a solution to provide the backup capability for Azure virtual machines. As a kind of tradition of Veeam backup solutions, it provides a “Free Edition” to allow 10 VM backup for free. This post is to provide an overview about how to deploy the Veeam Backup for Microsoft Azure.
The first impression of this solution is its simplicity. Not only from the backup methodology, but also the deployment and operation.
Continue readingCommvault supports backing up Cassandra database. Cassandra is a distributed database that can handle large amounts of data on multiple nodes. For Cassandra version 3, Commvault support backup log files as well. This post is to outline the high level steps to configure the Cassandra backup in Commvault.
The below configuration applied to Cassandra version 3 and Commvault version 11.18.
RecoverPoint for virtual machines (RP4VM) is one of the DELL EMC data protection solutions to provide the VM level protection locally or remotely.
Comparing with the hardware RecoverPoint Appliance, RP4VM utilized virtual RecoverPoint Appliance and provide VM level protection with the data splitters installed on each of the ESXi servers.
RP4VM relies the vCenter to function properly. This post is to provide a quick guide about how to check and update the vCenter registration information in RP4VM.
When operating DELL EMC Networker environment, in some scenarios, it is required to clone a few selected saveset to target devices. In general, there are two ways to perform this:
This post provides an example to perform the Networker saveset clone by SSID through commands.
This post is to provide the general trouble shooting steps for one DELL EMC Networker Common Error, the Error Message is:
No matching devices; check storage nodes, devices or pools
This error message usually appears in both Networker client and server daemon.raw logs. The good side to see this error is the client can communicate with server.
The error is related with the backup client could not find a matching backup device to write the backup data. Let’s use an example as below to explain the trouble shooting steps:
