Seamless upgrade for network system

Patent metadata

Field	Value
Publication number	US-9430668-B2
Application number	US-201414292802-A
Country	US
Kind code	B2
Filing date	May 30, 2014
Priority date	May 30, 2014
Publication date	Aug 30, 2016
Grant date	Aug 30, 2016

Abstract

In one embodiment, a network system may be upgraded without losing access to write privileges to a network file 122 during the system upgrade. A network file management system 120 may execute a system upgrade. A network file management system 120 may provide direct write access for a data file 122 to a user throughout the system upgrade.

First claim

We claim:

1. A machine-implemented method, comprising:
maintaining a content database for a network file management system, the content database being separate from a source server farm configuration database that stores source configuration data for controlling access to a data file on the content database;
executing a system upgrade on the network file management system by performing an operation to switch from use of the source configuration data to target configuration data stored in a target server farm configuration database; and
during at least a portion of the execution of the system upgrade, processing an access request that requests access to the data file on the content database.

2. The method of claim 1 , wherein the access request is received from a client device over a network, the client device being remote from the network file management system, and wherein the target configuration data is obtained by applying at least one of an update or a patch to the source configuration data to obtain an upgraded version of the source configuration data.

3. The method of claim 1 , wherein the operation comprises a dual-mounting operation in which the content database is mounted to both the source server farm configuration database and the target server farm configuration database, the method further comprising:
based on a determination that the system upgrade has completed, dismounting the source server farm configuration database from the content database.

4. The method of claim 1 , further comprising:
directing an access request from a user prior to a changeover point to a source user proxy account.

5. The method of claim 1 , further comprising:
redirecting an access request from a user after a changeover point to a target user proxy account.

6. The method of claim 1 , further comprising:
block write access to a source management proxy account after a changeover point.

7. The method of claim 1 , further comprising:
grant write access to a target management proxy account after a changeover point.

8. A computing system comprising:
at least one processor; and
memory storing instructions executable by the at least one processor, wherein the instructions configure the computing system to:
control access to a data file on a network file management system using first configuration data:
execute a system upgrade to upgrade the configuration data used by the network file management system to control access to the data file from the first configuration data to second configuration data; and
during at least a portion of the execution of the system upgrade, provide direct write access for the data file on the network file management system to a use.

9. The computing system of claim 8 , wherein the instructions configure the computing system:
store the data file on a content database that is separate from a server farm configuration database that stores the configuration data used by the network file management system to control access to the data tile.

10. The computing system of claim 8 , wherein the instructions configure the computing system to:
dual-mount a content database for the network file management system to both a source server farm configuration database and a target server farm configuration database during the portion of execution of the system upgrade.

11. The computing system of claim 10 , wherein the instructions configure the computing system to:
dismount the source server farm configuration database from the content database.

12. The computing system of claim 8 , wherein the instructions configure the computing system to:
receive an access request from the user in a user proxy account.

13. The computing system of claim 8 , wherein the instructions configure the computing system to:
direct an access request from the user prior to a changeover point to a source user proxy account.

14. The computing system of claim 8 , wherein the instructions configure the computing system to:
redirect an access request from the user after a changeover point to a target user proxy account.

15. The computing system of claim 8 , wherein the instructions configure the computing system to:
receive an access request from the network file management system in a management proxy account.

16. The computing system of claim 8 , wherein the instructions configure the computing system to: block write access to a source management proxy account after a changeover point.

17. The computing system of claim 8 , wherein the instructions configure the computing system to:
grant write access to a target management proxy account after a changeover point.

18. A network file management system, comprising:
a content database interface that interacts with a content database that stores a multi-share data file; a source server farm configuration database interface that interacts with a source server farm configuration database that stores source configuration data separate from the content database;
a target server farm configuration database interface that interacts with a target server farm configuration database that stores target configuration data separate from the content database;
a processor that executes a virtual machine to process an access request to the multi-share data file on the content database during a system upgrade from the source server farm configuration database to the target server farm configuration database; and
a grid manager that blocks write access to a source management proxy account after a changeover point.

19. The network file management system of claim 18 , further comprising:
a load balancer that redirects an access request from the user after a changeover point to a target user proxy account.

Assignees

• Microsoft Technology Licensing Llc

Inventors

• Bie Fuyuan
• Chang Le
• Malhi Balinder
• Paranthaman Sundar
• Thomson Randy
• Kona Kalyan
• Raz Zohar
• Snapkauskas Darius
• Banerjee Atanu
• Silva Roshane

Classifications

• G06F21/62 Primary

  Protecting access to data via a platform, e.g. using keys or access control rules · CPC title

• G06F21/6218 Primary

  to a system of files or objects, e.g. local or distributed file system or database · CPC title

• H04L67/10

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title

• H04L67/1097

  for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title

• H04L67/1034

  Reaction to server failures by a load balancer · CPC title