Scheduled Version Upgrade Dates and Refresh Requests
When a new NetSuite release is coming, check your scheduled upgrade date in the New Release portal. Avoid requesting a sandbox refresh close to your upgrade date. A sandbox refresh will fail if it doesn't finish before your scheduled version upgrade starts.
Use your best judgement to decide when to request a sandbox refresh during the version upgrade period for a new NetSuite release. For example, if it usually takes approximately two days for your sandbox refresh to complete, and:
-
if your scheduled version upgrade date is 72 hours (three days) away, defer your refresh request until your production and sandbox upgrades are complete.
-
if your scheduled version upgrade date is a week away, you might decide to go ahead and refresh your sandbox.
All sandbox accounts are targeted to be taken offline for upgrade at the time and date mentioned on the New Release portlet. The time to complete a sandbox upgrade can vary depending on the amount of data in the account. Average time is about an hour and most complete within 2 hours, but times can vary. The New Release portlet is located on the home page of your sandbox account. If you do not see the portlet, see Add the New Release Portlet to Your Dashboard.
You can request a refresh and monitor its status on the Sandbox Accounts page. This page is available to users with the Administrator or System Administrator roles. Go to Setup > Company > Sandbox Accounts.
If you upgrade your sandbox before your production account and then refresh it, the sandbox will revert to the same version as your production account.
When your account is ready to be activated, you will receive an email notification asking you to select the Activate Sandbox button on the Sandbox Accounts page.
When you activate a refreshed sandbox, the new sandbox completely replaces the previous sandbox. The new sandbox contains a copy of your chosen source account data that is a snapshot taken at the time of the sandbox refresh request. Any changes made to the sandbox during the refresh are not included in the new sandbox. Before you activate the new sandbox, save any changes you made after the refresh request. These changes must be saved outside of the sandbox account so that they are available to be added to the new sandbox after activation. Account administrators should formulate a strategy for saving these changes and adding them to the new sandbox, and inform users of the processes to be used. Change management across your sandbox accounts is your responsibility. For more information, see Refreshing Sandbox Accounts.