Abstract:
A method and system for utilizing snapshots to provide copies of a database or other application or large data structure to computing devices receives a request for access to a copy of a database, and performs a snapshot of a storage volume containing the requested database. The system then clones the snapshot and mounts the snapshot to a computing device, thus enabling the computing device to access a copy of the database. In some examples, the system automatically updates copies of a database on a scheduled basis (e.g., daily or weekly basis) to refresh a database regularly.
Abstract:
The present inventors devised a holistic approach for protecting serverless applications in single-cloud, multi-zone, multi-cloud, and/or non-cloud data center computing environments. An illustrative data storage management system discovers application assets, relationships, and interoperability dependencies and creates an “application entity” that references the various assets. Protection preferences apply to the application entity as a whole. An orchestration function in the system coordinates storage management operations (e.g., backup, replication, live synchronization, etc.) in a suitable order of operations gleaned from asset dependencies, if any. A set of copies of the application's discovered assets are generated in coordinated fashion and represent a point-in-time copy of the application. The point-in-time copy can be restored and/or migrated to other computing services by the data storage management system. The orchestration function coordinates restore and migration operations, including any cloud-to-cloud or cloud-to/from-non-cloud conversions that might be necessary to activate the application in a different computing environment.
Abstract:
Systems and methods use a ZFS file system in a Windows-based computing environment without protocol conversion or native ZFS support on Windows-based computing devices. Windows-based computing devices may obtain native Windows-based access to data in a storage volume that is managed by a Unix-based storage management server executing a ZFS volume manager and file system. ZFS clones may be served as logical unit numbers to Windows-based computing devices. The ZFS nature of the accessed storage volume is unbeknownst to the Windows-based machines. This enables Windows-based utilities, applications, and tools executing on a Windows-based computing device to operate upon the data in ZFS-managed space the same as they might have operated on a workspace in an array-created hardware snapshot in the prior art. Users may use storage space from their Windows-based computing devices according to a Windows-based file system such as NTFS. The Windows-based formatting of the contents in the ZFS-managed volumes are unbeknownst to the Unix-based storage management server and to the ZFS volume manager and file system.
Abstract:
Systems and methods use a ZFS file system in a Windows-based computing environment without protocol conversion or native ZFS support on Windows-based computing devices. Windows-based computing devices may obtain native Windows-based access to data in a storage volume that is managed by a Unix-based storage management server executing a ZFS volume manager and file system. ZFS clones may be served as logical unit numbers to Windows-based computing devices. The ZFS nature of the accessed storage volume is unbeknownst to the Windows-based machines. This enables Windows-based utilities, applications, and tools executing on a Windows-based computing device to operate upon the data in ZFS-managed space the same as they might have operated on a workspace in an array-created hardware snapshot in the prior art. Users may use storage space from their Windows-based computing devices according to a Windows-based file system such as NTFS. The Windows-based formatting of the contents in the ZFS-managed volumes are unbeknownst to the Unix-based storage management server and to the ZFS volume manager and file system.
Abstract:
Queued software patches are analyzed before one patch is chosen as the next patch to be integrated into a working build. The chosen patch might not be next in chronological order of arrival at the queue. Instead, an illustrative build server applies a number of priority factors to every patch awaiting integration in the patch queue, specifically by analyzing one or more relevant attributes of the patch. The patch that receives the highest priority score in the course of the evaluation is then extracted for integration. After the patch has been integrated, the build server (e.g., using an illustrative patch queue manager module) circles back and again evaluates all the patches in the current queue, which may have queued new patches that were submitted while the previous patch was being integrated. Relative to a default chronological order, a given patch may receive a boost in priority or, conversely, may have its priority reduced.
Abstract:
Systems and methods use a ZFS file system in a Windows-based computing environment without protocol conversion or native ZFS support on Windows-based computing devices. Windows-based computing devices may obtain native Windows-based access to data in a storage volume that is managed by a Unix-based storage management server executing a ZFS volume manager and file system. ZFS clones may be served as logical unit numbers to Windows-based computing devices. The ZFS nature of the accessed storage volume is unbeknownst to the Windows-based machines. This enables Windows-based utilities, applications, and tools executing on a Windows-based computing device to operate upon the data in ZFS-managed space the same as they might have operated on a workspace in an array-created hardware snapshot in the prior art. Users may use storage space from their Windows-based computing devices according to a Windows-based file system such as NTFS. The Windows-based formatting of the contents in the ZFS-managed volumes are unbeknownst to the Unix-based storage management server and to the ZFS volume manager and file system.
Abstract:
Systems and methods are disclosed that substantially overcome the long delays and unproductive cycle time inherent in managing an informal (friendly) build platform. The systems and methods disclosed herein ensure that an official software base residing on a production machine propagates efficiently to the machine that generates the friendly builds, and furthermore, the friendly-build machine experiences minimal unproductive cycle time between successive friendly builds. Accordingly, developers experience improved access to, and more efficient use of, the computing device that generates the friendly executables.
Abstract:
A method and system for utilizing snapshots to provide copies of a database or other application or large data structure to computing devices receives a request for access to a copy of a database, and performs a snapshot of a storage volume containing the requested database. The system then clones the snapshot and mounts the snapshot to a computing device, thus enabling the computing device to access a copy of the database. In some examples, the system automatically updates copies of a database on a scheduled basis (e.g., daily or weekly basis) to refresh a database regularly.
Abstract:
The present inventors devised a holistic approach for protecting serverless applications in single-cloud, multi-zone, multi-cloud, and/or non-cloud data center computing environments. An illustrative data storage management system discovers application assets, relationships, and interoperability dependencies and creates an “application entity” that references the various assets. Protection preferences apply to the application entity as a whole. An orchestration function in the system coordinates storage management operations (e.g., backup, replication, live synchronization, etc.) in a suitable order of operations gleaned from asset dependencies, if any. A set of copies of the application's discovered assets are generated in coordinated fashion and represent a point-in-time copy of the application. The point-in-time copy can be restored and/or migrated to other computing services by the data storage management system. The orchestration function coordinates restore and migration operations, including any cloud-to-cloud or cloud-to/from-non-cloud conversions that might be necessary to activate the application in a different computing environment.
Abstract:
A holistic approach protects serverless applications in various cloud and/or non-cloud data center computing environments. An illustrative data storage management system deploys, or causes to be deployed, a discovery tracker function in a customer's cloud service account. The discovery tracker identifies and tracks what applications are executing therein, whether they are already known to the illustrative system or not. This aspect ensures that the system is up-to-date with a customer's cloud deployments, so that it may timely back up active applications, and conversely, so that it may dispose properly of copies of applications that are no longer deployed. The discovery tracker discovers application assets, relationships, and interoperability dependencies. The illustrative system creates a corresponding “application entity” that references the various assets. An orchestration function coordinates storage management operations to generate a set of copies of the application's discovered assets. The set of copies forms a point-in-time copy of the application.