QoreStor 7.5.0 onwards can protect Veeam backups over CIFS from unintentional changes. This can be achieved using UI option while creating a container or using CLI option “—veeam_overwrite_protect”. This option works with CIFS and Rapid CIFS protocols. Veeam customers can achieve immutability using this option along with enabling Recycle Bin. Once this option is enabled, it cannot be undone or disabled.
Due to its chain-level operation and lack of merges, Veeam forward incremental flow is the only application for which it is employed. Thus, backup files ending in .vbk and .vib, both complete and incremental, will only be unchangeable.
Following a backup and a predetermined amount of time that has passed since the file's last write activity, except delete and expiry, it is automatically rendered immutable for file operations like write, append, truncate, etc. It is safeguarded by a recycle bin for deletion. Therefore, as soon as this new option is activated on the CIFS container, the recycle bin is instantly enabled. All file operations are permitted on the system until the cool-off period.
The same is cascaded to the target QoreStor if replication is set up with this option. Therefore, the same data files become immutable after the cool-off period when replication is stopped. Only on-premises data is immutable for cloud replication.
Also, during disaster recovery, the data is not locked on the CIFS container. So backups are immute post cool-off period.
The Network File System (NFS) is a file system protocol that is designated to be a file server standard, and its protocol uses the Remote Procedure Call (RPC) method of communication between computers. Clients can access files via the network similar to the way that local storage is accessed.
NFS is a client-server application in which a client can view, store, and update files on a remote system just like they are working on a local system. System or Network Administrators can mount all or a portion of a file system, and the file system (or portion) that is mounted can be accessed using the privileges assigned to each file.
|
|
NOTE: If you want to do a mount on AIX, you must set the nfs_use_reserved_ports and portcheck parameters first. The parameters cannot be set to 0. For example: root@aixhost1 / # nfso -po portcheck=1 root@aixhost1 / # nfso -po nfs_use_reserved_ports=1 |
When Rapid NFS and Rapid CIFS are used with QoreStor they offer the following benefits:
- Reduce network utilization and DMA backup time
- Chunk data and perform hash computation on the client; transfer chunked hash files on the back-end
- Reduce the amount of data that must be written across the wire
- Improve performance
- Support DMAs such as CommVault, EMC Networker, and Tivoli Storage Manager. For the current list of supported DMAs, see the QoreStor Interoperability Guide.
- Compatible with existing NFS and CIFS clients — just need to install a plug-in (driver) on the client
- Can use Rapid NFS and Rapid CIFS to accelerate I/O operations on any client — including a client that uses home-grown backup scripts
- Can service multiple and concurrent media server backups
Rapid NFS and Rapid CIFS enable write operation acceleration on clients that use QoreStor replication and NFS or CIFS file system protocols. Similar to OST and RDS, these accelerators allow for better coordination and integration between QoreStor backup, restore, and optimized deduplication operations with Data Management Applications (DMAs) such as CommVault, EMC Networker, and Tivoli Storage Manager. For the current list of qualified DMAs, see the QoreStor Interoperability Guide.
Rapid NFS is a new client file system type that ensures that only unique data is written to QoreStor. It uses user space components and file system in user space (FUSE) to accomplish this. Metadata operations such as file creates and permission changes go through the standard NFS protocol, whereas write operations go through RDNFS.
Rapid CIFS is a Windows-certified filter driver that also ensures that only unique data is written to QoreStor.
All chunking and hash computations are done at the media or client server level.
Rapid NFS and Rapid CIFS require you to install a plug-in on the client or media server, depending on your DMA and configuration. For details, see "Configuring and Using Rapid NFS and Rapid CIFS".
